Question
The highest-value piece of this map: a wayfinder map rendered inside T3 Code, so working a ticket
does not mean bouncing between the Issues list and the chat.
Settled already: it is wayfinder-specific (not a general issue list), it lives as a right-panel
tab (apps/web/src/components/RightPanelTabs.tsx already registers Browser / Terminal / Files /
Diff / Pull request / Agents), and it is web + desktop only.
Open: what does it actually render, and is it read-only?
- Which parts of the map body — Destination, Decisions-so-far, Not-yet-specified, Out-of-scope?
- How is the frontier shown: open, unblocked, unassigned children? Is blocked-ness visible?
- Does it write — claim a ticket, post a resolution, close, edit fog? Writing needs auth in the
client and turns a viewer into an editor, which is a much larger surface.
- What does it show when the thread has no map?
Build something rough to react to rather than specifying it in prose — this is a "how should it look
and behave" question. Link the prototype from this issue as an asset.
Question
The highest-value piece of this map: a wayfinder map rendered inside T3 Code, so working a ticket
does not mean bouncing between the Issues list and the chat.
Settled already: it is wayfinder-specific (not a general issue list), it lives as a right-panel
tab (
apps/web/src/components/RightPanelTabs.tsxalready registers Browser / Terminal / Files /Diff / Pull request / Agents), and it is web + desktop only.
Open: what does it actually render, and is it read-only?
client and turns a viewer into an editor, which is a much larger surface.
Build something rough to react to rather than specifying it in prose — this is a "how should it look
and behave" question. Link the prototype from this issue as an asset.