Alan Docs

Missing artifact

Find a plan, test report, document, or whiteboard that isn't where you expect.

If a plan or report is missing, check its task or session, archived artifacts, and the conversation where it was written.

Find it

Open Artifacts on the right task or session

On a task, open Artifacts in the right-hand panel. A standalone session (one that isn't part of a task) has its own Artifacts panel. Make sure you're in the team and task you expect; an artifact made in another session or task is listed there instead.

Check Archived

Archived artifacts are hidden from the main list. Expand Archived (n) at the bottom of the panel, then use … → Restore to bring one back.

Look in the conversation

Artifacts an agent creates also appear as a card in the conversation, at the turn that made them. Select the card to open it, then note which task or session it belongs to.

Check it was ever an artifact

If the agent wrote it only as a chat message, ask the agent to save it as an artifact.

Recreate it

Ask in the same session, so the agent still has the context:

Save the plan you wrote above as a plan artifact on this task.

For a test report, ask the agent to create a test report with the evidence it already gathered. You can also create one yourself from Artifacts with New. Then check it appears in Artifacts before moving on.

Look for pull request reviews under Alan Review on the pull request. Starting a review also creates a document artifact when the pull request has a primary linked task. See Review work.

Prevent it

  • Ask for an artifact by type ("a plan artifact", "a test report"), not just a summary in chat.
  • Run sessions from the task they belong to, so their artifacts land on that task.

Next steps

On this page