Projects

When an effort outgrows one session, give it a project. Everything an agent writes for that pipeline, model, or deployment collects in one place you can browse like a folder of files.

Availability

Set a project up

1. Create a project

   New Project asks for a name and a description. Keep it to one project per pipeline, model, benchmark, or deployment effort. The list carries search and a refresh, and each row has pin, copy ID, and delete — pin the effort you are on and it stays at the top.

2. Point an agent at it

   Projects fill up from the agent side. Tell Claude Code, Codex, or Kimi which project to write into and the Wingman MCP document tools do the rest: create_document for something new, update_document to revise it. Paste the project ID from the row action when the agent asks which project it is working in.

Read what the agent wrote

1. Browse it like a folder

   Opening a project shows folders and files. Agents name documents like paths, so apps/pool_safety.py and configs/region.json land in an apps and a configs folder, and anything named without a path sits at the root. Open a folder to go deeper; the breadcrumb and your browser Back button walk you out again. The Filter this folder box narrows a long list without leaving it.

2. Open a document

   Open a file and it takes the screen — headings, tables, and code blocks all render, and the breadcrumb tells you where you are. Documents are read-only here: the agent writes them, you read them. To change one, ask the agent.

3. Send it to the editor

   In the desktop app, Open in editor — or a double-click on the row — hands the document to the editor beside the chat panel, so you can read it next to your own code. It opens read-only there too, because the document lives in the project rather than on your disk. In a plain browser the action is not offered and the in-app viewer is the whole story.

What belongs in a project

A project is the durable half of an effort and the session is the working half. Anything you would be sorry to lose when the session ends belongs in a document; anything you are mid-thought on belongs in the chat panel. Ask for the write-up before you close the session, not after.

Tasks and work orders are retired