Repository navigation
Replies: 2 comments
|
Hey, |
|
Following up with a request for explicit maintainer approval of direction and scope before opening another feature PR. I use Mistral Vibe through T3 and have a local prototype for a dedicated, opt-in provider that reuses the existing shared ACP adapter. The main motivation is Vibe-specific usage history, included API/Vibe billing allowances and retry/quota reporting; it does not require a second ACP transport implementation. The proposed scope is:
A Windows browser smoke test with Vibe 3.1.0 displayed DeepSeek's thinking levels and completed a short request. The prototype is not submission-ready yet: replay coverage, final validation and UI evidence remain. I understand the closure of #23380 means an implementation or a linked discussion alone is not approval. I also found the open native Would maintainers approve the direction and scope above for a feature PR, or prefer contributions to #31881 / a narrower generic ACP usage solution instead? If a dedicated ACP-based provider is not desired, which of the usage/billing gaps would you welcome as a focused contribution? I will link an explicit approval comment in any eventual PR and follow the scope you prefer. No new PR has been opened for this prototype. |
Uh oh!
There was an error while loading. Please reload this page.
Feature request
Track Mistral Vibe (Mistral 4) session usage on T3's Usage page, alongside the existing providers (Codex, Claude Code, Grok Build, OpenCode, Antigravity, Pi, Cursor).
Users running Mistral Vibe through the ACP Registry currently have no visibility into their token usage or estimated cost in T3.
Proposed behavior
~/.vibe/logs/session/unified/(or$VIBE_HOME).projection-state.jsonand the.session-index.jsoncatalog, whichever reading is fresher.Implementation
Implemented in PR #23380 (branch
feature/mistral-vibe-usage): a newmistralVibeUsageReaderon the ACP Registry driver, amistralprovider kind in contracts, web/mobile presentation, and user docs.Requesting maintainer approval of direction and scope for this new provider, per the PR template.
All reactions