Results for “mako-code”

Claude knows what you changed between turns: files edited outside Claude are named (with small diffs) beside your next prompt, and an optional cheap review flags slips in your own edits.

Runs the tests related to each change (Claude's edits and yours) in the background; a failure caused by Claude's edit reaches Claude mid-turn, and the band offers Show and Fix it.

Say "this error", "the tests", "this file", "what you just did" or "the plan" and what it points at goes along with your prompt: the failing output, the test failures, the file, the diff, the plan. No model calls, size-capped, never twice, and Remove takes it back.

Keeps work flowing: when Claude stops mid-task ("Next I'll…") or asks an obvious yes ("Shall I continue?"), a 5-second countdown you can stop sends a short continue. Never for choices, missing info or risky steps.

Every prompt you type gets a quiet second read: without changing your words, a hidden note gives Claude the goal in one line, the likely scope, the project's checks to keep green, and what done means. Haiku only for vague prompts; See, Undo and Off in the band.

A quick second pair of eyes after edits: reviews the turn's diff in the background and offers to fix what it finds.

Runs your linter on every file Claude edits and hands the errors back with the edit's result, so Claude fixes them right away.

Notices when Claude is stuck repeating itself (same failing call, same output, edit flip-flops, failure streaks) and tells it to change approach.

A prompt queue that runs itself: line up prompts with /queue and they run one after another, pausing when Claude asks you something or a turn fails.

Sharper retries after a failed turn: when checks still fail, Claude gives up, errors loop, or you say "that didn't work", haiku drafts a retry with the lesson, a different approach and the exact failing output. One click sends it.

No lazy placeholders: flags TODOs, '... rest of code', NotImplemented stubs and empty bodies an edit introduces, nudges Claude to finish them, and lists what is left.

One prompt, several jobs: when a prompt you type holds independent tasks (a list, numbered steps, "do A, then B, and also C"), offers to run them one by one as their own turns, stopping at the first that fails or asks you something.

Caps runaway turns: asks, stops or warns when one turn passes a step, time or cost limit.

Runs your project's checks after Claude edits, shows pass/fail above the prompt, and closes the loop with one-press (or automatic, bounded) fixes.

The Gobworks manager: browse every mod by category, see what each does and costs, turn mods and presets on or off, and check them. Best standalone in any terminal (gobworks); inside a running Claude Code session too (/mods).

A little game layer: 32 achievements for how you use Claude Code, with lifetime progress and a /achievements pane.

Something to do during long turns: /snake and /2048 in a pane, with high scores and a nudge when Claude is done.

Gob as a Tamagotchi-style companion who lives off your work: finished turns, green tests and commits grow him, and /pet lets you feed, play with, pet, nap and dress him. Free, and he never punishes you.

Opt-in: after a long turn, hear one spoken sentence about what Claude did.

A chime, a toast and an optional webhook when Claude finishes a long turn or needs your permission.

Themed words for the waiting line (pirate, space, kitchen, ...) plus live output speed and step count.

Shows when you sent each prompt ([14:32]) and when each turn finished.

Jev (TypeSafe's System One model) as Claude's instant co-processor: bulk filter/classify/rank/semantic-grep tools, risk notes under permission dialogs, a check on unverified 'it passes' claims, and optional per-prompt effort.

Opt-in instant approval for clearly harmless shell commands: a strict pre-filter, then Jev classifies the command; only read-only inspection at ≥ 97% with no network risk skips the permission dialog. Every approval is logged.