Follow the work linked to a task or doc

Move between a requirement and the agent work that was started from it.

Before you start

Open a task in Tasks or a document in Docs. Linked work is most useful when the agent was started through that item’s Implement action.

This completed demo task retains links to its agent and design. Reimplement starts another draft; it does not mean the previous result was automatically verified.

Step by step

1. Look for the linked agent indicator near the task or document header. Open it to inspect the implementation conversation.

2. Confirm that the conversation refers to the intended requirement. Read the latest response, pending questions, and the reported status.

3. Inspect the resulting files and behavior. A task’s Done label or an agent’s final message is not a substitute for checking the requested outcome.

4. Return to the task or document when you need to compare the implementation with the original description. Use its linked design or pull-request indicators when present.

5. Send corrections in the relevant conversation and keep the requirement up to date when the intended scope changes. If you start another implementation, make the relationship to earlier work explicit.

What to expect

You can trace the requirement, implementation conversation, and relevant result without reconstructing the history from unrelated chats.

Troubleshooting and useful details

If no linked agent is shown, check whether work was started from this exact item or from a separate new-agent request. Similar titles do not prove that two records are linked. A Reimplement action can be available when prior work exists; inspect that work before starting another run. External task statuses and suggested pull-request status changes still need the appropriate review.