Personal access tokens
Issue tokens that let tools such as the OpenInspect MCP server call the API as you, limited to the permissions you grant.
A personal access token is a credential you issue to yourself so a tool on your machine, such as the OpenInspect MCP server or a script, can call the OpenInspect API as you. Each token carries the permissions you grant it and nothing more.
Create a token
- Open Settings › Access tokens and select New token.
- Name the token after the tool or machine that will use it, for example
Work laptop MCP server. - Choose when it expires: 7, 30, 90, or 180 days, or 1 year. Choices longer than your workspace's lifetime cap are left out, and a cap that isn't one of these is offered too. Every token expires.
- Select its permissions. Read-only selects every read permission your role includes and your workspace allows. Grant only what the tool needs.
- Select Create token and copy the token from the dialog.
The token is shown once. OpenInspect stores only a hash of it, so nobody, including administrators, can show it to you again. If you lose it, revoke it and create another.
Tools send the token as an Authorization: Bearer <token> header. Tokens start with oi_pat_, so a leaked one is recognizable.
What a token can do
A token's permissions are always the overlap of the permissions you granted it and the permissions your role has now:
- If your role loses a permission, every token you hold loses it at the same moment.
- If your account is suspended, your tokens stop working.
- The picker lists only permissions your role includes and your workspace allows. Workspace administration permissions, such as managing members, roles, secrets, and integrations, can never be granted to a token.
- Manage skills works only alongside Read skills, so selecting it selects Read skills too.
A token also reaches only the parts of the API that accept tokens: today, specific session, automation, and skill routes explicitly marked to accept them, including every route the MCP server uses. Everything else refuses it, whatever it was granted. A token can never create, list, or revoke tokens, so a leaked token cannot issue itself a replacement.
Within a granted permission, your role still decides what you see. For example, an administrator's token with Read sessions can read the sessions that administrator can read.
Workspace policy
Administrators can set a workspace policy for tokens. It applies to tokens you already hold, not only to new ones:
- When tokens are turned off, every token stops working and New token is hidden. Your tokens are not revoked; they work again once tokens are turned back on.
- A lifetime cap ends a token once it is older than the cap, even if you created it for longer.
- A permission limit narrows every token's permissions and what the picker offers.
Administrators can also revoke any member's tokens.
Manage your tokens
Settings › Access tokens lists each token's name, the first characters of its value, its permissions, when it was last used, and when it stops working, including an earlier end set by a workspace lifetime cap. Last use is recorded to the minute.
Select Revoke to stop a token immediately. Revoking deletes the token; anything still using it gets 401 Unauthorized.
Creating and revoking tokens is recorded in the audit log. Requests made with a token are attributed to you and to the token that made them.
Linear
Start OpenInspect sessions by mentioning or assigning the Linear Agent on an issue, follow progress in Linear, and control model and repository selection.
MCP server
Let Claude Code or another MCP client investigate sessions and automation runs, and optionally create and run automations or import skills, through a personal access token.