Skip to content
General Augment Docs

Identity Linking

General Augment begins with the host app’s trusted identity contract. genaug launch records the app’s token issuer or JWKS URL and stable user claim. Every runtime turn then supplies that stable claim as user; General Augment verifies and resolves it inside the Project before memory or tools are available.

{
  "agent": "support",
  "user": "customer_123",
  "input": "Where is my order?"
}

Do not accept a user ID from an unauthenticated client and forward it as trusted identity. The app backend derives it from the verified session.

Section titled “Operational Links”

When an external surface has its own identity, link it to the existing app user through the v3 operational plane:

Terminal window
genaug user link telegram-user-id \
  --provider telegram \
  --display-name customer_123

This is audited operational state; it does not create a Candidate. Connection declarations and Agent grants remain governed Project desired state.

Runtime Resolution

Section titled “Runtime Resolution”

General Augment resolves the verified Project, app user, session, Agent, and exact release before invoking Hermes. Direct app tools receive signed Project/user/session/release identity from General Augment; the model cannot choose or forge those values.