2fd748edad
* feat(desktop): distinguish account quota alerts from API key notices * docs: condense architecture introduction within existing budget (cherry picked from commit 01aacaee4d48fd7f4d00acb5e23758084d3f224e) * test(desktop): cover quota notice lifecycle and remove unknown casts (cherry picked from commit 7fd09407c482d1f0e30f24ba0ebf23cd844ac9a1) * chore(account-quota): align tests, catalogs, and bilingual pairs with the account plugin * fix(ui-settings-account): pass the Platform retry label to the account top-up overlay * fix(chat): preserve quota failures and global notices * fix(account): keep active top-up pages across quota notices * fix(account): share platform page ownership and release quota holds * fix(account): defer notices behind the shared Platform page The single native Platform view covers the document, so a quota failure that arrives while a Settings-opened page shows is deferred rather than retained: the newest failure still replaces an older notice and its Modal appears after the viewer returns if still current. Top up remains the retained case, releasing its hold and page request with the entry. * test(account): align quota fixture with bonus actions * fix(account): preserve quota notice and Platform return focus * fix(account): preserve onboarding return reads and failed notices * docs(account): clarify page opener return ownership * test(account): drive bonus acknowledgement retry deterministically --------- Co-authored-by: liyao <[email protected]> Co-authored-by: lsdsjy <[email protected]>
description, kind
| description | kind |
|---|---|
| Runtime API inspection, process-local runners, and historical Cordis cards. | package-group |
packages/extensions
English | 中文
Summary
The extensions group provides read-only runtime API discovery for agents, process-local runners for programmatic and browser consumers, and historical generated-plugin cards. Creator mode installs persistent plugins through Plugin Manager. Choose a child package for inspection, Host execution, Client execution, or browser controls.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
tool-cordis |
Two read-only tools for runtime API discovery | registers on ctx.tools |
cordis-host-runner |
Host half: definition registry, sandboxed host-half lifecycle, and the inspect registry that answers browser queries | provides ctx.dynamicCordisRunner and ctx.cordisInspect |
cordis-client-runner |
Browser half: evaluates a browser-half source into a live plugin and answers run requests | client face; provides browser ctx.dynamicCordisRunner |
ui-cordis |
Browser panel and historical lifecycle tool cards | client face; registers slots |
Related documentation
- Extensions subsystem — the generated
ctx.cordisInspectandctx.dynamicCordisRunnerservice API. - Generated tool catalog — the two read-only tool schemas.
- Generated configuration catalog — the runner's accepted config fields.
- Self-referential Cordis toolset Agent Note — design home for sandbox semantics, lifecycle, and composition.
- Client shells and dynamic packages Agent Note — package placement and build faces for the client halves.
Dev Note
Working context for maintainers — click to expand
The two browser-half packages live in this group rather than under packages/client/ because they are halves of this subsystem's dual-half packages; the client face compiles them through the client program, while the host program references only the host runner.