You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Add TUI ability to inspect session system messages #24990
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Currently, there is no way to directly inspect or view system messages (such as system prompts, environment info, or initial context details) from the OpenCode TUI during a session. This feature request proposes adding a TUI feature to view the current or previous system message(s) associated with the active session or a selected session.
Benefits:
Allows users to verify, debug, and audit what system prompt/context is being provided to the model.
Helps troubleshoot session behavior by letting users see key context details (like working directory, platform, custom environment settings, etc.) used in system messages.
Improves transparency for users who suspect system context is affecting completions or need to confirm OPENCODE's understanding of environment state.
Suggested implementation:
Add a TUI shortcut or command (e.g., /system or a context menu option in the session list) that opens the latest system message for the current session.
Optionally support viewing system messages for previous sessions or the full session timeline.
Display the exact content of the message (with redaction as needed for sensitive values), formatted for readability.
This would give TUI users parity with API/web users who can already view or export system messages, and is especially helpful for CLI-only workflows.
Extra points for being able to edit them in EDITOR for while that part stays alive, but that could conflict with how it is implemented so probably not super important. But it would be really nice for testing small system message changes.
This could help debug problems that happen when changing agent or model during a conversation, for example. It could also help users understand and better learn how LLMs and agentic harnesses work.
It does not add a TUI surface, but it adds a CLI debug command for inspecting the resolved effective system prompt:
opencode debug prompt
The goal is to make prompt customization easier to debug from the CLI: AGENTS.md, opencode.jsoninstructions, skills, MCP instructions, custom agents, and system prompt plugin transforms.
This does not replace the TUI request in this issue, but it may cover part of the same debugging/auditing need for CLI workflows.
Activity
e-magon commentedon Jun 22, 2026
This could help debug problems that happen when changing agent or model during a conversation, for example. It could also help users understand and better learn how LLMs and agentic harnesses work.
Rexarrior commentedon Jul 31, 2026
I opened a related but narrower PR here: #39905
It does not add a TUI surface, but it adds a CLI debug command for inspecting the resolved effective system prompt:
The goal is to make prompt customization easier to debug from the CLI:
AGENTS.md,opencode.jsoninstructions, skills, MCP instructions, custom agents, and system prompt plugin transforms.This does not replace the TUI request in this issue, but it may cover part of the same debugging/auditing need for CLI workflows.
github-actions commentedon Sep 30, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.