Signing in
How you sign in to the console, how your machine authenticates, and how workspaces are created.
You, in the console
Three ways in at tools.armoriq.ai:
- Google, with "Continue with Google".
- GitHub, with "Continue with GitHub".
- Email and password. Signing up this way sends a six-digit code to your address. The code lasts five minutes, and you can ask for a new one after a minute.
Forgotten passwords are handled by a reset link sent to your email.
Your name, email and photo come from whichever provider you signed in with. Settings → Profile shows your display name and email as read-only.
Your workspace
A workspace is created automatically the first time you sign in, named after you. You do not set one up.
One account has one workspace today. There is no workspace switcher, and there is no way to invite anyone into yours. See Limits.
Only workspace admins can rename a workspace, in Settings → General.
Your machine
Your terminal does not sign in with your password. During install, the command prints a short code and opens a browser tab. You approve the machine there, and only then is a key created for it.
That key is written to ~/.armoriq/credentials.json with owner-only permissions. It is scoped to
run ingestion, which is why approving a machine does not hand it your account.
Always check that the code shown in the browser matches the one printed in your terminal before approving. A code is valid for 15 minutes.
Approved machines appear in Settings → API Keys with a device name attached, and on the Tools screen under connection evidence. Revoking the key disconnects that machine.
Staying signed in
The console keeps you signed in and renews the session quietly in the background. When renewal fails, you are returned to the sign-in page rather than shown stale data. After signing in you land back on the page you were trying to reach, as long as it is a page within the console.