About

About Jack

Jack is a free macOS IDE built around AI coding agents instead of a text cursor. Claude Code, OpenAI Codex and Google Gemini share the same workspaces, editor, git, terminals, services, databases and browser. Agents from different vendors review each other in Rooms, plans run unattended through the night, and every tool call still passes through you, from the desk, the floating HUD, or your phone. The whole app stays local: no account required for local features, telemetry off by default. Jack is built and maintained by Oglut Srl.

Who builds Jack

Jack is a product of Oglut Srl, an Italian software company (VAT IT15766701005) building developer tools. The company also publishes the open Provider SDK that lets third parties wire their own agents into Jack, and the Gemini provider that ships in the box is built on it.

• Legal entity: Oglut Srl, Italy — VAT IT15766701005
• Website: oglut.com
• GitHub organization: github.com/ottimis
• Provider SDK: github.com/ottimis/JACK-provider-sdk

How Jack got here

Jack started as a native macOS GUI for the Claude Code CLI: a real diff instead of terminal scrollback, a conflict resolver, a permission inbox on your phone. It then became multi-provider, with OpenAI Codex and Google Gemini plugging into the same contract. Today it is an IDE: tabs and split panes, a CodeMirror editor with symbol navigation, a git history and review tab, terminals and a services panel, a Docker cockpit, database connections, an allowlisted browser the agent drives, a test vault and a test mailbox. On top of that sit the coordination surfaces no single vendor will ship: Rooms where Claude and Codex deliberate, run plans that survive usage limits, a timeline of the cooperation committed to git by the host.

What Jack is

• A workbench. Everything the agent touches, you can open, read, edit, diff and commit in the same window. You can still use your usual editor; you no longer have to.
• A tool host. Forty-two host tools over MCP, identical for every provider: databases, containers, terminals, services, browser, vault, mailbox, git proposals, todos, data tables, rooms, wake-ups. Reads on by default; dangerous writes behind a switch and a card.
• A supervisor's console. Permission cards with scoped always-allow, a floating HUD, a cockpit across workspaces, a triage queue that clears itself to what still needs you, a mobile companion.
• A coordination layer made of files. AGENTS.md and _shared/ are the protocol; Activities, handoffs, Rooms, run plans and the Timeline sit on top and stay readable outside Jack.

What Jack is not

• Not an orchestrator. No DAG editor, no graph runtime, no manager agent that removes you from the loop. Rooms are opened by you; plans are queued by you; Play cards are pressed by you.
• Not a hosted service for your code. Sessions run on your machine, talking directly to the provider you chose. Jack keeps its metadata in SQLite under ~/Library/Application Support/jack/ and secrets in the OS secret store.
• Not a proprietary protocol. Roles are plain agent.md files. Cross-agent boundaries pass through _shared/specs/, _shared/api/, _shared/decisions/. Exported browser runs are plain Playwright specs.
• Not finished. macOS only, single user, no LSP, Rooms verified on two of three vendors, mobile parity a backlog. The site says so where it matters.

Open contracts

The Jack runtime is closed today. The contracts that let providers plug in are open and MIT on npm:

• @ottimis/jack-provider-sdk — provider plugin contract; write a third-party provider without seeing Jack's main process
• @ottimis/jack-chat-core — the normalized message model every provider speaks

The Provider guide walks through both architectural patterns (agent-as-runtime and agent-as-reasoning-layer with the client executing tools via JSON-RPC). Third-party providers get the same UX, permissions, host tools and usage chip as the bundled three. Third-party plugins are trusted by version, and a version bump asks again.

Pricing

Everything that runs on a single machine is free, forever. A free Jack account is optional and adds account-based phone pairing and beta features; a feature you are not entitled to is invisible, never a disabled button with an upsell. The future Team layer adds Rooms and handoffs across machines, inline review comments, shared coordination backup and audit as a per-seat add-on, built on the same primitives, opt-in.

Contact

For commercial enquiries or Provider SDK partnerships, see oglut.com. Bug reports and feature requests can be sent from inside the app.

← Back to home