aki-mcp-sv 1.15: drive Postman automatically from the panel
aki-mcp-sv moves from 1.12 to 1.15 with a CDP-driven Postman controller: auto-clicking Approve/Run, toggling Thinking and Auto-run, tracking weekly AI credits, and summarizing a chat for handoff.
Four consecutive releases 1.12 → 1.15 turn aki-mcp-sv from a tool-only MCP server into a Postman app-control layer built into the panel. The biggest milestone lands in 1.14: a Launch button starts a daemon that drives Postman over the Chrome DevTools Protocol. Before that, 1.12 added the Postman connector and a streamable bridge, and 1.13 prefilled the Postman MCP JSON config and restored ChatGPT Developer mode.
How does aki-mcp-sv control Postman?
The Launch button on the Postman tab starts or attaches a background daemon in scripts/aki-pmcontrol/ that drives the Postman desktop app over CDP. The daemon auto-clicks Approve / Continue / Run / Try again and toggles Thinking and Auto-run — exactly the actions you repeat while running an agent inside Postman. Quit stops the daemon; New window asks it to open another Postman window.
Neither the daemon nor the panel launch path runs at npm start. A new read-only MCP tool, postman_status, only reports whether it is attached. SIGINT/SIGTERM plus the ~/.aki/cdp-postman/daemon.pid file let panel Quit or Ctrl+C stop the daemon even when it was started from a standalone checkout.
Tracking AI usage inside the chat
Version 1.15 adds a context-length bar at the foot of the Postman chat: green, amber, red by conversation size in KB and characters, signaling when a chat has grown long enough to start a new one (default thresholds 80K/150K characters). Alongside it sits a weekly AI-credit reset countdown ("Resets in Xd Yh") next to the used and limit numbers.
Every chat turn also logs a usage delta to a JSONL file (~/.aki/cdp-postman/usage-turns.jsonl) — one row per turn, for offline validation of the usage signal.
Summarize a chat to open a new one
The Summarize this chat button sends a shared summarize prompt into the chat so the model writes a handoff summary you carry into a new chat, wrapped in a four-backtick code block so it copies in one click. Instruction prompts now live under $AKI_DATA_DIR/prompts/<provider>.md, sharing one data source with the main MCP server.
The whole control surface is opt-in: it never runs at boot, and postman_status only reads, never acts. See aki-mcp-sv 1.11 and the MCP server launch for the full arc of the project.