Your AI — home base. Talk to Onion, direct it, and approve what it proposes before anything runs.
This console is gated by your Onion Core passcode. It is kept in this tab's session storage only, and sent only to the Onion Core Bridge.
This is your AI's home. Ask anything — or flip to Agent mode, put Onion to work, and approve what it proposes.
Verify runs a second pass that checks each claim against the sources — unsupported claims are flagged, never hidden. Style appends a short instruction to your prompt (the agent sees it as part of your instruction; it is added by this console, marked [Console style: …]).
Onion can make mistakes. Please double-check responses.
No tasks yet this session.
One-tap operations, agent profiles (presets that fill the composer above), and saved automation recipes you can rerun. Profiles and recipes live in this browser; running a recipe creates real tasks through the normal approval flow.
Keys let your apps, scripts, and automations call Onion AI with exactly the power they're given — no more. A key is shown once when created or rotated. Only you (the root passcode) can create, change, or revoke keys.
Keys not loaded yet.
Permissions — tick only what this key truly needs:
Pick “Activity” on a key to see its recent calls.
Everything ONION AI can use — tools, sources, MCP servers, skills — generated from the real registries, not a marketing list. ENABLE/DISABLE persists on this device today; server-side manifest gating is staged (see catalog-server/APPLY.md). INSTALL never installs silently: it creates an approval-gated task with the exact command.
No installs proposed from the catalog yet.
One search across this session's tasks, the catalog, .oc sources, and memory held on this device (pinned notes + the local task archive). Server-side warm memory stays in the Memory panel.
Act on several tasks at once: star them, export them as one markdown bundle, or hide them from these v3 panels. Hiding is device-local — the server journal is append-only, so nothing here pretends to delete server records.
No tasks yet.
No browser sessions reported yet.
Pick a session — its latest screenshot lands here.
No browser tasks yet.
No control changes yet.
Pick a session — its events land here.
Nothing saved yet — macros, bookmarks and pinned sites land here.
⌨️ Shortcuts (panel focused, not typing): T take control · R release to AI · P pause AI
Where your AI's bots are built and run. Make bots, pick what they do, pick how many — link checks, site watches, question answering, file jobs and Cloud PC errands, all on the Onion Core engine machine. Bot Forge is admin-only and keeps its own pass gate; it lives at its own home and is embedded here as Onion AI's workshop.
Embedded from https://onioncore-botforge.pages.dev/ — if the embed ever fails to load, open Bot Forge directly.
Hot = this session's live tasks (held in the console right now).
Warm = the agent's long-term memory on the Cloud PC (semantic when the embedder is up, keyword fallback otherwise — the mode is always labeled).
How memory works here (v1): the PC store is append-only — there is no server delete endpoint yet. Pin writes a new copy of the memory at importance 1.0 (the newest copy is its current state); Forget hides a memory in this console on this device only — it is not erased on the PC.
Cold = this browser's local archive of finished tasks you've run here (kept on this device, survives reloads, capped at the newest 200). The PC memory corpus itself is search-only — use Warm to query it.
No notes yet. Notes live in this browser only.
No failures this session. When a task fails, its reason, dispatch notes and retry history land here.
Scans the last 12 hours of failed tasks and proposes operating rules. A rule only joins the agent's system prompt after you approve it here.
Counted live from the real task journal above — no invented metrics. Shows what ran, which brain answered, and what is still waiting on you.
No tasks yet this session.
Live checks: Bridge API, Cloud PC / GPU registration (from the console's own status badges), memory transport, and the codetools detection summary baked into the catalog.
Not checked yet.
Every task this session, newest first — the same journal, rendered as a feed. Tap any entry to open it.
No activity yet.
Privacy: this page talks only to the Onion Core Bridge. Third-party AI/search calls happen server-side under the operator identity — your phone's IP never reaches them. Machine actions always require your approval above.
No chats yet — your console sessions will list here.
Nothing running right now.
Projects live on this device. Star, rename or archive from the ⋯ menu.
Files you add here are stored with their content on this device. Seeded entries carry a name only — open one and it will say so.
These instructions ride with the project on this device. They're written for Onion, in our own words.
Fort Wayne resource finder — GPS map of shelters, food, showers and help, offline-first.
Private browser with Dark Onion mode and the Agent built in.
Neon-stacked tower defense, built in Godot and shipped as an APK.
Chaotic cart-racing mayhem — the Death Cart build line, v2.8.
Game-building toolkit — forge, test and ship small games fast.
Drag to fly between planets; tap one for its story. A sample interactive to remix.
A clean one-page notes layout with date, place and follow-ups. A sample document.
Five rooms, three monsters, one very brave knight. A sample mini-game.
Streaks and weekly bars for anything you do daily. A sample data view.
Your artifacts are your shipped deliverables — their downloads live in Onion Core Files. Inspiration cards are neutral samples written for this page.
—
Custom instructions are appended to your sends, marked as a console instruction — the same channel as console styles.
Import or export your memory. Import stores entries through the console's memory route; export downloads what this console holds on this device.
Bridge-side MCP servers live in the Extension Catalog.
Imports are listed here on this device. Workspace skills themselves live in the skills folders Onion loads from.
This workspace has exactly one human: Blaze. Enterprise controls from the reference app are shown as not applicable rather than faked.
States are checked against the real connections.
One plan, your own stack. The other columns keep the comparison layout as reference only — they aren't offered, because Onion Core already includes everything.
Your plan — Bridge, Cloud PC and this console.
Comparison column — not offered.
Comparison column — not offered.
Onion runs on brains: a failover chain of cloud models behind the Bridge, plus the local Dolphin model on your own Cloud PC. When one brain is down or out of quota, the chain moves to the next — the brain that answered is labeled on every reply, so nothing pretends. Chat is for talking; Agent tasks are for doing — anything that would run a command or write a file stops for your approval tap first. Local brain means no vendor in the loop at all: slower, fully yours.
| Surface | This session | Limit |
|---|---|---|
| Chats | 0 | None — your stack |
| Agent tasks | 0 | None — your stack |
| Local brain | 0 | None — your hardware |
One workspace for your personal AI: talk to Onion, keep projects and knowledge, run agents and bots, and watch activity — approvals included — without leaving. Chat rides the persona lane to the local Dolphin brain on Node A first, with the Bridge ask chain as fallback; every reply is badged with the lane that actually answered.
Brain: not checked yet
No messages yet. Say something — the reply comes from a real brain lane or the panel says the brain is offline. Nothing here echoes or fakes a reply.
Persona sheets ride in the prompt exactly like persona_chat.py builds them (condensed sheet text is baked into this page; the full sheets live in ~/workspace/personas/). Speak replies uses this browser's built-in speech voice — each persona's own TTS voice (Onion: Cheeky Bubble, Neuro-sama: Playful Whistle, Evil-sama: Commanding Arch) runs in the voice-note lane, not in a browser.
↑↓ navigate · Enter run · Esc close · Ctrl/⌘K toggles this palette.
Dark is the default. Light re-skins the shell and cards through the theme variables; a few deep panels (Browser Control) keep their own dark styling.
Choose how you'd like the conversation to feel