Skip to content

/plannotator-last feedback uses Build instead of the annotated message agent #1612

Closed

Description

@balaji-dutt

On AI assistance: OpenCode (GPT-6 Sol) helped me narrow down the behavior and draft the wording below, including the repro steps. The actual issue and the workflow are mine. — @balaji-dutt

What happened

I launched OpenCode with opencode-plannotator-custom, switched from the configured default agent (build) to a custom agent I created (agent-engineer), and received a response from Agent-Engineer. I selected that message in /plannotator-last, added an annotation, and clicked Send Feedback. Build answered the feedback, although the annotated message was generated by Agent-Engineer.

In the original session where I noticed this, multiple subsequent responses were from Build and I switched back manually. In a separate reproduction session, Build answered the feedback but the session then returned to Agent-Engineer on its own. The duration of the switch varied; the feedback responder was wrong in both cases.

Steps to reproduce

  1. Configure OpenCode with default_agent: build.
  2. Start a session, select another agent (agent-engineer, a custom agent in my case), and get a response from it.
  3. Run /plannotator-last and select that Agent-Engineer message for annotation.
  4. Add a comment and click Send Feedback, without manually changing agents.
  5. Check which agent answers the feedback.

Expected

The agent that generated the selected message (Agent-Engineer in this example) answers the annotation feedback.

Actual

Build answers the annotation feedback. The sanitized export from the reproduction session shows:

Sequence User-message agent Replying agent
Before annotation agent-engineer agent-engineer
Annotation feedback build build
Following empty command turn (parts: []) agent-engineer agent-engineer
Later normal message agent-engineer agent-engineer

The empty turn and automatic return to Agent-Engineer describe the reproduction session, not the longer-lived Build behavior observed in the original session.

Reproduction session: feedback on an Agent-Engineer message was answered by Build. An Agent-Engineer turn followed; no agent change was made manually during this reproduction.

Environment

  • OpenCode: 1.18.31
  • @plannotator/opencode plugin: 0.27.20
  • Plannotator CLI: 0.27.15
  • Plugin runtime: cli
  • OpenCode default agent: build
  • Agent that generated the annotated message: custom agent-engineer

Plannotator displayed Agent Switching: Disabled during the reproduction. The UI describes this setting as switching after plan approval, so I include it as context rather than assuming it governs /plannotator-last.

Activity

  1. backnotprop commented on Sep 25, 2026

    @backnotprop
    Owner

    Thanks @balaji-dutt, clear repro. It looks like when the OpenCode plugin sends /plannotator-last feedback back into the session, it doesn't say which agent should get it, so OpenCode falls back to your default agent (build). We'll look at routing the feedback to the agent that wrote the annotated message. Separately, your CLI is 0.27.15 while the plugin is 0.27.20; worth updating the CLI too (curl -fsSL https://plannotator.ai/install.sh | bash), though that doesn't explain this bug.

  2. backnotprop commented on Sep 25, 2026

    @backnotprop
    Owner

    Fixed in #1614, thanks @balaji-dutt for the clear repro and the agent-by-turn table. /plannotator-last (and /plannotator-annotate) feedback is now sent to the agent that wrote the annotated message, on the embedded, CLI-bridge and OpenCode 2 paths. It only names an agent OpenCode still lists, and otherwise delivers exactly as before, so feedback is never dropped. One known gap: if you select several messages written by different agents, it still goes to the default agent. Ships in the next release.

  3. added a commit that references this issue on Sep 25, 2026
    0560d59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions