anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Use agent description as prompt placeholder text #6420

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

Originally created by @JosXa on GitHub (Jan 15, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

Currently, the prompt input placeholder always shows randomized hint text like "Ask anything... 'debug the login flow'", regardless of which agent is active. This means users don't get contextual information about what the current agent is designed to do.

When switching between specialized agents (e.g., from build to docs to frontend-ui-ux-engineer), the placeholder text doesn't adapt to reflect the agent's purpose, missing an opportunity to guide users on what kind of tasks to request.

Proposed Solution

Display the agent's description as the placeholder text when available, falling back to randomized hints only for:

  • The build agent (default mode for newcomers)
  • Agents without descriptions

Benefits

  1. Contextual guidance: Users immediately see what the active agent specializes in
  2. Better discoverability: Agent capabilities are surfaced without needing to check documentation
  3. Smoother onboarding: New users still get the polished randomized hints on the default build agent

Implementation Details

  • Use agent description as placeholder when available
  • Stop hint rotation when showing descriptions (avoid distraction)
  • Continue rotation for build agent and agents without descriptions
  • Apply to both CLI/TUI and web app

Example

When switching to the docs agent:

  • Before: "Ask anything... 'refactor the authentication'"
  • After: "Writes and maintains comprehensive technical documentation"

Additional Context

This enhances the agent switching UX by providing immediate feedback about what changed and what the new agent can do.

Originally created by @JosXa on GitHub (Jan 15, 2026). Originally assigned to: @thdxr on GitHub. ## Problem Currently, the prompt input placeholder always shows randomized hint text like "Ask anything... 'debug the login flow'", regardless of which agent is active. This means users don't get contextual information about what the current agent is designed to do. When switching between specialized agents (e.g., from `build` to `docs` to `frontend-ui-ux-engineer`), the placeholder text doesn't adapt to reflect the agent's purpose, missing an opportunity to guide users on what kind of tasks to request. ## Proposed Solution Display the agent's description as the placeholder text when available, falling back to randomized hints only for: - The `build` agent (default mode for newcomers) - Agents without descriptions ### Benefits 1. **Contextual guidance**: Users immediately see what the active agent specializes in 2. **Better discoverability**: Agent capabilities are surfaced without needing to check documentation 3. **Smoother onboarding**: New users still get the polished randomized hints on the default build agent ### Implementation Details - Use agent description as placeholder when available - Stop hint rotation when showing descriptions (avoid distraction) - Continue rotation for build agent and agents without descriptions - Apply to both CLI/TUI and web app ## Example When switching to the `docs` agent: - **Before**: "Ask anything... 'refactor the authentication'" - **After**: "Writes and maintains comprehensive technical documentation" ## Additional Context This enhances the agent switching UX by providing immediate feedback about what changed and what the new agent can do.
yindo commented 2026-02-16 18:04:10 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #7492: Primary agents lack identity awareness when user switches agents - cannot determine which agent is active
  • #4825: agent description used in /agent command are cutoff
  • #6335: Improve Agent Navigation: Tree View, Alphabetical Sorting, and Active/Inactive Filtering
  • #6101: indicator for the currently active subagent

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

@github-actions[bot] commented on GitHub (Jan 15, 2026): This issue might be a duplicate of existing issues. Please check: - #7492: Primary agents lack identity awareness when user switches agents - cannot determine which agent is active - #4825: agent description used in /agent command are cutoff - #6335: Improve Agent Navigation: Tree View, Alphabetical Sorting, and Active/Inactive Filtering - #6101: indicator for the currently active subagent Feel free to ignore if none of these address your specific case.
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
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#6420
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?