Authentication

An assistant connected to Teramot always acts as you: it sees the workspaces and projects you are a member of, and can do only what your role in each one allows. There are two ways for it to sign in.

Used by Claude, Claude Code, ChatGPT, GitHub Copilot, Gemini and Microsoft 365 Copilot.

You add the Teramot server URL to your assistant (see Connect an AI assistant).
The assistant opens a browser window on the Teramot sign-in page.
You sign in with your Teramot account. The assistant receives a token and renews it on its own, so you do not have to sign in again every session.

Good to know:

Finish the sign-in within 10 minutes of the window opening. After that the attempt expires and you see “this authorization session has expired or was already used; start the login again” — start the connection again from your assistant.
Only known assistants can complete a sign-in: Claude, ChatGPT, Microsoft 365 / Teams agents, VS Code, and command-line clients that receive the sign-in on your own computer. Any other client is refused with “redirect_uri … is not registered for this server”.

Client ID

Most assistants discover everything they need from the server URL. Only a few ask for a Client ID.

Where: Administration → Connect AI in the sidebar → Advanced configuration, the last panel of the page; click it to expand. It shows the server URL and the Client ID, each with a copy button.

Teramot uses a public sign-in client, so a Client Secret is never needed — if a form insists on one, any value works.

Used by Cursor, v0, Antigravity and any client that can only send a fixed header.

Generate a key

Where: Administration → Connect AI in the sidebar → Access keys, below the assistant cards: the name field and Generate key are at the top of the section.

In the Teramot app, open Administration → Connect AI in the sidebar.
Under Access keys, type a name that tells you where the key is used, for example cursor-work.
Click Generate key and copy the key. It is shown only once.

Keys created this way do not expire; the list shows them with no expiry.

Use a key

Send it in the Authorization header of every request:

Authorization: Bearer <your-key>

The client setup shows where each client takes the header.

Revoke a key

Where: Administration → Connect AI → Access keys → the trash icon at the right of the key’s row.

On the Connect AI page, click the trash icon next to the key and confirm. A client that is already connected may keep working for a few more minutes before it is disconnected.

Access keys are not Project API keys. The same page has a Project API keys section, below Access keys and shown only while a project is selected. Those keys are for calling the Teramot API from your own application and do not work for connecting an AI assistant. Use a key from Access keys.

When access is refused

What the assistant tells you	What it means	What to do
Your session is no longer valid, so “…” could not run. Please sign in again — retrying with the same session will not help.	The sign-in expired or the access key was revoked.	Reconnect Teramot in your assistant, or generate a new access key.
You don’t have permission to run “…” (requires … — minimum role: …). Your current role is “…”. Ask an admin of the workspace for access.	Your role in that workspace or project does not allow the action.	Ask an admin to change your role — see Permissions.
tool “…” is not available on this connector	The tool exists only inside the Teramot app, not for external assistants.	Use the agent in the Teramot app for that task.
The “…” tool failed. Correlation ID: …	Something went wrong on Teramot’s side.	Try again; if it keeps failing, send the correlation ID to support.

Connect an AI assistant Tool reference