Console

console.codemany.com shows every machine in your fleet in one browser tab: its runners, its recent runs and its cloud machines. From there you can drain, resume or resize a machine without being at it.

What it shows

Your machines: each Mac and Linux machine with Codemany, online or offline, its version, its mode (running, draining or paused) and how many runners are idle, busy or starting.
Targets: the accounts, organizations and repositories each machine runs jobs for, with the runner count for each.
Recent runs: the newest 50 runs per machine, with repository, workflow, branch, status, result and duration, and the jobs that ran there.
Cloud machines that Codemany created for a machine, with provider, region, size and monthly price.

It never shows job logs or code: those stay on the machine. What a machine sends.

Open console.codemany.com and choose Sign in with GitHub. The console asks GitHub only for read:org, to learn which organizations you belong to and your role in them. You see the machines whose seat belongs to your own account or to an organization you can activate Codemany on, and only that owner's targets and runs. A session lasts 1 hour; then you sign in again.

One machine first, then add more

With no machines yet, the console shows one step: Get Codemany on your first machine. Download Codemany, install it on a Mac or a Linux machine, and sign in to GitHub in it with the same account.
Start your trial or subscription. A machine reports only while it holds a seat.
The machine appears in the console by itself, usually within a minute. The page waits for it; no refresh needed.
To add another, choose Add another machine and repeat on that computer. Each machine takes one seat.

On a Mac, the app first shows a one-time notice that the Mac appears at console.codemany.com, with Turn Off and OK. The Mac reports nothing until you answer it. A Linux machine prints the notice in codemany setup and reports right away.

Commands, and who can send them

On a machine's page you can:

Drain: busy jobs finish, no new ones start. Resume takes jobs again.
Stop all runners: busy jobs finish, then the runners stay off until Start runners. Running jobs are never cancelled.
Change runner count: how many jobs the machine runs at once, for the whole machine or one target.
Add cloud machine and Remove cloud machine.

Not everyone who sees a machine can send it commands: only the account the seat belongs to, an organization's admins, and whoever pays for Codemany there. Changing one target's runner count needs that right on the target's owner; commands that reach the whole machine (drain, resume, stop, start, cloud machines) need it on every owner whose seat the machine holds. The machine carries out each command with its own credentials when it next reports, usually within 30 seconds; an offline machine gets it if it comes back within 10 minutes.

Privacy

A machine sends its name, OS and version, runner states, target names, cloud machines and short run and job summaries (names, status and times). It never sends logs, step output, code, file paths, tokens or keys. The console keeps the newest 50 runs and 50 commands per machine and deletes a machine that has been silent for 30 days. Sign-in uses two cookies: one for the GitHub sign-in itself (at most 10 minutes) and one session cookie (1 hour). Full details are in the Privacy Policy.

Turn it off

Reporting is on by default. Turn it off on a machine with any of:

the Mac app: Settings › General › Privacy › Show this machine at console.codemany.com
the machine's dashboard: Settings › Privacy
codemany console off (and codemany console on to turn it back on)

It applies within a minute, with no restart. The machine then sends nothing to the console and shows as offline there.