Conversation
Root setup points at login or tools MCP; connect is scoped to domain MCP. Co-authored-by: Cursor <cursoragent@cursor.com>
Connect's user-visible journal named ~/.aisa/key even when AISA_API_KEY or the CLI store was authoritative. Manual file-read warnings now apply to users and agents; bundled VS Code may still read the compatibility mirror. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agents following CLI help previously saw the compatibility key file described as the credential source, and
aisa connectadvertised as the general starting point. Help and manifest now describe CLI-managed OAuth/static-key credentials, the explicit environment override andaisa balanceverification; the root separates CLI login/the general four-tool Router from optional domain MCP setup.The connect journal reports a semantic source instead of a credential path or value. Manual-copy guidance is corrected while the CLI and bundled VS Code integration retain their existing credential-handling behavior. Changes are concentrated in
src/commands/tool-help.ts, auth after-help, connect/flow copy and the Skill-init template; authentication and billing implementations are unchanged.Validation: build and74 focused help/skills/connect/flow/config tests passed. Final CI passed Node18/20/22/24/26. This PR does not publish a new npm version or certify OAuth refresh against the live provider.
Companions: Skill #53, Docs #105, landing #108, domain MCP #5. Use the normal CLI release process after merge so npm users receive the new help.