Skip to main content

​
Tilde auth.md

Tilde authenticates four kinds of caller: operators, automation, agents, and end users. Each uses its own credential, and none can stand in for another. Full details are at https://trytilde.ai/docs/iam and https://trytilde.ai/docs/operator-access.

​
Operators

Operators use the Tilde UI and management API. In Tilde Cloud and Tilde Enterprise, they sign in through your OIDC identity provider, with the authorization code flow and PKCE. Sessions last eight hours, and signing out revokes them. Roles decide what each operator can see and change. Tilde OSS has no operator roles, management API keys, or OIDC configuration, and no operator sign-in: the UI and management API accept every request that reaches them. You must protect them with a reverse proxy or another authentication method.

​
Automation

CI pipelines and scripts call the management API with a management API key, sent as Authorization: Bearer <key>. In Tilde Cloud and Tilde Enterprise, a key holds roles exactly as a person does, is shown once, and is stored only as a hash. In Tilde OSS, a pipeline registers deployments with the agent’s own deployment registration key.

​
Agents

  • A deployment token lets an agent replica connect to the gateway and wait for work. It grants nothing else. Set it as TILDE_DEPLOYMENT_TOKEN.
  • For each invocation, the gateway issues a signed token that lasts five minutes. It carries the agent’s capabilities and assigned inference connections. The SDK renews it while the invocation is active, and renewal can only narrow its authority.
  • Agents never receive provider credentials or operator credentials.

​
Tool servers

A self-hosted Tilde tool server connects with a tool server token, set as TILDE_TOOL_HOST_TOKEN. Tilde shows it once, and you can rotate it.

​
End users

End users talk to agents through chat channels, identified by a channel identity such as an email address or phone number. Each channel connection is private, public, or disabled. Your own apps post to native Tilde chat with scoped ingress tokens, which your server requests on the user’s behalf.