Manage AIOS agents and vaults from inside VS Code-compatible editors
翻译准备中
AI 摘要 · README
插件TypeScript · JavaScriptGitHub @The-AIOS自行安装运营者未确认
试用过了吗? 点一下就好,无需登录。
正在加载完整 README。 以下为已保存的摘录。
A friendly glass layer over the AIOS — run rituals, browse agents, manage spaces, and navigate your vault, all from inside Google Antigravity (or any VS Code-compatible editor).
Glass, not engine. AIOS Glass never reimplements the AIOS. It surfaces and triggers what already exists — your slash commands, your spawn workers, your company/collaborate syncs. The brain stays in the framework; this is the clickable window onto it. The terminal becomes optional, not required.查看完整 README ↗A friendly glass layer over the AIOS — run rituals, browse agents, manage spaces, and navigate your vault, all from inside Google Antigravity (or any VS Code-compatible editor).
Glass, not engine. AIOS Glass never reimplements the AIOS. It surfaces and triggers what already exists — your slash commands, your
spawnworkers, your company/collaborate syncs. The brain stays in the framework; this is the clickable window onto it. The terminal becomes optional, not required.
From Open VSX, in any editor that uses it: Google Antigravity, Cursor, VSCodium, Windsurf. Search AIOS Glass in the Extensions view. It needs The AIOS cloned at ~/aios and Claude Code installed.
The AIOS is powerful but lives behind the terminal: slash commands you type, the spawn wrapper, git pulls. That's a wall for non-developers. AIOS Glass turns each ritual into a button, each argument into a form field, each agent into a click — so anyone can operate their AIOS from a graphical surface.
⌘⌥G Q chord, and a fallback in every picker: a search that matches nothing resolves by meaning instead of dead-ending.Alt+↑/↓, Daily pinned), and navigate by keyboard.⌘⌥G B.⌘⌥G chords + the * palette — 21 shortcuts behind one leader with an on-panel cheat-sheet, plus a wildcard palette that fuzzy-searches everything launchable: sessions, routines, tasks, agents, commands, skills.Sessions and agents reach each other through files in ~/.aios/spawn-inbox/, and Glass is one of the two surfaces that carry them out (the AIOS App is the other). Four verbs, contract 4:
spawn: start a named session, with an optional first tasksend: type a prompt into a session that is already runningkill: close a sessionresume: reopen a closed session with the context it hadWhichever surface is running picks the request up. Add "surface": "glass" or "surface": "app" to choose one. A field Glass cannot honour (cwd, App only) is refused with a dead letter naming it, never carried out somewhere else. The full protocol is the README.md the running surface writes into that folder.
AIOS Glass recommends Foam for the vault-navigation layer — [[wikilinks]] rendering, backlinks, and graph view. It's an optional companion (Glass prompts to install it on first run): Glass works without it, and it's deliberately not a hard extensionDependency so Glass installs cleanly on editors whose engine predates the latest Foam (e.g. stock Antigravity). AIOS Glass adds the operating-system control plane on top:
/aios:* commands via native Claude Code/company + /collaborate, args as formsWe lean on Foam rather than forking it deliberately — Foam stays the engine and auto-updates upstream; we stay glass. (Soft dependency, not hard: a stuck/old Foam never blocks Glass from activating.)
npm install
npm run watch # or: npm run compile
Then press F5 ("Run AIOS Glass — Extension Dev Host"). A second editor window opens with your vault loaded and the AIOS activity-bar icon active.
The Rituals view reads the live plugins/aios/commands/*.md directory of your framework at runtime — it never hardcodes the command list, so anything /aios:update adds shows up automatically. Clicking a ritual launches claude "/aios:<name>" in an integrated terminal. Commands with an argument-hint prompt for arguments first.
Configure the framework location with aiosGlass.frameworkPath (default ~/aios).
GPL-2.0-or-later © The AIOS contributors — same license as the AIOS framework.