Repository navigation
Provider capability self-checks per thread (skills, tools, flags actually work) #324
Description
T3 Code's #1 and #3 most-voted open issues: skills exist on disk but the orchestrator reports zero (Claude/Codex discover them fine); permission requests from one provider silently dropped, aborting the turn. Per-provider capability drift is the canonical orchestrator bug.
Add a per-provider capability probe: which skills/tools/flags/events does this provider actually expose through Solenta's wiring, verified at setup and surfaced on mismatch — so 'works in the raw CLI but not through Solenta' gets caught by us before the user finds it.
Activity
currentbits commentedon Aug 18, 2026
Research note (AAIF): MCP conformance is now mechanically testable (SEP-2484 harness, SDK tiers, modern/legacy/dual-era taxonomy). Surface per-server conformance badges and deprecation warnings (Roots/Sampling/Logging) in the capability self-check — before the harness vendors productize it.
currentbits commentedon Aug 18, 2026
Deep-dive (Zed Terminal Threads): per-CLI attention-signaling conventions worth supporting — Claude Code preferredNotifChannel terminal_bell; Amp AMP_FORCE_BEL=1; OpenCode plugin writing BEL on session.idle/permission.asked; Codex OSC title sequences parsed for run state. If Solenta ever falls back to PTY-level detection, these are the documented switches.
currentbits commentedon Oct 19, 2026
Not planned (board cleanup 2026-10-19): a speculative brainstorm idea with no work in two months. Model-catalog divergence warnings (#745) cover the most common drift. Reopen if it becomes a priority.