Installing the CLI with npm install
EACCES
EACCES
sudo in front.403 Forbidden
403 Forbidden
429 Too Many Requests
429 Too Many Requests
Signing in with praesia request
invite_required
invite_required
rate_limited
rate_limited
This profile already has a badge
This profile already has a badge
- If it’s the agent you’re setting up, ask your agent to read its status.
- For a new agent, ask your agent to use another profile name.
This sign-in link has ended
This sign-in link has ended
Running a tool with praesia call
This agent is not enrolled yet
This agent is not enrolled yet
No agent of this machine has this profile name
No agent of this machine has this profile name
This agent must be set up again on this machine
This agent must be set up again on this machine
Enroll the agent again with another --profile
Enroll the agent again with another --profile
The clock of this machine is off
The clock of this machine is off
The Praesia CLI of this machine needs a check
The Praesia CLI of this machine needs a check
praesia doctor --profile PROFILE_NAME. Then ask your agent to try again.Paying with pay
result: unresolved
result: unresolved
get_status under the same key. Don’t ask it to pay again.Run praesia operations
Run praesia operations
This machine keeps no record of payments
This machine keeps no record of payments
get_status. To keep the record, give your computer account write access to the Praesia home.An operation journal file cannot be read
An operation journal file cannot be read
Updating the CLI
Version X of the Praesia CLI is available
Version X of the Praesia CLI is available
Praesia needs a newer version of the Praesia CLI
Praesia needs a newer version of the Praesia CLI
Starting the server with praesia serve
Your harness runs this command. It shows these messages.
praesia serve takes no --profile option
praesia serve takes no --profile option
The harness cannot start the server
The harness cannot start the server
Checking the setup with praesia doctor
Doctor failed
Doctor failed