Milestones

List view

• Upstream advance: T3 Code v0.1.7

  The next upstream advance, to stable T3 Code v0.1.7 (released 2026-11-04). Covers everything since v0.1.3, including linked environments. What the advance has to handle is tracked in #772.

  No due date

  •1/9 issues closed
  11% complete8 open1 closed

• Mobile catch-up

  Bring the native J5 mobile app (iOS/Android) back to working order and catch it up with web and desktop: gaps, build and test infrastructure for agents, live testing, then the build-out.

  No due date

  •26/37 issues closed
  70% complete11 open26 closed

• Playbooks v2: one owner, flexible staffing

  Playbooks v2: the agent in my conversation owns each run and picks who does each step at runtime, so a playbook no longer needs a Crew. Each run keeps its own copy of the playbook. A step's persona is a requirement. Approval checkpoints are enforced. Cancelling stops whoever holds the step. Only Owners save, and a library copy can override a team-folder playbook. Each issue says which item it is (#795 is item 1). Build them in this order: 1. #795 (each run keeps its own copy) ships first. It includes the upgrade migration. 2. After #795, in any order: - #787 (revising an active run); - #788 (the owner hands each step to someone). Coordinate with Crews #745: whichever lands second makes a handed-off step start a waiting member. - #790 (approval checkpoints), which also needs Crews #747. 3. #789 (cancellation and archive), which needs #788. 4. #791 (progress shows the current step), which needs #788 and #790. 5. #792 (required personas), which needs #788 and #790, plus Personas #778, #781, and #782. 6. #793 (owner instructions) lands last, once #787, #788, #789, #790, and #792 are in. 7. #794 (saving and overriding) doesn't depend on any of these and can land any time.

  No due date

  •0/9 issues closed
  0% complete9 open0 closed

• Personas v2: simpler specialists

  Personas v2: agents pick saved personas on their own, within limits set by who picked them. Each persona gets an ordered model list and one of three access levels. Persona runs no longer owe a handoff file. Reviewers prefer a model that didn't write the work. People can switch a worker's model. Edits made in conversation save as overrides on this server. Order: 1. #776 ships first, on its own. 2. #777, #778, and #779 ship together in one release. 3. #780 (monorepo PR) lands once that release is out. 4. #781 ships with or before Crews #743 (auto-approve and additions without approval). 5. After #781, in any order: - #782 (reviewer preference), which needs #778; - #783 (model switching), which needs #779; - #784 (seat replacement), which needs #782; - #785 (escalation and Allow this once), which needs #778; - #786 (editing in conversation), which only needs #779. Deferred: the approved-fallback-models setting, syncing overrides across servers, and proving persona instructions reach Cursor, OpenCode, Pi, and ACP.

  No due date

  •4/11 issues closed
  36% complete7 open4 closed

• V3: Collab sharing enhancements

  Shared UX state and everything else set aside past the MVP.

  No due date

  •0/11 issues closed
  0% complete11 open0 closed

• Memos

  docs/j5/product/features/memos.md

  No due date
  0% complete0 open0 closed

• Roles

  docs/j5/product/features/roles.md

  No due date
  0% complete0 open0 closed

• Fleet observability

  The Fleet page and the reads it needs: docs/j5/product/features/sidebar-and-roster.md (contract on PR #107)

  No due date

  •1/3 issues closed
  33% complete2 open1 closed