Open source · Apache 2.0
Coding agents that remember how you work.
Prokop is an open-source agentic coding workspace. Persistent agents keep their own memory, skills, and searchable history across projects, while each project keeps its context separate and inspectable.
the problem
Your coding agent is smart.
Its working environment is still temporary.
Six sessions become six windows.
Parallel work turns into terminal management. The desktop becomes the job.
Every project starts from zero.
Context lives inside one session. Close it and the decisions, fixes, and conventions evaporate.
The new session has never met you.
Re-explain your stack, your conventions, your preferences. Every time. To a capable stranger.
Remote means a chat bridge.
Check in from your phone and you get a stripped-down bot, not your actual workspace.
continuity
Stop briefing a stranger every session.
Promote a profile into a persistent agent and it gets a home, its own memory, its own skills, and history that follows it across projects. Project knowledge stays in the project. Plain files, on your disk, you can read and edit.
Works in every project. It knows you, not just this repo.
Separate on purpose. Your repo's quirks don't leak into other work.
Full-text search over past sessions. Recover decisions instead of redoing them.
Skills preserve repeatable ways of working. Write them, or let the agent propose them.
You define the reflection prompt and schedule. You decide what gets kept.
not model training · markdown files on disk · read, version, edit, delete
the workspace
Run the work, not the windows.
Sessions, projects, files, Git changes, terminals, and permissions in one focused interface. Any number of sessions running; the board keeps six live panes in view.
Board
Parallel sessions side by side. Six live panes, no window management.
Workspaces
Multiple projects with fast switching, plus an Overview that aggregates sessions across them.
Files and diffs
Direct file access, editing, Git changes, and reviewable diffs in the interface.
Terminals
Persistent terminals for long tasks. Keep talking while commands run.
Permissions
Every tool call visible. Approve one action, the session, or the workspace.
Schedules
Recurring agent sessions. Review runs and reflection jobs on your cadence.
the scale
As plain as a CLI. As far as you want.
Everything is opt-in, per workspace. One project and a plain agent is a perfectly good setup. Turn capabilities on only if you want them.
01 / bare
One project. A plain agent.
Read, edit, grep, run. No memory, no skills, no search. Nothing runs that you didn't turn on. Start working immediately.
- single workspace
- built-in coding tools
- nothing else on
02 / wired
The agent starts to know you.
Turn capabilities on per workspace. Memory that survives sessions. Skills that capture repeatable work. Full-text search over every session you've run.
- memory on
- skills on
- session search on
- scheduled jobs
03 / full send
A whole operation on one machine.
Session panel, six live sessions on the board, files alongside. Multiple workspaces under one Overview. Persistent agents with their own homes and memories, any number of sessions running, long tasks in background terminals while you keep working.
- board: six live panes
- multi-workspace overview
- persistent agents
- background terminals
on your phone
Not a Telegram bot. Your actual workspace.
The client is a mobile-optimized PWA served by Prokop itself. Same sessions, same agents, same history, same permissions. Mobile reorganizes the interface into one surface at a time. It does not reduce the product to a chat bridge.
- The same agents and their memory, from anywhere
- Approve permission requests from your phone
- Push notifications when long runs finish
- Reach it privately through networking you choose, like Tailscale
Prokop ships the PWA, auth, and optional TLS. The network is yours.
in control
Familiar does not mean opaque.
Every tool execution is visible. Diffs land in the interface. Permission requests show the action, the risk, the resource, and the intent before you grant anything.
Scopes you can revoke. Auto-approval boundaries you set per session or workspace.
Edits arrive as diffs. Files, memory, and prompts stay inspectable.
yours
The working relationship stays yours.
The full stack is open source, Apache 2.0. Server and client. It runs as a daemon on your machine, independent of the browser or terminal. No account, no telemetry, no cloud gate between you and your workspace.
Open all the way through
Not open-core. The server, the client, the tools, the scheduler. Apache 2.0.
Files, not a database mystery
Memory, skills, and prompts are plain files on your disk. Version them, share them, delete them.
Bring your own models
Direct support for OpenAI, OpenRouter, DeepSeek, MiniMax, Zhipu, and Zhipu Coding, plus Codex subscription auth.
Extensible by design
MCP tools over stdio or OAuth, browser automation, git worktrees. Tools appear alongside the built-ins.
more models through openrouter, including anthropic and google families
install
Bring your next project into Prokop.
One command, then prokop init. The daemon starts, the client opens, you pick a model and start working. Everything else is opt-in.