anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: message tool for subagent-to-user direct output #5305

New Issue
Open
opened 2026-02-16 17:51:07 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:51:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @jcyamacho on GitHub (Jan 13, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Feature Request: message tool for subagent-to-user direct output

Problem

When a subagent (via subtask: true command or Task tool) generates carefully
formatted output, the main agent receives it and often reformulates, summarizes,
or adds commentary before presenting to the user. There's no way to guarantee
verbatim output delivery.

Example scenario:

A subagent generates a SQL migration script that must be exact:

ALTER TABLE users ADD COLUMN last_login TIMESTAMP;
CREATE INDEX idx_users_last_login ON users(last_login);
UPDATE users SET last_login = created_at WHERE last_login IS NULL;

The subagent produces exactly what the user needs. But the main agent receives
this and responds with:

"I've generated a migration script for you. It adds a last_login column
and creates an index. Here's what it does..."

The user wanted the raw SQL to copy-paste, not an explanation of it.

Proposed Solution

Add a message tool that subagents can invoke to push content directly to the
user, bypassing the main agent's interpretation layer.

API Design

message({
  content: string,       // Content to display to user
  format?: "text" | "markdown" | "code",  // Display hint (default: "text")
  language?: string,     // For format: "code", e.g., "sql", "yaml"
  label?: string,        // Optional header, e.g., "Migration Script"
})

Usage Example

---
description: Generate database migration
agent: db-expert
subtask: true
---

Analyze the schema changes needed and generate a migration script.

After generating, use the `message` tool to send it directly to the user:

message({
  content: "<the migration SQL>",
  format: "code",
  language: "sql",
  label: "Migration Script"
})

Behavior

  1. Subagent calls message tool with content
  2. OpenCode captures and displays content directly in TUI (verbatim)
  3. Main agent still receives subagent's return value for context awareness
  4. Message content is marked as "already displayed" so main agent knows not to
    repeat it

Symmetry with question tool

This mirrors the existing question tool pattern:

  • question: Subagent -> User (input) -> Subagent
  • message: Subagent -> User (output)

Both enable direct subagent-user communication without main agent mediation.

Use Cases

  1. Migration scripts - SQL/schema changes that must be copy-paste ready
  2. Config file generation - YAML/JSON/TOML that shouldn't be narrated
  3. Code generation - Output code blocks without explanation
  4. CLI commands - Exact commands the user should run
  5. Reports/analysis - Structured output the user will export or share

Implementation Notes

  • Permission: Follow question pattern - denied by default, enable with
    permission.message: allow
  • TUI: Display in a distinct block (similar to tool output) with optional
    label
  • Main agent prompt: Inject note like "The following content was already
    displayed to the user via message tool: [truncated preview]"
Originally created by @jcyamacho on GitHub (Jan 13, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request # Feature Request: `message` tool for subagent-to-user direct output ## Problem When a subagent (via `subtask: true` command or Task tool) generates carefully formatted output, the main agent receives it and often reformulates, summarizes, or adds commentary before presenting to the user. There's no way to guarantee verbatim output delivery. **Example scenario:** A subagent generates a SQL migration script that must be exact: ```sql ALTER TABLE users ADD COLUMN last_login TIMESTAMP; CREATE INDEX idx_users_last_login ON users(last_login); UPDATE users SET last_login = created_at WHERE last_login IS NULL; ``` The subagent produces exactly what the user needs. But the main agent receives this and responds with: > "I've generated a migration script for you. It adds a `last_login` column > and creates an index. Here's what it does..." The user wanted the raw SQL to copy-paste, not an explanation of it. ## Proposed Solution Add a `message` tool that subagents can invoke to push content directly to the user, bypassing the main agent's interpretation layer. ### API Design ```typescript message({ content: string, // Content to display to user format?: "text" | "markdown" | "code", // Display hint (default: "text") language?: string, // For format: "code", e.g., "sql", "yaml" label?: string, // Optional header, e.g., "Migration Script" }) ``` ### Usage Example ```markdown --- description: Generate database migration agent: db-expert subtask: true --- Analyze the schema changes needed and generate a migration script. After generating, use the `message` tool to send it directly to the user: message({ content: "<the migration SQL>", format: "code", language: "sql", label: "Migration Script" }) ``` ### Behavior 1. Subagent calls `message` tool with content 2. OpenCode captures and displays content directly in TUI (verbatim) 3. Main agent still receives subagent's return value for context awareness 4. Message content is marked as "already displayed" so main agent knows not to repeat it ## Symmetry with `question` tool This mirrors the existing `question` tool pattern: - `question`: Subagent -> User (input) -> Subagent - `message`: Subagent -> User (output) Both enable direct subagent-user communication without main agent mediation. ## Use Cases 1. **Migration scripts** - SQL/schema changes that must be copy-paste ready 2. **Config file generation** - YAML/JSON/TOML that shouldn't be narrated 3. **Code generation** - Output code blocks without explanation 4. **CLI commands** - Exact commands the user should run 5. **Reports/analysis** - Structured output the user will export or share ## Implementation Notes - **Permission**: Follow `question` pattern - denied by default, enable with `permission.message: allow` - **TUI**: Display in a distinct block (similar to tool output) with optional label - **Main agent prompt**: Inject note like "The following content was already displayed to the user via message tool: [truncated preview]"
yindo added the discussion label 2026-02-16 17:51:07 -05:00
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 discussion
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#5305
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?