Conversation
added 2 commits
April 11, 2026 20:10
- schema field names: tool_profile_add/remove → profile_add/profile_remove - remove invalid notification_routing from project-level config reference - add discord-ops init subcommand documentation - add serve flags (--allowed-origin, --allow-unauthenticated) - document bot persona profile_add/profile_remove fields - update version references from v0.14.0 to v0.23.0
…setups When a global config contains projects from multiple orgs, the server now starts successfully even if some projects are missing their token_env in the current environment. Projects with missing tokens are logged as warnings and marked unavailable; only when all projects lack tokens does startup fail. validateConfig() likewise downgrades per-project missing token_env from errors to warnings, since the server can still serve other projects. Resolves #86
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
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.
Summary
loadConfig()now only throws a fatal error when all projects are missing tokens — if some have valid tokens the server starts and warns about unavailable onesvalidateConfig()downgrades missing-but-configuredtoken_envfromerrors[]towarnings[]Behavior change
Before: Any missing
token_envin the global config caused a fatal startup error, even for projects from completely unrelated orgs.After:
list_projectssurfaces missing tokens as warnings, not errorsTest plan
npm test— 932 tests, all passnpm run typecheck— cleannpm run lint— clean