Prokop is an open-source agentic coding workspace for persistent agents, parallel sessions, and projects that keep their context.
Website · Get Started · Documentation · Releases · Chrome Extension
Most coding agents are capable inside one session. Prokop improves the work around and between sessions.
- Persistent agents: Give recurring agents their own memory, skills, and searchable history across projects.
- Separate context: Agent context follows the agent. Project context stays with the project. Both remain editable.
- Parallel work: Run multiple sessions and projects without a desktop full of terminal windows.
- Complete workspace: Work with files, diffs, Git, terminals, tools, and permissions in one interface.
- Desktop and phone: Use the same responsive PWA through networking you control.
- Open stack: No required Prokop account, no telemetry, Apache 2.0.
macOS / Linux
curl -fsSL https://prokopai.dev/install.sh | bashWindows PowerShell
irm https://prokopai.dev/install.ps1 | iexThen run:
prokop initThis prepares Prokop, starts the daemon, and opens the client at http://localhost:8742. See Getting Started for provider setup.
Persistent agent
├── Memory and skills
└── Searchable history across projects
Project A
└── Project-specific memory and skills
Project B
└── Project-specific memory and skills
Promote a reusable profile to create a persistent agent with its own home workspace. Memory and skills remain visible as files. Search can cover the current session, one workspace, or the agent's history across projects.
Reflection is user-directed. You choose the prompt and schedule. Prokop does not automatically learn from every session or train model weights.
| Area | Capabilities |
|---|---|
| Workspace | Session board, cross-workspace Overview, files, editor, Git, diffs, persistent terminals |
| Agents | Persistent identity, memory, skills, session search, subagents, workflows, scheduled work |
| Control | Visible tool calls, scoped permissions, auto-approval boundaries, revocable grants |
| Client | Responsive PWA, mobile layout, push support, multi-server connections |
| Tools | Filesystem, search, shell, tasks, questions, web fetch, Git worktrees, opt-in browser tools |
| Extensibility | MCP and Capek plugins for providers, tools, memory, workflows, and agent behavior |
The board displays up to six open session panes. The server is not limited to six sessions.
Direct support: OpenAI, OpenRouter, DeepSeek, MiniMax, Zhipu, Zhipu Coding, and Codex subscription authentication.
Anthropic and Google models may be available through OpenRouter, but Prokop has no direct integrations for those providers.
Prokop is the coding workspace: server, client, sessions, projects, agents, terminals, permissions, and schedules.
Capek is the separately maintained plugin-based agent runtime underneath it.
Both are written in TypeScript and run on Bun.
Prokop runs on infrastructure you control, with no required account or telemetry. Your configured model provider still receives the requests sent to it.
The daemon survives closing the browser or terminal, not host sleep, reboot, power loss, or process failure. Remote access requires your own networking, such as Tailscale. Local operation alone is not automatic security hardening.
Prokop is evolving and maintained by one developer. It is used for real daily work, but is not presented as enterprise-ready or production-hardened.