Capek Dev
Capek Dev is best classified as an individual/solo developer project identity rather than a conventional company. Daniel Bilek describes his work as building open-source software he wants to exist; the main project, Prokop, is an open-source, self-hosted agentic coding workspace designed to give coding agents persistent memory, skills, searchable history, project context, and a unified interface across desktop and phone.
At a Glance
- Individual developers
- Open-source developers and maintainers
- Technical teams wanting persistent coding-agent context
- Users who prefer self-hosted, local-first developer tools
- +1 more
AI Tools by Capek Dev
(1)
Prokop
Open Source Agentic Coding Workspace
Discussions
No discussions yet
Be the first to start a discussion about Capek Dev
Latest News
Prokop server 1.17.0 released with experimental memory and skill selection, configurable relevance acceptance, context inspection, expanded memory capacity, and DeepSeek Flash image capability.
Prokop server 1.16.0 released with on-demand archived/scheduled sessions, multiple Codex subscriptions, per-workspace session ordering, workspace sorting, and optional commit hooks.
Prokop server 1.15.0 released with automatic update notices, published-release validation, and separate instance data-directory handling.
Prokop Browser Chrome extension version 1.0.0 updated in the Chrome Web Store.
Products & Services
Open-source Apache-2.0 agentic coding workspace and local daemon. It provides sessions, projects/workspaces, persistent agents, files, Git, diffs, terminals, permissions, schedules, memory, skills, searchable history, workflows, subagents, and a responsive web/PWA client.
Chrome extension that connects browser tabs to a running Prokop server, allowing agents to read visible page content, take screenshots, navigate, click, type, interact with controls, discover elements, and manage tabs.
Separately maintained Bun-native, composable agent runtime containing the runtime, shared contracts, and tool-authoring contracts used by Capek hosts and underlying Prokop.
Market Position
A local-first, open-source alternative to session-centric coding-agent products: rather than focusing only on an agent chat, Prokop packages the surrounding workspace—persistent agent identity, project-scoped memory, parallel sessions, files, Git, terminals, permissions, schedules, and browser access—under user control. Its differentiators are self-hosting, inspectable file-based context, no required account or hosted service, and an integrated desktop/phone client.
Leadership
Founders
Daniel Bilek
Software developer and open-source builder based in Prague. He says he began programming at 16, building console applications, web apps, automations, computers, and client websites, and has worked across frontend and full-stack development, technical leadership, and project management. His public profile lists TypeScript, Go, Python, and PHP and identifies him as Prokop's creator and sole maintainer.
Executive Team
Daniel Bilek
Creator and sole maintainer
Prague-based software developer and open-source builder; background across frontend/full-stack development, technical leadership, project management, and client software work.
Founding Story
Bilek describes a motivation to build software he wants to exist and to keep software on users' computers theirs. Prokop addresses the limitation he saw in session-based coding agents: each new session starts without the prior agent's memory, project conventions, decisions, or reusable procedures. The initial vision was an open-source, self-hosted workspace where persistent agents, project-scoped context, files, Git, terminals, permissions, and schedules live together without a required Prokop account or hosted service.
Business Model
Revenue Model
Open-source, self-hosted software distributed under Apache License 2.0 for Prokop. The project states there is no required Prokop account or hosted Prokop service; users connect their own model providers and credentials.
Target Markets
- Individual developers
- Open-source developers and maintainers
- Technical teams wanting persistent coding-agent context
- Users who prefer self-hosted, local-first developer tools
- Developers working across multiple repositories, sessions, and devices
- Software development with coding agents
- Continuing work across sessions without re-briefing an agent
- Managing multiple projects and parallel coding tasks
- Running agents from a desktop, phone, or another browser on a controlled network
- Preserving project conventions, decisions, reusable procedures, and lessons
- Git-based editing, review, branching, and release workflows