One interface, provider-specific contracts.
Use the same terminal and session model while each adapter translates canonical history and tools to the provider's wire format.
Pkwn gives Claude, Codex, and Gemini a shared, persistent operating surface: an interactive terminal, hub-style sessions, and an OpenAI-compatible API.
Direct API turnsno vendor CLI subprocess required
Persistent sessionsresume after restart; search every transcript
Explicit permissionssafe, edit, and full are visible boundaries
Pkwn owns the durable parts of agent work: credentials, transcript history, tool execution, and session identity. Each backend remains its own direct provider connection.
Use the same terminal and session model while each adapter translates canonical history and tools to the provider's wire format.
Sessions and raw transcript events persist in local SQLite databases, including tool results and searchable conversation content.
Loopback binding is the default. A non-loopback daemon requires an API key; permissions govern what the agent may do inside a project.
No hidden cloud control plane. You install the runtime, select the accounts it may use, and keep the daemon where you can operate it.
npm install -g punakawan — no build step, no repo checkout.
Log in only to the providers you intend to use.
Run pkwn; it self-starts its local daemon when needed.
Use the TUI, OpenAI-compatible API, or a persistent session.
Then run pkwn auth login <backend> for each provider you plan to use.
npm install -g punakawan
pkwn initPkwn keeps agent work from becoming a disposable terminal invocation without turning the operating model into a black box.
Attach, resume, stop, remove, and full-text search conversations through the TUI or REST API.
Read session controlCron schedules reuse their own persistent session, and Telegram is an optional client of the daemon API.
Read automationWork in the Ink terminal UI, call an OpenAI-compatible endpoint, connect over WebSocket, or route approved Telegram chats.
Read the APIPkwn's adapters use provider-specific OAuth and direct endpoints. Consumer-account terms, OAuth traffic requirements, and model availability remain vendor-controlled. Review the provider notes before pointing Pkwn at an account you cannot afford to have restricted.
Read provider and exposure notes