wellactually

Getting started

Sign in and sync

You sign in on this website with GitHub, and then connect each machine your agent runs on. After that the plugin keeps the machine in step with your advisory board by itself.

Sign in on the website#

Choose sign in at the top right and continue with GitHub. Your GitHub handle becomes your handle here, and your profile is at /e/<handle>. Signing in is free and asks GitHub for nothing but your public profile.

Connect a machine#

Run the plugin's login skill in your agent: /wellactually:login in Claude Code, $wellactually:login in Codex, @wellactually-login in OpenCode or /skill:wellactually-login in pi. The agent shows you a link and a code:

Open https://wellactually.dev/device?code=ABCD-EFGH
and confirm the code ABCD-EFGH

Open the link, check that the browser shows the same code and confirm it. The skill waits for that, then downloads your advisory board right away and tells you how many principles are on it.

What the machine gets#

Login stores a token in ~/.wellactually on this machine. The token downloads your advisory board, sends detection counts and ratings, and uploads drafts of your own principles. It can also start a sync of a repository you connected, which releases what changed unless the repository leaves drafts. It cannot release a draft, change your advisory board or touch anything of anyone else.

Every connected machine is listed on your advisory board under connected machines, with the date it was last used. Revoke takes a machine's access away at once.

CI and cloud agents#

A CI runner or a cloud agent starts on a fresh machine every run, where nobody is there to confirm a code. Give it a token instead:

  1. Open your advisory board, name the token after where it runs under connected machines, and choose Create token.
  2. Copy the token. It is shown only this once.
  3. Store it as the secret WELLACTUALLY_TOKEN where the agent runs, for instance in the repository's secrets or the cloud environment's variables.

With WELLACTUALLY_TOKEN set, the plugin and the wellactually command use it instead of a login and store it nowhere. Run wellactually sync, or the plugin's sync skill, at the start of a run so the advisory board is there before the agent works. Ratings the agent gives reach the experts like those from your own machine.

The token can do what a login's token can, and nothing more. It is listed under connected machines with its name, and Revoke stops it at once.

Syncing#

Signing in syncs once right away, and after that the plugin syncs in the background whenever a session starts, in Claude Code and in Codex. A sync downloads what the experts and collections on your advisory board released since the last one, checks each download against its hash, and removes what left your board.

So you rarely sync by hand. Do it after you change your advisory board in the middle of a session: /wellactually:sync in Claude Code, $wellactually:sync in Codex, @wellactually-sync in OpenCode or /skill:wellactually-sync in pi.