Method: CLI (engine) · blocked-upstream
Warp ships a standalone Warp Agent CLI (works in tmux), and the app claims a large base ("nearly 1M developers," vendor, 2026-04-28) — but the integration surface is undiscovered: the app stores agent conversations in a SQLite blob column with an undocumented format (~/.local/state/warp-terminal/warp.sqlite, agent_conversations), and where the standalone Agent CLI logs, if anywhere, is unknown.
The trigger: someone records real Agent CLI sessions and finds a readable on-disk format, or Warp documents one. If you use Warp Agent CLI daily and want this, the recording is the contribution — comment here.
Method: CLI (engine) · blocked-upstream
Warp ships a standalone Warp Agent CLI (works in tmux), and the app claims a large base ("nearly 1M developers," vendor, 2026-04-28) — but the integration surface is undiscovered: the app stores agent conversations in a SQLite blob column with an undocumented format (
~/.local/state/warp-terminal/warp.sqlite,agent_conversations), and where the standalone Agent CLI logs, if anywhere, is unknown.The trigger: someone records real Agent CLI sessions and finds a readable on-disk format, or Warp documents one. If you use Warp Agent CLI daily and want this, the recording is the contribution — comment here.