Getting started.
Download it, sign in to an agent, point Cyboflow at a repo, and take one run from first prompt to merged diff. Cyboflow runs on macOS and Windows.
01Prerequisites
- A supported machine. macOS 13 Ventura or later, Apple Silicon or Intel. Or Windows 10 or 11, 64-bit. The build is x64 only, and there is no arm64 Windows build.
- git, installed and carrying a user.name and user.email. A session needs git for its worktree. First run puts a prerequisite card in front of you until both are set, though you can dismiss it and carry on.
- A login for at least one agent. Claude, through your Claude Code login, or Codex, through your ChatGPT account. Neither needs anything on your PATH. How auth works has the one exception.
- Somewhere to work. A local git repo to point it at, or an empty directory that Cyboflow creates and runs git init in.
02Install and updates
On macOS, download the DMG from the download page, arm64 for Apple Silicon or x64 for Intel, and drag Cyboflow into /Applications. Builds are Developer ID-signed and Apple-notarized, so Gatekeeper opens them without an unidentified-developer warning.
On Windows, download the .exe installer and run it. It is code-signed through Azure Artifact Signing under the publisher name Raimundo Esteva, so SmartScreen names the publisher. It may still show a reputation prompt while that publisher is new.
03First run
When you first set up the app, it takes you through a structured onboarding that connects your subscription providers, sets your default preferences, and sets up your first project. You can skip it at any time and go straight to the app.
Before you start your first session you need at least Claude or Codex connected as a provider, and one project added.
To run the onboarding again later, use Settings → General → Onboarding → Replay walkthrough.
04Start a session
The launcher is a three-step wizard: project, then workflow, then configure. Opened from inside a project, it skips the project step. The workflow step opens on three featured cards, above an or run a workflow divider.
- Start a quick session lets you drive an agent yourself, with no structured flow around it.
- Ultracode opens an interactive session in ultracode mode. It is not a structured flow either. It defaults to Fable 5.1 It defaults to Fable 5.1 when that model is available to you and you have set no default launch model of your own..
- Design opens design mode, which prototypes against the real codebase.
Below the divider sit the five flows, in the order the launcher lists them. Each one is covered in the built-in flows.
Verify Setup is not in this list. You start it from the Verify Queue, which is the surface it configures, or from a project’s overview.
The configure step sets runtime and mode, model, and permission mode. A quick session adds reasoning effort. A built-in flow adds a tuning level and a runtime mix.
A quick session’s Advanced section holds Workspace, the base branch, and, on Claude, MCP servers and Plugins. Workspace offers Use global setting, Own worktree, and In place (project checkout). A flow’s Advanced section holds the base branch, Quality eval, Visual verification, and Orchestration.
A worktree is the default. Sessions and worktrees covers what the isolation does. An in-place session works straight in your checkout, and a flow launched from one still opens in its own worktree-backed session.
05Where you get pulled in
How much an agent may do before it stops and asks you is one setting with four modes.
- Ask before edits, the built-in default, stops the agent before each edit.
- Allow edits lets edits, safe reads, and git through without asking.
- Auto hands the decision to Claude’s native classifier. Other runtimes map the same label onto their own gating.
- Don’t ask runs with no permission prompts at all.
Whatever the mode, the agent’s own questions still reach you. Full behavior per provider is on permission modes.
Requests from every running agent in every project land on the app’s landing page, headed Human review queue, with a count of what is waiting on you underneath.
You approve or reject a permission request in place. A decision gate carries Answer →, which takes you into the run where the gate lives. See the review queue.
06Ship the result
A run that reaches its human gate shows a summary panel in place of the run view. It reads Ready for review while the gate is still open, and Workflow complete or Workflow failed once the run has settled. The panel splits token usage into Input, Output, Cache write, and Cache read.
Sprint and Ship runs also carry an advisory Score summary from the code-review eval, which is on by default at Settings → AI → Session settings → Code Review Eval. A failed run shows none.
Read the changes in the rail’s Diff tab, then use the close-out bar.
-
Merge
The Merge session changes dialog offers Squash merge, which combines all commits into one, or Preserve commits, which replays them onto the default branch. If the branch’s work is already in that branch, the merge comes back with a Nothing left to merge notice carrying a Mark session complete button.
-
Create PR
Pushes the branch and opens GitHub’s compare page in your browser. You open the pull request there.
-
Dismiss
Removes the worktree, force-deletes the session branch, and archives the session. Your default branch is untouched.
Merging writes into the project’s effective default branch, which is not necessarily one named main. If that branch has moved under you, the merge is refused with Rebase required before merging. Cyboflow does not rebase on your behalf.
Sprint runs each task in its own lane. Merging a sprint moves the tasks of every lane that reached integrated to Done, and lanes that failed, were blocked, or never started revert to the stage they came from. The mechanics are on shipping a session.
07How auth works
Cyboflow bundles the Claude Agent SDK and the Codex CLI, so the SDK runtimes need nothing on your PATH. They borrow the login your Claude Code or ChatGPT sign-in already established. There is no API-key field anywhere in the app.
The Claude Interactive (CLI) runtime spawns the real claude binary. It looks on your PATH, or at the custom path you set at Settings → General → Advanced Options → Custom Claude Installation.
Defaults differ by surface: flow runs start on Claude SDK, and new quick sessions start on Claude Interactive (CLI). Both are covered under runtimes.
08Settings at a glance
The dialog is titled Cyboflow Settings and holds seven tabs.
Updates and Integrations act immediately. The other five tabs need Save Changes.
09Keyboard shortcuts
Eight remappable global chords ship bound. A session adds a few fixed ones of its own, covered in sessions and worktrees. Windows uses Ctrl in place of ⌘.
Remap any of them at Settings → Shortcuts: click a binding, press the new combination, Escape cancels. A binding must carry ⌘ (Ctrl on Windows) or it is refused with Needs ⌘…, and ⇧⌘R and ⌥⌘R stay reserved for Reload and Force Reload. Changes apply on Save Changes.
⌘' works only inside a session, and is three-state there. It opens the dock and focuses the composer, focuses the composer when the dock is already open, and collapses the dock when the composer already has focus. On the review queue, the backlog, and Insights it does nothing.