The title generated from a custom command gets confused by instructions #1480

Closed
opened 2026-02-16 17:31:11 -05:00 by yindo · 7 comments
Owner

Originally created by @Cluster444 on GitHub (Aug 25, 2025).

Originally assigned to: @rekram1-node on GitHub.

So basically I have instructions to the running agent that if no args are passed, the agent should not try to continue, but ask the user to provide some information after the command is run. Problem is this causes the title generator to bug out on the same instruction.

Maybe the title generator could be tweaked a touch to have it not follow instructions in the prompt its generating for?

Easiest to see here

https://opencode.ai/s/Jn9ER46G

Originally created by @Cluster444 on GitHub (Aug 25, 2025). Originally assigned to: @rekram1-node on GitHub. So basically I have instructions to the running agent that if no args are passed, the agent should not try to continue, but ask the user to provide some information after the command is run. Problem is this causes the title generator to bug out on the same instruction. Maybe the title generator could be tweaked a touch to have it not follow instructions in the prompt its generating for? Easiest to see here https://opencode.ai/s/Jn9ER46G
yindo closed this issue 2026-02-16 17:31:11 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 25, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #948: Similar issue where generated titles included response text instead of being concise titles, though that was focused on verbose prompts/attachments rather than custom commands specifically

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Aug 25, 2025): This issue might be a duplicate of existing issues. Please check: - #948: Similar issue where generated titles included response text instead of being concise titles, though that was focused on verbose prompts/attachments rather than custom commands specifically Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Aug 29, 2025):

should be fixed in next release

Edit: reverted this change

@rekram1-node commented on GitHub (Aug 29, 2025): ~~should be fixed in next release~~ Edit: reverted this change
Author
Owner

@rekram1-node commented on GitHub (Aug 29, 2025):

actually I didn't like solution, reopening will address better

@rekram1-node commented on GitHub (Aug 29, 2025): actually I didn't like solution, reopening will address better
Author
Owner

@Cluster444 commented on GitHub (Aug 30, 2025):

Had another similar weird one that I didn't notice at first, looks like a straight tool call in the title

Image

And here's the session for it
https://opencode.ai/s/Cv26wvD4

@Cluster444 commented on GitHub (Aug 30, 2025): Had another similar weird one that I didn't notice at first, looks like a straight tool call in the title <img width="512" height="183" alt="Image" src="https://github.com/user-attachments/assets/71208aca-4a7e-4a4e-b186-150700e160af" /> And here's the session for it https://opencode.ai/s/Cv26wvD4
Author
Owner

@rekram1-node commented on GitHub (Aug 30, 2025):

now that one might just be a grok code thing tbh but I will address both shortly

@rekram1-node commented on GitHub (Aug 30, 2025): now that one might just be a grok code thing tbh but I will address both shortly
Author
Owner

@rekram1-node commented on GitHub (Aug 30, 2025):

I tested quite a bit, think I have a decent fix now

@rekram1-node commented on GitHub (Aug 30, 2025): I tested quite a bit, think I have a decent fix now
Author
Owner

@rekram1-node commented on GitHub (Aug 31, 2025):

should be fixed in next release

@rekram1-node commented on GitHub (Aug 31, 2025): should be fixed in next release
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1480