Paste with Ctrl+Shift+V. Plain Ctrl+V is not a paste in a terminal: it sends a control byte into the machine, and at the hidden key prompt you will not see that it did.
A small Linux computer, running inside this browser tab, with temur already on it. temur is a command line AI agent. Nothing is installed on your own machine, and nothing you do here is uploaded anywhere. To get real answers out of it you need an API key from an AI provider, which you give to the setup wizard in the terminal above.
Into the computer in this tab, and nowhere else. This page has no box to type a key into, and it never reads what you type in the terminal: you are typing into a program running inside the emulated machine, at that program's own prompt. The key is written to a file inside that machine, which exists only in your browser's memory. It is not sent to this site and not saved in your browser's storage.
The wizard asks four things. Enter alone takes the default shown in brackets.
2
or anthropic, 3 or openai,
4 or gemini, 5 or
xai. Do not pick 1 here; there is a question about
that below.
/root/.secrets/.
Then type temur to start the agent, or
temur doctor to check the configuration and the
connection first.
Paste with Ctrl-Shift-V. In a terminal, plain Ctrl-V is not a paste command at all: it sends a single control character to the program you are talking to. At the key prompt the terminal is not showing you what it receives, so a plain Ctrl-V looks exactly like nothing happening, and you can end up with a key that is wrong in a way you never saw.
That is correct, and it is not a hang. The key prompt turns the terminal's echo off, so there are no characters, no dots and no length to look at while you type or paste. Press Enter. temur then prints a line confirming that the key was saved, and it never prints the key itself.
Ctrl-C at any ordinary question leaves the wizard and puts you at
the shell prompt, where temur init starts it again.
At the hidden key prompt, Ctrl-C is ignored on purpose: echo is
off there, and a Ctrl-C at that moment could leave you at a
terminal that has quietly stopped showing what you type. To get
past the key question without answering it, press Enter on the
empty line.
Run temur init --force. It rewrites the
configuration, but it will deliberately not overwrite a key file
that already has a key in it: it prints a line saying the key file
already exists and was left untouched, and then does not ask you
for a key at all. If you are replacing a key, delete the file
first and then run the wizard again:
rm /root/.secrets/temur-anthropic-key
Each provider keeps its key in its own file, so moving to a different provider does not need the old one deleted.
Template 1 points temur at a model server running on the same machine, which is how you would run it against llama.cpp on a real computer, with no key and no provider. In this tab there is nothing listening at that address, so temur would have nothing to talk to. Pick one of the hosted providers instead.
Networked tier is the working state: the emulated machine can reach the provider you picked, through a relay that carries the traffic without being able to read it. OFFLINE TIER means no relay could be reached, so this machine has no network at all. temur still runs and everything local to the machine still works, but any request to a hosted provider will fail. Reloading the page later is worth a try.
The whole computer stops existing, along with its files, the configuration you just made, and your key. Nothing is written to your own disk and nothing is kept here, which is why you have to type the key again next time.
This page runs a small Linux computer inside your browser. When you type an API key, you are typing it into that computer, at the setup wizard's own hidden prompt, not into this web page: there is no key box on this page, and the page never reads what you type into the terminal. Your key stays in that computer's memory.
Requests to your AI provider are encrypted inside that computer before they leave it. They travel through a relay that can see only which provider you are contacting and how many bytes moved. The relay cannot read your key, your prompts, or the replies, and it can only reach the handful of AI providers on its allowlist.
You do not have to take that on trust. The relay's source is published under the AGPL and linked at the bottom of this page, and both the page and the relay show the exact commit they were built from, so what is running here can be checked against what is published.
Nothing is stored. Close or reload this tab and the computer, its memory, and your key are gone. You will type the key again next time, because there is nowhere for it to have been kept.