Amolfi from your terminal

Amolfi has a command-line client. It installs in one line, and it talks to the same public API, the same governed specialists, and the same approval gate as the app.

npm i -g @amolfi/cli

Signing in comes next, and it is the part most tools get wrong. amolfi login never asks you to copy a key out of a settings page and paste it into a shell where it lives forever in your history.

amolfi login

The terminal prints a link and a short code, then waits. You open the link in the browser where your identity already lives, confirm the code, and pick which workspace this terminal is allowed to reach. Approve, and the credential lands in your operating system’s keychain. The terminal tells you which workspace it now holds and nothing else. One token, one workspace.

After that, the verb that matters is ask.

amolfi ask "draft the october email from what actually shipped"

That hands a goal to your AI workforce and follows it. A run id comes back immediately, then the activity prints line by line as the work moves, the same run you would be watching in the app, arriving as text instead of a screen.

Four verbs steer it once it is going. amolfi runs get takes a single snapshot with the status and each specialist’s state. amolfi runs watch follows a run you started earlier. amolfi runs guidance sends a correction mid-flight, which is how you say “shorter” or “use the other template” without throwing the work away and starting again. amolfi runs cancel stops it. The client reads, too: amolfi team names who can approve, amolfi webhooks lists what is registered, amolfi audit walks the log. Each of those needs its own scope on the token you are holding.

Then the run reaches something governed, and the terminal stops.

approval required
  approve or deny at  https://amolfi.com/chat?decision=…

Nothing else happens in that window. The client prints the link and never opens it, exits zero because waiting on an owner is the designed outcome rather than a failure, and offers you nothing further to type. There is no approve verb in the command list, because there is no permission a terminal could hold that would let it approve. The scope does not exist to be granted to anyone.

Engineers have run their whole working lives from a prompt: build, deploy, query, release. The business itself was always the part that lived somewhere else, behind a login and a mouse. Some of it answers here now. You can start real work against your real records without leaving the window you were already in, and the decisions that deserve a person still go and find one.