Skip to content

Stop requiring a licence token managed Intelligence no longer issues - #362

Merged
davidmckayv merged 1 commit into
mainfrom
license-token-no-longer-required
Sep 4, 2026
Merged

Stop requiring a licence token managed Intelligence no longer issues#362
davidmckayv merged 1 commit into
mainfrom
license-token-no-longer-required

Conversation

@davidmckayv

Copy link
Copy Markdown
Contributor

Managed Intelligence derives entitlement from the project key and issues no licence token, so asking for a second credential sent people hunting for something that no longer exists. This repository was the loudest remaining source of that story.

What changed

runtimeCapabilities() required all four Intelligence values. Now three: INTELLIGENCE_API_URL, INTELLIGENCE_GATEWAY_WS_URL, INTELLIGENCE_API_KEY. COPILOTKIT_LICENSE_TOKEN is optional and still forwarded to the runtime when set, which a self-hosted Intelligence with its own licence needs. @copilotkit/runtime itself declares licenseToken optional.

The chart failed harder than the docs. secret.yaml and validation.yaml both required secrets.licenseToken, so a managed-Intelligence install was blocked at helm install rather than merely misdocumented.

Then every surface that taught the two-key setup: prompt.txt, .env.example, README.md, docs/{configuration,development,deployment}.md, charts/openbot/README.md, and the start.sh failure hint that told people to run license --write.

Dropped the fake licence from the CI smoke, so CI now proves boot without one.

Dependency bump

@copilotkit/runtime and @copilotkit/react-core 1.69.0 → 1.70.1, which moved @ag-ui/* to 0.0.59. The old 0.0.57 pins in server/package.json and app/package.json left two copies of @ag-ui/client and split AbstractAgent into incompatible declarations, breaking typecheck.

Verification

  • Typecheck exit 0 on server, app, worker
  • Lint clean, 511 files
  • 2153 pass, 18 skip, 0 fail
  • Build exit 0 on all workspaces
  • Chart renders and passes check-rendered-chart.ts both with and without a licence: zero licence references when unset, three when set
  • Booted the server with COPILOTKIT_LICENSE_TOKEN absent from the env file: /health 200, /api/copilotkit/info 200, licenseStatus still valid, all three Bots registered, so the start.sh gate passes
  • Red-green: restoring the token to the required set makes the two new config tests fail

Managed Intelligence derives entitlement from the project key, so there is no
second credential to fetch. This repository was the loudest remaining source of
the two-key story: runtimeCapabilities() refused to boot without
COPILOTKIT_LICENSE_TOKEN, and prompt.txt, .env.example, the README, three docs
and the chart all taught people to go and find one.

The token is now optional everywhere and still forwarded when set, which is what
a self-hosted Intelligence with its own licence needs.

The chart failed harder than the docs did: secret.yaml and validation.yaml both
required secrets.licenseToken, so a managed-Intelligence install was blocked
outright rather than merely misdocumented.

Also bumps @copilotkit/runtime and react-core to 1.70.1, which moved @ag-ui/*
to 0.0.59; leaving the old 0.0.57 pins split AbstractAgent into two
incompatible declarations and broke typecheck.
@davidmckayv
davidmckayv merged commit f6bc8db into main Sep 4, 2026
14 checks passed
@davidmckayv
davidmckayv deleted the license-token-no-longer-required branch September 4, 2026 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants