Creytix
Request a seat
Creytix ShipLive

GitForge Shared Threads

Same-screen presence + continuous agent thread board — angles, commit trailers, LIVE_STATUS. Not Cursor Glass teleport.

Note

Creytix Shared Thread is the same operational screen for people who keep their own Cursor and clones. It does not teleport Cursor Glass chats.

Overview

Open GitForge on the Control Panel (:3025) to see LIVE_STATUS presence, open Shared Threads with angles, and the fusion board. Each developer still uses their own Cursor; they attach to a thread via continue bootstrap after git pull.

How it works

  1. Threads live as git-backed JSON under docs/fleet/gitforge/SHARED_THREADS/.
  2. Soft angles[] describe intent + pathspecs; preferred branch is feat/<threadId>-<angleId>-….
  3. Commit trailers (Creytix-Thread / Creytix-Angle) come from npm run creytix:gitforge:commit-intent.
  4. Append from the CP form writes the same board JSON. Commit/push of that file is still a release-lane / RT-05 step. No SSE yet — use Refresh board or git pull.

Steps

  1. •

    Open GitForge

    Control Panel → Ship → GitForge · or http://localhost:3025/app/ship/gitforge.

  2. •

    Attach in a new Cursor chat

    npm run creytix:gitforge:shared-thread -- continue --id=st-…

    Paste the bootstrap into a new Agent chat. Do not expect Glass history to move.

  3. •

    Claim an angle

    npm run creytix:gitforge:shared-thread -- angle list --id=st-…
npm run creytix:gitforge:commit-intent -- --thread=st-… --angle=ang-…

Limits & honest scope

  • Not Cursor Origin global sync and not Glass teleport.
  • Append updates disk JSON; it does not auto-push.
  • Accounts multi-tenant filter on this panel is deferred (SAC-P2-04).
  • Live SSE/WS is deferred (SAC-P2-03).

Related

  • Ship overview
  • Spec: docs/creytix/CREYTIX_SHARED_AGENT_CHAT_SPEC.md

Have a code from email or QR?