unofficial fan-made tool · not affiliated with, endorsed by, or connected to heyclicky
^ ω ^ { ^-^ } (¬_¬) ¯\_(ツ)_/¯

cruise control

keeps your ai buddy driving while you're away

get it for mac see how it works

private preview · macos sonoma 14 or higher · heyclicky companion with optional vscode automation

ReasonFileEditWindow
CRUISE

May I bring Reason forward and inspect the export state while you watch?

Hands off the mouse while I drive. Esc stops me.

YOU
Go ahead Not now
approved by cruise control · you're away
CRUISE

three modes

pick one from the notch

cruise control lives right next to your notch whenever heyclicky is open. the dropdown is just three modes and settings. automation, permissions and activity live in a dedicated settings window, with real heyclicky and vscode counts shown separately and saved across restarts.

MANUAL

manual

you're at your desk. clicky asks, you answer. cruise control just watches.

REST

rest area

stepping out but don't want anything moving the mouse? every “may i drive?” gets a polite “not now”.

CRUISE

cruise control

let it cook. every request gets “go ahead” / “let clicky drive”, so long tasks don't stall waiting for you.

keep going

picks up where clicky left off

when a task stops early and clicky drops a full report, cruise control opens it and sends one line back:

“please continue the users request to implement this particular feature based on your findings”

when clicky stalls with a “needs you” card, cruise control closes it, reads the chat, and has a local ollama model write a short nudge for that task. drafts that pretend you approved something never get sent.

when clicky goes quiet, it waits a few minutes, then nudges unfinished work without inventing consent or answering credential questions.

after a restart or interruption, it inspects the task card and sends a polite “pick up where you left off” message—or presses retry if the chat is unavailable. no working status in the notch? it hovers and checks for itself while you're idle.

when heyclicky has an update, it presses update app, waits for the relaunch, and tells the tasks that were interrupted to pick up where they left off.

budgets survive restarts: up to 6 nudges per task per hour, sharing a 10-continue hourly budget and a 90-second minimum gap. the glowing dashboard badge shows cruise mode on every display, above ordinary desktop overlays.

🎛️rippa repair DONE10:55 AM
reason now shows L 3131 / R 3237, but the export did not complete. the save dialog is still open.
Open Rippa 📄 Full report
please continue the users request to implement this particular feature based on your findings
sent by cruise control

optional vscode companion

keep the work moving.
keep the cost in check.

LOCAL REVIEW

screen tool requests

opt in to “always allow in vscode”. a fixed safety filter and local ollama review inspect each request before pressing “allow once”. flagged requests stay for you; temporary review or click failures are retried.

ECONOMY FIRST

mai-code flash first

prefer MAI-Code Flash in the active chat. repeated unresolved failures, a regression, or stalled progress can trigger an escalation suggestion—but a pricier model needs your explicit confirmation. the same chat history stays intact.

TEXT ONLY

a thoughtful follow-up

after five quiet minutes, ollama checks whether the task is actually unfinished. a short, labelled follow-up can help it continue. no screenshots, no draft overwrites, no interrupted tools. fifteen-minute cooldown.

these options start off. local models can miss risks or misread progress: this is assistance, not a security boundary or a guarantee of github's model routing. auto-approval can cause data loss, secret exposure, malicious installs, or real-world side effects. read the warning before enabling it.

install

three steps, then walk away

  1. 1

    build it

    gh repo clone ilovespectra/CruiseControl
cd CruiseControl
./scripts/build-app.sh --install

    private preview: repository access is required. needs GitHub CLI and the Swift command line tools. installs to /Applications with a login agent that keeps it running.

  2. 2

    say yes to two permissions

    accessibility so it can press clicky's buttons, and screen recording as a backup for reading clicky's notch prompt. that's it.

  3. 3

    pick a mode

    tap the pill next to your notch. manual at the desk, rest area or cruise control when you leave. enable vscode features separately if wanted. the green dashboard light means cruise mode is selected—not that permissions or task completion are guaranteed.

notes

clicky asks before it drives your computer. that's the right call when you're sitting there.

but if you kick off a big task and go make coffee, you come back to a prompt that's been waiting twenty minutes and a task that went nowhere.

cruise control is a tiny, opt-in switch for that moment. you decide when it's on. you can flip back to manual from the notch any time, and esc still stops clicky mid-drive.

— the cruise control project

faq

questions

is this made by heyclicky?

no. cruise control is an independent, unofficial project. it isn't affiliated with, endorsed by, or supported by heyclicky or its makers. please don't contact them about it.

does it bypass anything?

no. heyclicky still asks every time. cruise control just answers for you, on your own machine, in the mode you picked. it presses the same button you would.

what does it look at?

heyclicky's windows and, with the vscode options enabled, vscode chat controls and recent conversation text. accessibility reads labels; screen capture is an optional fallback for the heyclicky notch. ollama uses your configured endpoint (localhost by default). no screenshots are automatically sent to chats. it also checks heyclicky's public update feed; this webpage loads fonts from google.

do i need ollama?

for heyclicky nudges, ollama is optional: a plain continuation message is the fallback. vscode approval reviews, task follow-ups, and escalation assessments require a successful ollama response. if the review fails, requests remain pending and the selected model stays unchanged.

can i change the wording it looks for?

yes. button labels, the continue prompt, rate limits and more live in ~/Library/Application Support/CruiseControl/config.json.

how do i stop it?

switch to manual to stop heyclicky task automation and text follow-ups; turn off the separate vscode approval and model toggles to stop those too. “hide” only hides the notch—it does not disable automation. to remove the app and login agent, run ./scripts/build-app.sh --uninstall.