Working with an AI agent

Uclusion keeps the work and its discussion together while your coding agent works in a repository. Start with agent-led setup or connect an existing workspace through MCP.

Prepare the work

Put enough information in the job or bug for someone who has not seen your chat to understand the result you want:

• Describe the problem and the expected outcome. For a bug, include steps to reproduce it and what happened instead.
• Name the repository and any relevant files, attachments, or earlier decisions.
• Include constraints and the verification you want, such as tests, environments, or examples the result should handle.

Use the job’s stage to show its status and assignments to identify the people responsible for decisions. Mark work AI able when you want it to appear in the agent’s work list.

Assignment

Use the job’s short code copy button, then paste the code in your agent message. For example, using the fictitious short code J-Demo-1:

Work on J-Demo-1 in this repository.

If you want help choosing, ask:

Find AI-able work in this workspace.

You can also use Poke AI from Uclusion. When running several agents, give each conversation a clear target. Codex’s recipient-inspection command helps you check where Pokes will arrive. For agents that choose work themselves, consider enabling work claims.

To change the target, name both the current work and the work you want next. This makes the switch clear when the conversation already contains several jobs.

Answer questions where the decision belongs

Reply to a question in Uclusion so the answer stays with the job. When the question offers alternatives, vote for your choice and explain any conditions that affect it. Link earlier decisions when they already answer the question.

If a job is waiting for input, check its questions and current assignees. Questions explains who can answer and what Resolve means. Connected agents receive responses automatically through Poke AI.

Resolve on a question asks the agent to choose. The question stays in its assistance until the agent has handled that choice, including any required change to the current design note. Reopen the question and Resolve it again when you want the agent to choose again.

Review a suggestion’s wording before converting it to a task. Edit it first when the proposal does not describe the work you want.

Review the result

Use the job’s report and current design note to compare the agreed outcome with what was built. Ask for the diff and verification results when you need them. Check the original reproduction steps or acceptance examples, and reply on the review with any remaining issue.

Read the proposed completion actions before approving them. Name the actions you want, such as committing the changes or pushing them to a branch. Ask for an explanation when the proposed action or its scope is unclear.

Reports and notes stay with the work, so later reviewers can follow the decisions and results.

Agents also point out open jobs and bugs that completed work has made duplicate, obsolete or in need of change, and blockers that work may clear, in one linked report in your inbox. The findings, reasons, evidence and proposed actions also stay with each affected item, so later conversations can use them. Agents already working on an affected job can receive the new context without additional human notifications. You decide whether to change or resolve the work and its blockers.

Resume or redirect work

In a fresh conversation, name the job or bug and ask the agent to continue from its latest discussion. Include any new evidence or requirements. Uclusion’s records remain available across conversations; repository changes still need to be available in the checkout the agent uses.

The agent reads the current design note and its discussion together. Before a design note exists, it reads the job and task notes for context. Discussion can inform the work; changes to the agreed outcome belong in the design note itself.

For a fix that still fails, give the work’s short code, reproduction steps, and the observed result. For a new requirement, say how it changes the outcome you previously requested.

When you need background from older work, ask a specific question such as “What did we decide about retaining exported reports?” The workspace export makes past discussions searchable.

Check a session that is not progressing

Check that the client has a connected Uclusion MCP server and the intended workspace. If no work appears, check AI able on the item. If work is waiting, open the job and look for an unanswered question or blocker.

For a Poke that seems to go nowhere, use the client-specific delivery guidance. After an update, restart the client so it loads the installed configuration. For usage or repeated-read investigations, see token usage and response statistics.

Read the skills

The public Uclusion skill and design skill contain the agent instructions and link to their references. The installation paths show where to inspect the copies your client uses.