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]: Collapse skill body in user message #33980
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Currently, OpenCode appends the full skill/command body to the user message. This takes up a large space in the UI and makes it difficult to navigate in the session history.
It would be great if we could have a dedicated UI component for skills/commands used. Would be better if they could be toggled to collapse/show just like generic tool outputs now.
The Codex (currently ChatGPT) app provides a much cleaner experience here: invoking a skill only adds a lightweight skill reference or metadata entry to the visible conversation, while the agent can still access the full skill instructions internally.
In OpenCode, I currently avoid invoking skills explicitly. Instead, I mention the skill name in a normal message and let the agent load it automatically. This keeps the conversation readable, but it is an inconvenient workaround.
Ideally, explicit skill invocation should:
display only the skill name and description in the user message;
keep the complete SKILL.md content available to the agent;
optionally allow users to expand the full content;
avoid rendering the skill instructions as if they were written by the user.
In other words, the visible conversation representation should be separated from the context supplied to the agent.
Reacted by 4rcadia, iWorld Jiang and Mohamed Ibrahim
The Codex (currently ChatGPT) app provides a much cleaner experience here: invoking a skill only adds a lightweight skill reference or metadata entry to the visible conversation, while the agent can still access the full skill instructions internally.
In OpenCode, I currently avoid invoking skills explicitly. Instead, I mention the skill name in a normal message and let the agent load it automatically. This keeps the conversation readable, but it is an inconvenient workaround.
Ideally, explicit skill invocation should:
display only the skill name and description in the user message;
keep the complete SKILL.md content available to the agent;
optionally allow users to expand the full content;
avoid rendering the skill instructions as if they were written by the user.
In other words, the visible conversation representation should be separated from the context supplied to the agent.
Unfortunately, they don't usually merge UI/UX PRs, so the best thing to do would be to mention a maintainer, @rekram1-node.
Activity
[-][FEATURE]: Folding command or skill body in user message[/-][+][FEATURE]: Hiding skill body in user message[/+]iWorld-y commentedon Jul 27, 2026
I’m running into the same issue.
The Codex (currently ChatGPT) app provides a much cleaner experience here: invoking a skill only adds a lightweight skill reference or metadata entry to the visible conversation, while the agent can still access the full skill instructions internally.
In OpenCode, I currently avoid invoking skills explicitly. Instead, I mention the skill name in a normal message and let the agent load it automatically. This keeps the conversation readable, but it is an inconvenient workaround.
Ideally, explicit skill invocation should:
SKILL.mdcontent available to the agent;In other words, the visible conversation representation should be separated from the context supplied to the agent.
[-][FEATURE]: Hiding skill body in user message[/-][+][FEATURE]: Collapse skill body in user message[/+]Arcadi4 commentedon Jul 27, 2026
Unfortunately, they don't usually merge UI/UX PRs, so the best thing to do would be to mention a maintainer, @rekram1-node.
mibrahimdev commentedon Aug 21, 2026
Any news?
Arcadi4 commentedon Sep 27, 2026
Shipped in v2!
mibrahimdev commentedon Sep 27, 2026
Finally, thank you