CrafterOps
App info

Coming Soon · Mac

A quieter place for studio operations.

CrafterOps is a Mac app in development: one native window for the work a solo developer hands to AI agents. Issues, routines, goals, approvals and notes sit together, and the records are stored on your Mac.

A drawing, not a screenshot. It uses the current build’s own words and colours: the first issue of a project called Studio, with the lead agent and the first task the setup suggests. Costs and Settings are left out.

What is in the current build

CrafterOps is still being built. These are the parts the current build is organised around. Names and details may change before release.

Work
An inbox, issues and goals, with a page for each project. An issue takes its identifier from the project’s name, such as STU‑1, and a status from Backlog to Done. Routines, marked Beta, are named jobs you assign to an agent.
Agents
Each agent has a page for its instructions, skills, configuration and past runs, and a place in an org chart.
Approvals
A queue for the decisions that stay yours, not a prompt for every command. A request can be approved, rejected or sent back for revision, with a note if you want one, and the decision goes into the activity log.
Documents
A vault of Markdown files, kept as ordinary .md files in folders on your Mac, so any editor can open them. It starts with notes, prompts, outputs and briefs, and has search, an editor and a preview.
Chat
A side panel for talking to one agent at a time while the work stays in view. ⌘⇧C opens and closes it.
Activity
A running log of what was created, changed and decided.

How a workspace starts

The current build opens with a short setup. These are its steps, with its own wording in quotation marks.

  1. Name your project“The company or project your agents will work for.” Goals are optional.
  2. Set up your adapter“The CLI that powers your agents”: Claude Code, Codex or a custom process, with a check that it is installed and responding.
  3. Choose your lead agentA name and a role, CEO or PM. Left blank, the agent is called Atlas.
  4. Give it something to doA first task: “a bug fix, a research question, a script”.
  5. Ready to launchThe setup creates the project, the agent and the first issue, and opens that issue. It is the one in the drawing above.

How agents run

CrafterOps has no AI model of its own. It is being built to start the command-line agents already installed on your Mac, such as Claude Code or Codex, and to keep the work around them in one place.

In the current code, a message in the chat panel becomes one command. What the command prints is the reply, and it is kept as a run on the agent’s page. CrafterOps has no sign-in of its own and no field for an API key: the tool it starts uses the account you have already set up for it.

A tool started this way may use the network and sees much of the app’s environment. Review the tool and its prompt before you run it.

What we can say today

There is no price, no release date and no download yet, and how CrafterOps will be distributed is still open. This page describes build 26.0.0, from August 2026. Nothing on it is a promise of a feature.

Your records
Operations records live in a local SwiftData database and Markdown documents in a local vault under your user account. The current build uses no cloud persistence or account service.
Native
Written in SwiftUI for macOS 26, with no web view inside and no third-party code.
Tracking
No advertising, analytics, cookies or third-party tracking SDKs.
What it is not
Not a code editor or a terminal, and not a way to run coding sessions side by side: it has no worktrees and no diff view. Not a cloud service. It makes no promise of a company that runs itself.

To ask when it will be available, or anything else: CrafterOps support · Privacy details