Canonical page: https://tellenze.com/help/agent-reactions

Invite an agent into the conversation

Configure reactions, ask a connected agent, and inspect readiness, execution, and retry states.

Choose when to ask a companion

Agent reactions let you request help from a teammate’s configured local companion in a work-item conversation. Use them to review context, research a question, summarize evidence, or prepare follow-up work. A reaction has a limited workspace context and does not receive filesystem tools or ambient repository context. Use your normal development workflow for repository implementation.

The target must have an enabled, ready reaction profile. You and the target need access to the source project work. Agent reactions currently require a project-owned work item; team-owned work supports ordinary comments. An active teammate who can comment on the shared project work can request a reaction, including from their own companion.

Prepare your personal reaction profile

Open your personal settings and choose Agent reactions.

1. Choose a provider, an already paired Companion installation, and an active Tellenze MCP connection belonging to your account.
2. If you select a Machine profile, use the profile bound to that MCP connection. The selection does not give the reaction filesystem access.
3. Choose Save setup, then read the readiness results. Saving a draft does not enable reactions.
4. Resolve any blockers and choose Enable reactions when the setup is ready.

Check the companion’s Heartbeat and Native sign-in details. An offline companion must reconnect; a provider that needs attention requires its native client sign-in on that computer. The workspace must also permit the provider, client version, and model.

The selection page expects a companion that has already been installed and paired. If the companion list is empty, obtain the supported installation and pairing instructions from the person operating your workspace. Creating a Machine profile alone does not install or pair a companion.

Request help from a conversation

Open the work item’s Conversation tab and choose Ask an agent. Select one member in the picker; it inserts the target mention and @agent. Add a clear instruction after the directive, such as “Check this proposal against the linked procedure and identify missing acceptance criteria,” then post the comment.

Use the picker to establish the target. Typing or pasting a handle alone cannot start a reaction. Keep the question and its relevant source material in the shared work item so the target can access them.

The request displays its provider, target, requester, and current state. Queued, Waiting, Starting, and Working describe progress toward execution. Completed, Failed, Expired, and Cancelled are final states for that attempt. Review the returned discussion output and any linked created items; a completed reaction does not mean the original work item is complete.

Pause, cancel, or retry deliberately

Use Cancel Agent reaction on an active request when the control is available. In personal settings, Pause stops new work and blocks further actions from an in-flight reaction. Resume checks readiness again. Changing an active setup requires confirmation because it cancels the current work. Revoke clears the setup and requires configuration again.

Retry Agent reaction appears only for an eligible attempt. The system checks access, readiness, the original request, and whether the previous attempt already created effects or has an uncertain outcome. Access, source-comment, or Required Context changes can also invalidate active work. Read the failure guidance and existing outputs before retrying or posting a new request.

Understand workspace controls

Administrators use Admin → Agent reactions to control the workspace switch and provider policies. Supported client versions and models are exact values, one per line. Qualification and health are read-only signals; enabling a policy cannot override a closed deployment gate, stale health, or an unqualified provider. Native provider credentials remain on the member’s computer.