BasicAgent
Terminal Workspace Checklist
A terminal workspace checklist for persistence, replay, session identity, and resume behavior.
Published: 2026-01-04 · Last updated: 2026-01-04
If a terminal claims to be a workspace, it should pass these checks.
Checklist
- Stable session ID across reconnects.
- Output replay after time away.
- Resume-first behavior (no forced restarts).
- Fast access without heavy IDE startup.
- Resource limits to avoid runaway sessions.
Link up
- Always-On Terminal Workspace: /always-on-terminal-workspace/
- Session Persistence & Output Replay: /session-persistence-output-replay/
- Phone Terminal Codex: /phone-terminal-codex/
Build narrative
Follow a coherent path from thesis to lab notes to proof-of-work instead of isolated pages.
Step 1
Intelligence systems office
The strategic map for what is being built and why.
Step 2
Lab notes
Build footprints and progression logs as proof-of-work.
Step 3
Control surface
Governance and monitoring architecture for operational reliability.
Step 4
Private alignment
Convert insight into execution with scoped collaboration.