Summary
Design documents created by an agent during a chat are easy to lose once the conversation moves on. Users should have one persistent place to find them again without searching chat history or remembering a local workspace path.
First Tree already has the beginnings of the right destination in Context → Documents. The missing product loop is connecting a document created in chat to that library automatically and preserving navigation in both directions.
User story
As a user, when an agent creates a standalone design document in a chat, I want it to appear in a stable document list so I can find, review, and reopen it later.
Proposed experience
- When an agent creates and shares a standalone design-document artifact in a chat, First Tree registers it in the organization document library as a draft.
- The chat message renders a durable document entry point, such as Open document, rather than only a transient workspace-file link.
- Context → Documents is the fixed, organization-scoped index for these documents; do not add another top-level surface.
- Opening a document shows a backlink to its source chat/message. The source chat also links to the library document.
- Publishing a later revision of the same document appends a version instead of creating a duplicate list item.
Scope boundary
- Index explicit, standalone design-document artifacts only.
- Do not treat every Markdown chat message, arbitrary
.md attachment, or temporary agent file as a library document.
- The existing document library remains the canonical review/version surface; chat provides creation context and navigation, not a second document store.
Acceptance criteria
- A design document created and returned by an agent in chat is discoverable from Context → Documents without a separate manual CLI publish step.
- The list exposes the minimum useful metadata: title, current status, last updated time, and source chat.
- The document and source chat link to each other.
- Revisions are grouped under one document identity and use the existing version history.
- Organization isolation and existing document access rules continue to apply.
- Existing document-library filtering and review flows continue to work for chat-originated documents.
- Ordinary chat content and unrelated file attachments are not added to the library.
Current gap
The current docloop implementation provides the library, versioning, review, and first-tree doc publish, but discoverability still depends on an agent or user explicitly publishing the file. A document that is merely generated and shared in chat can therefore remain trapped in chat history or in the producing agent's workspace.
Planning context
- Requested from First Tree dogfooding
- Source chat:
dbc89576-7a7a-422d-aaa7-0d77ac007e14
Summary
Design documents created by an agent during a chat are easy to lose once the conversation moves on. Users should have one persistent place to find them again without searching chat history or remembering a local workspace path.
First Tree already has the beginnings of the right destination in Context → Documents. The missing product loop is connecting a document created in chat to that library automatically and preserving navigation in both directions.
User story
Proposed experience
Scope boundary
.mdattachment, or temporary agent file as a library document.Acceptance criteria
Current gap
The current docloop implementation provides the library, versioning, review, and
first-tree doc publish, but discoverability still depends on an agent or user explicitly publishing the file. A document that is merely generated and shared in chat can therefore remain trapped in chat history or in the producing agent's workspace.Planning context
dbc89576-7a7a-422d-aaa7-0d77ac007e14