Actual Trajectory Replay
Portable Agent does not treat a model response as success.
It creates isolated work, lets the LLM inspect and modify the repository,
measures the result with an external Guard,
retries when necessary, and only then advances to an
Accepted Checkpoint.
Isolated Worktree
The human repository stays untouched while the agent works.
External Guard
Success is measured outside the model.
Checkpoint Ownership
The LLM may change artifacts. Portable Agent owns the commit transition.
Explicit Lifecycle
Work is created, accepted, and closed as separate operations.
A real v0.7.0 end-to-end run
The sequence below is based on an actual Portable Agent run.
In v0.7.0, the Work Definition (.pa) and the Execution Engine (--agent) are fully decoupled. You can also see the Agent's local trajectory clearly using Tool Protocol debugging.
The first attempt failed its Guard, the next attempt corrected the artifact,
and only then did the trajectory reach Gate ACCEPT.
v0.7.0 Update
3 Trajectory Entry Modes
上記のログで使用されている --mode takeover をはじめ、v0.7.0ではタスクの進行状況や障害復旧に合わせて3つのエントリーモードを選択できるようになりました。
start
─────▶
Success / Clean
─────▶
Complete
Next Task
takeover
─────▶
Complete
If Guard Failed
recover
─────▶
Complete
start
まっさらなWorktreeから新規タスクを開始するデフォルトのモードです。
recover
Guardで失敗したArtifactから再開し、初期プロジェクトエージェントを再実行せずに検証からリトライします。
takeover
成功した現在のWorktreeを初期状態として、新しいタスクや別のAgentによる作業を引き継いで開始します。
Agent side
The agent produced and accepted a changed artifact inside its isolated worktree.
README.md:
# customer-system
status: step12
Accepted Checkpoint:
7f60c4f...
Human side
The human-owned main branch remained exactly where it started.
main
HEAD: f9a81f1
README.md:
# customer-system
unchanged