Skip to content

docs(control): clarify focus versus lane replacement in operator workflows #799

Description

@Juliusolsson05

When asked to focus A5, the operator clicked A5 in the shared Dispatch index while lane two was focused. [A5, B7, B8, B9] became [A5, A5, B8, B9], hiding B7 until repaired. These were two views of one agent, not newly duplicated processes.

The existing ac_agents_show intent reuse-existing-view is the appropriate route. The skill already describes that distinction, but a concrete multi-lane recipe would better prevent this observed mistake.

Acceptance: show a worked resolve-label-and-window → locate → reuse-existing-view → verify-window recipe; explain that the shared index places into the focused lane even when another lane already displays the agent; make the target lane evident in UI help. Preserve intentional mirrored views.

This is operator-error prevention, not a claim that the app spontaneously duplicated agents. Impact: the user's monitoring layout was unexpectedly changed and required repair.

Environment: macOS, development Electron, two Agent Code windows, external MCP plus computer use, observed 2026-09-05. Exact running build revision was not verified. Refs #793, #795.

Activity

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