@ctrl-spc/cs

The cs command keeps your computer online for CTRL+SPC so your coding agents can be reached, and opens the Companion — a small local app for signing in and attaching your codebases to your projects.

Install

npm i -g @ctrl-spc/cs
cs

Running cs opens your browser straight to sign-in — you barely touch the terminal:

Welcome to CTRL+SPC — opening your browser to sign in…

In the browser you'll:

1. Sign in (or sign up on the web).
2. Attach a codebase — point a project at a folder on this computer that has a git remote.
3. Open the web app — create work items and hand them to an agent.

Your folder paths stay on this computer; only path-free identifiers (a git remote URL) are shared.

Stay online

cs autostart on

Comes online automatically at login, with no window. Turn it off with cs autostart off.

Commands

cs                Open the Companion app (the front door)
cs open           Open the Companion app in your browser
cs login          Sign in from the terminal and link this computer
cs start          Come online now, no window (used by auto-start)
cs status         Inspect this service, its running version and cloud connection
cs stop           Stop this service when no owned work is active
cs restart        Load the installed CLI and keep it running in the background
cs stop --force   Interrupt owned work, preserve recovery, then stop
cs restart --force Interrupt owned work, then load the installed CLI
cs autostart on   Come online automatically at login
cs autostart off  Stop coming online at login
cs logout         Sign this computer out
cs help           Show this help

Requirements

• Node.js >= 22.
• Service stop and restart support macOS and Windows.

Updating and restarting

Installing a package does not replace a service already running in memory. On the computer you want to update, run:

npm install -g @ctrl-spc/cs
cs restart
cs status

cs status separates the version of the installed command from the verified version running in the service. A successful restart stays running after the terminal closes. cs stop leaves the computer's next-login startup preference unchanged; cs autostart off changes that future preference.

A normal stop or restart refuses while an assignment is active. Let the work finish, or explicitly use --force to interrupt the owned assignments. Saved files and conversations remain; open each interrupted card and send a new message to continue. Restarting the service does not automatically replay work.

Local service controls remain available without a cloud connection or usable sign-in. Cloud readiness is reported separately. An offline interruption appears in the app after the service can reconnect and reconcile it.

One-time upgrade from an older service

A service installed before these lifecycle controls cannot prove which work is still running. The new command prepares the future-login launcher and explains when a one-time computer restart is required. Save your work, restart that computer, then run cs status after signing in. If automatic startup is off, run cs start first. Interrupted work needs an explicit new message to continue.

Later service stop and restart do not need a computer restart. If ownership or execution cannot be verified, the command reports that problem and does not start a second service.

The app's Restart worker control reconnects work processing inside the current service. Activating an installed CLI update uses cs restart in a terminal on the named computer.

Not sure what a piece does? Open the Companion (cs) and click How it works.