Repository navigation
Add encrypted Agent defaults and frozen Session execution overrides - #66
Merged
Merged
Conversation
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.
Saved Agents can now store editable model, harness and encrypted model-provider defaults. Session creation resolves explicit overrides, then saved defaults, then deployment defaults, and atomically freezes the effective configuration and private credentials. Agent edits/deletion and operator configuration changes do not alter existing Sessions; idempotent retries recover the original Session without replay.
Provider overrides are complete bundles, so a new endpoint never receives an inherited key. Public responses expose only safe configuration and
api_key_configured. The existing hosted-only credential boundary remains in place. Includes migration 000059, generated OpenAPI/SQL, TypeScript contracts/examples and architecture documentation.Validation:
make checkwas run: 123 browser cases passed and four unrelated Dashboard cases failed. All four failures reproduce on pristine baseline d15da0d; the full gate is therefore not green. An initial isolated qualification Core connection closed once; recovery failed the interrupted Turn without replay, and subsequent real-model runs passed without recurrence. No production deployment was changed.Compatibility: newly frozen hosted deployment providers now use the same HTTPS validation as explicit providers; legacy HTTP endpoints must be changed to HTTPS. Native provider options remain privately encrypted and preserved.
Task: AGENT-EXEC-DEFAULTS-001 — https://vrfi1sk8a0.feishu.cn/wiki/EA3CwVSRviqe1XkZ0tAcq7FqnFc#doxcn8404vBIN5js7B06m1gZZwd