Skip to content

Route unified and compatibility endpoints by independent key profiles - #203

Merged
GDR merged 2 commits into
ui/refactorfrom
codex/unified-socket-compatibility
Oct 24, 2026
Merged

GDR merged 2 commits into
ui/refactorfrom
codex/unified-socket-compatibility

Conversation

@GDR

@GDR GDR commented Oct 24, 2026

Copy link
Copy Markdown
Owner

Both socket endpoints now route by the independent Personal/Bot profile instead of legacy purpose. The primary clavis.sock accepts eligible Personal and Bot profiles; clavis-agent.sock remains Bot-only, rejects forwarding/failed bindings and all control requests, and preserves legacy agent session restrictions. New Bot profiles support SSH and Signature without a launcher. Request prompts retain verified caller names, and audit key kind follows the actual profile.

Adds configuration/migration guidance explaining explicit identities, routing versus identity, uncertain once-only access, and pause behavior.

Validation: all 912 tests passed (534 core, 378 app). New coverage exercises the full classification/type/operation/endpoint matrix, disabled operations, exact key/caller prompts, uncertainty, forwarding, identity enumeration, persistent pause, and every control opcode on the compatibility endpoint. 323 changed lines. Targets ui/refactor; installed app unchanged.

@GDR
GDR merged commit 6910735 into ui/refactor Oct 24, 2026
1 check passed
@GDR
GDR deleted the codex/unified-socket-compatibility branch October 24, 2026 15:02
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.

1 participant