anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Audit log of commands ran by the LLM #6885

New Issue
Open
opened 2026-02-16 18:05:31 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:05:31 -05:00
Owner
Copy Link
Copy Source

Originally created by @Sleepful on GitHub (Jan 20, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Simple, I let the agent code and run commands for a bit, it generates a long wall of text. I don't want to scroll through the wall of text to find each command that has been run, I do a poor job at scrolling through.

I want to open only the commands that have been run by the agent, with the option to look at the output or ignore the output, even better if I can choose to toggle the output of each command. This log should not have any other text generated, to easily review every action (bash command) that got triggered.

Extra great if there is the option to filter some commands out of the log, such as grep commands that might not be important to audit and could generate noise.

For even better reporting: a toggle that allows these command logs to be output into a specific file.

That's all!

Reviewing is every time more important with these tools, thus, lets facilitate reviewing the critical pieces.

Originally created by @Sleepful on GitHub (Jan 20, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Simple, I let the agent code and run commands for a bit, it generates a long wall of text. I don't want to scroll through the wall of text to find each command that has been run, I do a poor job at scrolling through. I want to open _only_ the commands that have been run by the agent, with the option to look at the output or ignore the output, even better if I can choose to toggle the output of each command. This log should not have any other text generated, to easily review every action (bash command) that got triggered. Extra great if there is the option to filter some commands out of the log, such as `grep` commands that might not be important to audit and could generate noise. For even better reporting: a toggle that allows these command logs to be output into a specific file. That's all! Reviewing is every time more important with these tools, thus, lets facilitate reviewing the critical pieces.
yindo added the discussion label 2026-02-16 18:05:31 -05:00
yindo commented 2026-02-16 18:05:31 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 20, 2026):

This issue might be related to the following existing feature requests. Please check:

  • #9387: opencode session export to markdown or json - Focuses on exporting full session transcripts
  • #7535: Session logging as OpenAI messages - Focuses on preserving request-response pairs for training
  • #6604: MCP Tool Output - Related to displaying tool execution details in TUI

These issues share the theme of improving visibility and auditability of agent operations. Feel free to cross-reference if your use case differs from these existing requests.

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be related to the following existing feature requests. Please check: - #9387: `opencode session export` to markdown or json - Focuses on exporting full session transcripts - #7535: Session logging as OpenAI messages - Focuses on preserving request-response pairs for training - #6604: MCP Tool Output - Related to displaying tool execution details in TUI These issues share the theme of improving visibility and auditability of agent operations. Feel free to cross-reference if your use case differs from these existing requests.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6885
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?