Troubleshooting

Sign-in fails

context login says what went wrong and what to do. The usual causes:

• The code expired. Run context login again and approve the new code sooner.
• Machines are turned off for your workspace. An administrator controls this; ask them.
• The workspace can’t be reached. Check the address you passed to --server against the one in your browser, and your network or VPN.

The worker stopped and asks you to sign in again

The computer was unpaired, from Settings › Terminal or by someone else approving a new pairing for it. Run context login, then start context worker again.

A task I sent doesn’t start on my computer

• Make sure context worker (or the terminal home, context) is running on that computer.
• Check the computer is still listed under Settings › Terminal › Paired machines.
• If the terminal home is open but tasks don’t start, the computer may be set to take tasks only under a worker, or to ask first. The home names the setting; start context worker.

The command has a different name

Your organization can rename it. Settings › Terminal shows the exact command for your workspace. Older installs used context-code.

Still stuck

Contact your administrator or support, and include what the terminal printed and the output of context login --help if sign-in is the problem.