Hequbing · Articles
← All articles

Task Passport: handing a task between Claude, Codex and DSH

2026-10-02By Hequbing (He Fangsheng)3 min read#Task Passport#Task protocols#Benxiang Protocol

Changing AI tools should not require introducing a task all over again. I built Task Passport to move continuity out of a single chat window: Claude, Codex or DeepSeek Harness (DSH) can read the same task state and continue working.

This article covers the v0.2.2 development record dated 14 August 2026. When I checked the public repository on 2 October 2026, its README also described TaskPack for cross-machine handoffs. Use the Task Passport repository for current installation, versions and integrations.

A passport stores task state

Each task has a stable short ID, such as TP-7K4M-9D2Q. The handoff centers on six things: goal, current state, verified facts, decisions and reasons, artifact references, and next steps. The next AI does not need to infer which decisions remain valid from a long conversation.

Code stays in Git, documents stay in project directories, and images and build outputs keep their own locations. The passport stores references and state rather than embedding the whole project. A previous AI's guess must not become verified just because it appears in a handoff. Hypotheses and verification conditions remain distinct.

How a handoff works

  1. The first AI opens the task ID and reads its goal, version and next action.
  2. It completes some work and records artifacts, checks and remaining tasks.
  3. It submits a checkpoint using the version read at opening.
  4. The next AI opens the same task and continues from updated state.

The requirement is one authoritative store. Claude writing one directory while DSH writes another creates two passports with the same name, and progress can diverge.

Why expected_version matters

Suppose Claude and DSH both open version 4. Claude saves version 5 with expected_version=4. DSH then tries to save using old version 4: the store should return a conflict and reject it.

This prevents old state from silently overwriting new evidence. After a conflict, reread the current version and inspect the differences rather than automatically accepting the last save.

Integrations and later extensions

The v0.2.2 record described a native DSH bundle, general CLI, standard-input/output MCP interface and third-party WorkBuddy/CodeBuddy plugins. State could be hosted by U-King Action Core, a local reference store or another provider.

The current README distinguishes a resident passport from a one-time TaskPack: the passport stays in its store and pack/land carries a handoff. Machine-dependent verification needs reassessment on another machine. Package contents do not automatically grant permission to execute them.

What it does not replace

Task Passport does not synchronize Git, store secrets or make every tool compatible automatically. Files, model access, permissions and integrations still need their own configuration.

Task Passport and U-King are independent community projects. See U-King installation lessons and Benxiang's state and evidence layer (Chinese).

By Hequbing (He Fangsheng / Dosen). English edition prepared on 2 October 2026, based on my WeChat article (Chinese). Original illustrations and publication records are available there.

Contact: WeChat hecare888; hefangsheng@gmail.com. Services and pricing.