gemini-cli - 💡(How to fix) Fix tool execution history in yolo mode [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#26044Fetched 2026-04-28 06:50:01
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
issue_type_added ×1labeled ×1
RAW_BUFFERClick to expand / collapse

What would you like to be added?

The yolo mode is convenient but the user should have the power of visibility into what was executed , changes made or any specific output. Hence, I suggest logging the tool calls, especially the lengthy commands for shell executions. an external logger or some kind of plugin capability must be there.

Why is this needed?

Currently, you can review the whole session history by resuming it scrolling manually upwards but that's inefficient and often times as the bash commands are truncated in the preview not possible to read the whole command that was executed. This is really a problem when you're auditing what the agent did.

Additional context

No response

extent analysis

TL;DR

Implementing an external logger or plugin capability to log tool calls and shell executions can provide visibility into the actions taken and changes made.

Guidance

  • Consider adding a logging mechanism to capture the output of lengthy shell commands, allowing users to review the entire command without truncation.
  • Introduce a plugin architecture to enable the integration of external loggers, providing flexibility and customization options for users.
  • Evaluate the current session history review process and explore alternatives to manual scrolling, such as searchable logs or command history summaries.
  • Assess the feasibility of displaying the full command in the preview, rather than truncating it, to improve auditing capabilities.

Notes

The implementation details of the logging mechanism and plugin architecture are not specified, and may require further discussion and design.

Recommendation

Apply workaround: Implement a basic logging mechanism to capture tool calls and shell executions, and consider introducing a plugin architecture in a future iteration, as this will provide immediate visibility into the actions taken and changes made, while also laying the groundwork for more advanced logging and auditing capabilities.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix tool execution history in yolo mode [1 participants]