Skip to main content

Session continuity

The system treats chat history as temporary workspace. Active engineering state is kept in a small GitHub Issue called an AI Work Packet.

Why this was needed

The earlier loop consumed tokens and required repeated manual copy/paste. The current loop keeps resumable state in the repository-scoped Work Packet.

Owner-facing continuity

For the normal workflow the owner says only:
ChatGPT resolves the target repository, reloads the active Work Packet, rechecks exact Git/GitHub state, and continues implementation directly when the packet authorizes IMPLEMENTER=CHATGPT_CHAT. Cursor에 넘겨줘 is an explicit compatibility opt-in, not the default handoff. ChatGPT may switch the current packet to IMPLEMENTER=CURSOR and use /work-resume only after that explicit request. Cursor 끝났어. 계속 is used only after such an opted-in task.

One packet per workstream

A repository can have several independent active workstreams. Examples:
A Work Packet is not a project diary. It is a current-state record.

Required identity

Its main sections are:

Packet lifecycle

A new independent workstream gets a new Issue. A new chat window does not. Do not create a central cross-project handoff repository. The product repository is the namespace boundary for its own Work Packets.

Fail-closed resume

Cursor and ChatGPT do not guess when the current workstream is ambiguous. The resolver first determines the repository, then requires the matching active packet. If there are zero or multiple valid matches, it stops and asks for the minimum clarification needed. LAST_VERIFIED_HEAD is advisory only. Current Git state must always be rechecked. Work Packet v2 also prevents stale scope and stale implementer authority. Before mutation, ChatGPT refreshes TASK_KIND, OWNER_INTENT, INTENT_REVISION, CHANGE_RISK, and IMPLEMENTER, then verifies that Next Action advances the current intent. Direct ChatGPT mutation requires IMPLEMENTER=CHATGPT_CHAT; Cursor dispatch requires an explicit owner opt-in and IMPLEMENTER=CURSOR. STATUS has only four values: ACTIVE, PAUSED, BLOCKED, and COMPLETE. Values such as CURSOR_READY, WAITING, or DONE are not separate lifecycle states. Readiness is represented by ACTIVE plus a valid Next Action; observable wait conditions belong in Current State/Latest Evidence. Any implementation path requires a usable local shell/process and Git context. Optional Cursor dispatch additionally requires the explicit packet opt-in and its own resource/session gates; failure does not cause a silent fallback to a different repository or stale transcript.

Why GitHub Issue instead of HANDOFF.md

Updating a committed handoff file changes the product source HEAD. For release candidates that require verification of the exact HEAD, changing the committed handoff state can invalidate previous results. Updating an Issue preserves the qualified source revision.

Conversation handoff

When a chat becomes too long, no special Handoff Issue is created and no giant continuation prompt is required. The active Work Packet is updated, and the next conversation can begin with a short request such as:
The new conversation reloads the active Work Packet and current GitHub state instead of replaying the old chat.
Last modified on September 29, 2026