Forkara is a free, open-source, local-first desktop workspace and control plane for coding agents. It brings provider sessions, tasks, terminals, browser work, diffs, Git worktrees, handoffs, automations, and pull-request delivery into one application. Your repositories and workspace data stay on your machine, and Forkara uses the provider accounts you already have.
Forkara is early-stage software. APIs and interface details are still evolving.
Projects define the workspace; threads preserve task-specific conversations, state, files, and history.
- Multi-provider workspace — use Claude Code, Codex, OpenCode, Cursor, Antigravity, Grok Build, Kilo Code, Pi, and Factory Droid from one app.
- Parallel agents — run tasks in isolated Git worktrees and watch native subagents and workflows with live phases and pause/stop controls.
- Plan and Debug modes — ask an agent to propose before executing or use an evidence-first debug loop without changing runtime permissions.
- Persistent thread goals — attach a multi-turn objective with pause/resume, achievement history, and bounded autonomous continuation.
| Surface | Purpose |
|---|---|
| Changes | Inspect diffs, changed files, and review state. |
| Terminal | Run commands in the project environment. |
| Browser | Keep local previews and the in-chat browser next to the thread, with semantic or page-declared WebMCP tools for agents. |
| Files / Editor | Browse, inspect, and edit project files in context. |
| Git | Work with branches, commits, pushes, and pull requests. |
Split views, browser previews, and device previews keep execution and verification connected to the task that produced them.
Forkara is an MCP-native agent harness in two directions: supported agents running inside Forkara receive tools to coordinate tasks and automations, while Codex, Claude, and other local MCP clients can connect through a scoped integration.
- Handoffs and orchestration — continue a task with another provider, or schedule recurring agent runs with automations.
- Review and delivery — inspect diffs, verify in the browser, commit, push, open pull requests, and review or merge without leaving the app.
- External MCP — pair local MCP clients through a scoped, revocable integration. See External MCP integrations for setup and permission boundaries.
Download the desktop app from Forkara Releases.
To run the current source as a contributor:
git clone https://github.com/redxzeta/forkara.git
cd forkara
bun install --frozen-lockfile
bun run dev:contributorContributor mode uses repository-local data and non-default ports, so it can run beside an installed
Forkara app. Try the setup without starting services with
bun run dev:contributor -- --dry-run.
Provider credentials are optional for ordinary UI and unit-test work. Install and authenticate a supported provider only when you need to start a real agent session or test a live provider integration. Forkara does not include a model subscription; provider authentication, model access, and usage limits remain with that provider.
See the development guide for supported tool versions, repository structure, focused tests, and the pull-request base branch.
bun run typecheck uses TypeScript 7 with the native Effect checker for the TypeScript workspaces. The Astro marketing workspace retains astro check to validate its .astro files. Installation patches the native checker; the root check also reapplies the patch before running. TypeScript 5 remains installed for build tools and bun run typecheck:legacy. Native and legacy checks use separate caches.
The native Effect checker does not currently enforce every legacy diagnostic, including importFromBarrel. bun run architecture:check remains mandatory; use the legacy check when investigating diagnostic differences. bun run typecheck:native is an alias for the default check.
- Quickstart
- Core concepts
- Providers
- External MCP integrations
- Canonical architecture — current runtime boundaries, state ownership, and #174 migration scope
- X integration
- Development and testing
- Downstream rebrand guide
Forkara runs as the workspace layer on your machine. There is no Forkara cloud holding your repositories, chats, or project history. Provider traffic goes directly to the provider you choose.
Focused contributions are welcome. Small bug fixes, tests, and documentation changes can be opened
directly. Please start with an accepted issue before building a feature, architectural change, or
other likely size:L work.
Current contributor-ready work:
good first issue: #145 — restore a visible keyboard focus indicator for message actions.help wanted: #146 — remove runtime Google Fonts requests.
Read CONTRIBUTING.md for the issue-claim and review process. Ask support questions in GitHub Discussions, and report security concerns privately as described in SECURITY.md.
Forkara began as a clone of T3Code, but it has since become a substantially different product with its own branding, packaging, release system, provider orchestration, desktop app behavior, and product direction.
Forkara is licensed under the MIT License.