Docs · 05 · the dials

Models & permissions.

Which brain does the work, and how much it may do without asking. Both are set globally, overridden per run, and — for models — pinned per agent.

01Picking a model

The Model pill in the composer — and the model picker in the launch wizard — sets the model for a quick session or a whole flow run:

Fable 5 · 1MFrontier — the most capable option.

Opus 4.8 · 1MMost capable Opus, 1M-token context. The default.

Opus 4.8 · 250KSame model, standard context window.

Sonnet 5 · 1MBalanced — strong and cheaper, native 1M context.

Haiku 4.5 · 200KFastest.

AutoLet Claude pick the model.

Availability If Fable 5 isn’t available on your account, Cyboflow greys it out in the picker and any run pinned to it falls back to Opus transparently — runs never fail over model access.

02Fast mode

The Fast pill is an Opus-only toggle for faster output — it does not downgrade to a smaller model. It’s off by default, applies from your next message, and persists on the session.

03Per-agent pins

Inside a flow, each agent can pin its own model in the agent editor — Fable 5, Opus 4.8, Sonnet 5, or Haiku 4.5 — or leave it unset to inherit the run’s model. A pin beats the run model for that agent only. Typical shape: Sonnet for mechanical implement steps, Opus or Fable for planning and review.

04Permission modes

The permission mode decides what agents may do without a trip through your review queue. Set the global default in Settings → Agent Permission Mode; override per run in the launch wizard or live via the composer’s permission pill.

Ask before editsPrompt for each edit. The default — maximum oversight.

Allow editsAuto-allow file edits plus safe reads and git; everything else still asks.

AutoClaude’s native permission classifier decides what’s safe to allow.

Don’t askNo prompts — skip permissions entirely. For worktrees you fully trust the blast radius of.

Whatever the mode, worktree isolation is the backstop: even “Don’t ask” can’t touch main without your merge.

05SDK vs interactive PTY

Cyboflow can drive Claude Code two ways; pick per run with the substrate selector, or force one globally.

SDK (default)The structured chat experience, on the Agent SDK binary bundled inside the app. Supports pause/resume; nothing needed on your PATH.

Interactive (PTY)A real, live claude terminal you can type into mid-run — the CLI you already know, inside the cockpit. Requires claude on your PATH.

Settings → CLI Runtime: Allow SDK (default · pick per run) or Interactive PTY only, which forces every new run onto the live terminal and hides the per-run picker.
Interactive trade-offs today: no pause/resume, and Ship caps at 10 tasks per run instead of 15.