Roadmap 0.11, Fixes
FX.412 AI is part of Studio again: the Ask box works in every app with nothing to add
Owner 2026-11-20: "AI belongs to Studios and passes down to apps." On 2026-11-11 "no AI in the apps" was read as "no AI anywhere", and the part of the Ask box that uses a person's own model became an add-on they had to add (and could not add in a packed Studio). What was meant: not the same engine repeated in each of the eight apps.
BUILT. The engine is Studio's: one copy in Studio's package (hub/ask-engine.js + the tested engine), handed to every app window by Studio's own window script. Set a model up once in Studio, Your own AI model, and the Ask box of every app answers with it; with none set up the box says where to do that. The apps and the shared shell still hold no engine (the scan has no allow list; its rule text and checks now say where the engine lives). The "Your own AI key" add-on is the same engine for ONE app in a browser without Studio: its own set-up (provider, model, key, limits), the key kept in that browser's storage and said so plainly; inside a Studio it registers nothing.
Tests: node bin/test-ask-byok.mjs 55/0, node tools/shell-test/browser-ask-ownkey.mjs 64/0 (real CadCraft and BimCraft pages, stand-in Studio and providers), node tools/ai-scan/no-ai-scan.mjs clean, node tools/mcp/test/byok.mjs 62/0. In the lab; no Studio build made, nothing released. Limits: no real provider or key was ever used; SuperCad Studio has no Ask box or key card of its own yet (the engine accepts its native commands, tested with a stand-in).
Community comments
No comments yet
Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.
Sign in or create a free account to add a comment.