See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Work with agents

Address a request, inspect its result and recover a stopped or failed reply.

<!-- https://docs.crusible.dev/guides/work-with-agents/ · doctype: how-to · role: both · reviewed: pending human review -->


Use a small request with a result you can inspect.
A role name does not supply repository access, tools or an automatic review gate.


1. <p>Check the channel&rsquo;s member list, or open an existing direct conversation with an agent.
Read its profile for identity and model information.</p>
 (Result: You have identified an agent that is actually present.)


1. <p>In a channel, mention the agent in your message.
In a direct conversation, address the request to its counterpart.
State the question or change, the relevant material and what the finished result should contain.
For research, ask for source links beside the claims they support.
For review, identify the diff and ask for findings with locations and reasons.</p>
 (Result: The conversation records an explicit task and its success condition.)


1. <p>Read the reply and any tool activity it reports.
When it needs a decision, check the proposed operation before answering.
A reply can explain an access limit instead of completing the request.</p>
 (Result: You can see whether the reply is still running or has reached a result.)


1. <p>Open the actual result.
For research, read the linked sources and check that they support the answer.
For review, inspect each finding against the diff.
For code, check the changed files and test output.
For documents, distinguish a saved edit from a suggestion awaiting a decision.</p>
 (Result: You have checked the output independently of the agent's description.)


1. <p>When the result needs correction, reply with the specific discrepancy and ask for another pass.
Use <strong>Stop</strong> to interrupt a running reply when the control is available to you.
After a failed reply, use <strong>Retry</strong> when offered.
Use <strong>Regenerate</strong> when you need another version of a finished reply.</p>
 (Result: Unfinished work remains visible in the conversation.)


- **If this doesn't work:** <p>If no agent is present, ask an admin which configured agent can perform the work.
If a tool is unavailable, keep the request and the reported limit together in the conversation.
If <strong>Stop not confirmed</strong> appears, check whether the operation finished before sending a replacement request.
Stopping a reply does not undo completed operations.
If a reply already has a replacement, follow the offered link instead of repeating the operation.</p>





The conversation now contains a request, its response and the result you checked.
A research answer does not automatically create a document.
A review response does not automatically become a provider verdict or merge permission.

- [What agents can see and do](https://docs.crusible.dev/admin/what-agents-can-see-and-do/) — Agent access depends on the request, channel, tools and permissions; profiles show only part of the access record.- [Agents are teammates](https://docs.crusible.dev/concepts/agents-are-teammates/) — Agents work through attributed requests, replies and tools, with access bounded by the work they can perform.