How to Enable Ultracode in Claude Code

Updated October 30, 2026 · covers Claude Code v2.1.284+

There are four ways in, depending on how often you want it: once per task, once per session, at launch, or always. All four drive the same dynamic-workflows engine — they differ only in scope.

On the Pro plan?

Enable the "Dynamic workflows" row in /config first. Without it, the Ultracode toggle won't appear.

Method 1: the `ultracode` keyword (one task)

Type the word ultracode anywhere inside your prompt:

ultracode audit the auth module for injection risks

That single task runs as a multi-agent workflow; the rest of the session behaves normally
Plain language works too — "use a workflow" triggers the same thing
It only fires when you type it at an interactive prompt. It's inert from claude -p, SDK calls, scheduled tasks, and webhook/PR-comment payloads
To dismiss the keyword highlight without running it: Option+W (macOS) or Alt+W (Windows/Linux)

Method 2: the session toggle (recommended)

This is the main switch. In an interactive Claude Code session:

/effort ultracode

Or open the effort menu with /effort and press Tab to flip the Ultracode toggle, then Enter to apply.

With it on, Claude decides which tasks warrant orchestration for the rest of the session — one request may even chain several workflows (understand → implement → verify). Turn it off with:

/effort ultracode off

Version note: before v2.1.284 (Sept 2026), enabling Ultracode forced effort to xhigh and /effort ultracode off failed with "Invalid argument". Update if you hit either.

Method 3: the launch flag

claude --effort ultracode

Starts the session with Ultracode already on — and, unlike Method 2, this flag also sets effort to xhigh. Handy for dedicated deep-work sessions where you want maximum reasoning and orchestration from minute one.

Method 4: always on via settings

To start every session with Ultracode enabled, add it to your settings file (~/.claude/settings.json globally, or .claude/settings.json per project):

{
  "ultracode": true
}

Think twice before doing this globally: with the toggle always on, you'll draw down usage limits much faster even on days of small tasks. Project-scoped settings on your heavy-refactor repos are the safer bet.

Turning it off (fully)

Just this session: /effort ultracode off
Kill the keyword trigger: disable "Ultracode keyword trigger" in /config
Disable workflows entirely: "disableWorkflows": true in settings (or managed settings), or launch with CLAUDE_CODE_DISABLE_WORKFLOWS=1. This removes /workflows, workflow commands, and Ultracode itself; in-progress runs finish.

Permissions during workflows

Workflows still respect your permission mode:

Auto: prompts once on first launch — and is skipped entirely when Ultracode is on
Manual / accept-edits: prompts per run unless you pick "don't ask again"
Bypass / headless: never prompts — gate workflows with a Workflow allow rule or a PreToolUse hook instead