moai-ref-aside-browser
Skill1.3k starsChanged 2 months agoApache-2.0View on GitHub
Safe-use reference for the optional Aside browser agent (the `aside` command-line tool and its MCP server), which works inside the operator's own logged-in browser. Covers when the orchestrator may use it, how its permission modes work, and the rules that keep it read-only by default. Operated by the orchestrator alone. NOT for: public pages that a plain fetch can read, subagent work, or CI runs.
Trending
More talk lately.about the whole repository
Who's talking about modu-ai/moai-adk
- Ven0m0/claude-config“Add a structured external integration plan to the root TODO backlog”GitHub · Mar 18, 2026 · 4 reactions
- Ven0m0/claude-config“TODO list”GitHub · Jan 31, 2026 · 1 reactions
- sudosubin/agents.nix“codex-marketplaces.github.modu-ai.moai-adk: 3.1.2 → 3.2.0”GitHub · Oct 23, 2026
- sudosubin/agents.nix“agent-skills.github.modu-ai.moai-adk: 3.1.2 → 3.2.0”GitHub · Oct 23, 2026
- sudosubin/agents.nix“codex-marketplaces.github.modu-ai.moai-adk: init at 3.1.2”GitHub · Oct 13, 2026
The biggest 5 of 16 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 16
Talked about on GitHub (16 times).
On GitHub · 16
- Mar 18, 2026Add a structured external integration plan to the root TODO backlog — Ven0m0/claude-config4 reactions · 4 comments
- Jan 31, 2026TODO list — Ven0m0/claude-config1 reaction · 18 comments
- Oct 23, 2026codex-marketplaces.github.modu-ai.moai-adk: 3.1.2 → 3.2.0 — sudosubin/agents.nix0 reactions
- Oct 23, 2026agent-skills.github.modu-ai.moai-adk: 3.1.2 → 3.2.0 — sudosubin/agents.nix0 reactions
- Oct 13, 2026codex-marketplaces.github.modu-ai.moai-adk: init at 3.1.2 — sudosubin/agents.nix0 reactions
11 more on GitHub
- Sep 30, 2026agent-skills.github.modu-ai.moai-adk: init at 3.1.2 — sudosubin/agents.nix0 reactions
- Sep 7, 2026Worktree-isolation Bash check folds command substitutions in quoted-delimiter heredoc bodies but refuses braces there, though such bodies cannot expand — anthropics/claude-code0 reactions
- Sep 6, 2026docs(t41): moai gate 종료 코드 합류 — upstream 이슈 문안 (제출 안 함) — bjw202/minidiscord0 reactions
- Jul 23, 2026Hands-on eval: promote MoAI-ADK to core tier — cameronsjo/spec-compare0 reactions
- Apr 22, 2026Add MoAI-ADK to Collections & Libraries — travisvn/awesome-claude-skills0 reactions
- Apr 22, 2026Add MoAI-ADK to Meta & Orchestration category — VoltAgent/awesome-claude-code-subagents0 reactions
- Apr 22, 2026Add MoAI-ADK — SPEC-first Agentic Development Kit — jqueryscript/awesome-claude-code0 reactions
- Apr 22, 2026Add MoAI-ADK — SPEC-first AI-assisted coding framework — wsxiaoys/awesome-ai-coding0 reactions
- Apr 22, 2026Add MoAI-ADK — SPEC-first Agentic Development Kit for Claude Code — e2b-dev/awesome-ai-agents0 reactions
- Nov 19, 2025Issue #1: Estructura base del proyecto .NET 9 — mjcuadrado/mjcuadrado-net-sdk0 reactions
- Nov 13, 2025fix: resolve conflitos Git + remove hooks SYNC bloqueantes (Windows f… — PedroGiudice/lex-vector0 reactions
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- moai-cleanSkill
- moai-codemapsSkill
- moai-e2eSkill
- moai-feedbackSkill
- moai-fixSkill
- moai-gateSkill
- moai-goalSkill
- moai-gtdSkill
- moai-harnessSkill
- moai-loopSkill
- moai-mxSkill
- moai-planSkill
- moai-projectSkill
- moai-reviewSkill
- moai-runSkill
- moai-syncSkill
- moai-todoSkill
- hns-lsel-applierSkill
- hns-lsel-curatorSkill
- hns-moaiadk-best-practicesSkill
- hns-moaiadk-dev-referenceSkill
- hns-moaiadk-patternsSkill
- hns-oss-docs-i18n-rulesSkill
- hns-oss-docs-readme-syncSkill
- hns-oss-docs-structure-mapSkill
- hns-oss-docs-verifySkill
- hns-workflow-ci-loopSkill
- moai-domain-backendSkill
- moai-domain-databaseSkill
- moai-domain-design-dnaSkill
- moai-domain-frontendSkill
- moai-domain-html-reportSkill
- moai-domain-humanizeSkill
- moai-domain-svg-infographicSkill
- moai-factory-foremanSkill
- moai-foundation-ccSkill
- moai-foundation-coreSkill
- moai-foundation-qualitySkill
- moai-foundation-thinkingSkill
- moai-harness-learnerSkill
- moai-jev-skill-suggestionSkill
- moai-lane-watchdogSkill
- moai-meta-harnessSkill
- moai-ref-api-patternsSkill
- moai-ref-cross-model-auditSkill
- moai-ref-git-workflowSkill
- moai-ref-jev-question-designSkill
- moai-ref-llm-securitySkill
- moai-ref-owasp-checklistSkill
- moai-ref-react-patternsSkill
- moai-ref-secopsSkill
- moai-ref-seoSkill
- moai-ref-supply-chainSkill
- moai-ref-testing-pyramidSkill
- moai-ref-ui-polishSkill
- moaiSkill
- moai-workflow-dddSkill
- moai-workflow-docs-claim-checkSkill
- moai-workflow-loopSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Use it for a task that needs a page behind the operator's login, which a fresh headless browser cannot reach, and only when the operator …
- Distinctive: line 31
Do not use it for public pages (a plain fetch or the platform default browser tooling reads those), in CI, or because it happens to be …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Aside Browser (optional)
Purpose
Aside is an optional browser agent that acts inside the operator's own browser, so it sees every page the operator is signed in to, with the operator's credentials, cookies, and history. aside mcp starts an MCP server over stdio with two tools: exec runs the browser agent on logged-in sites, and repl runs Playwright-style JavaScript against open pages (120-second timeout; page starts unset, so call openTab(url) or getTabs() first). Flag and tool names here reflect one observed version; if a probe or a call fails, treat Aside as absent.
When to use, and when not
- Use it for a task that needs a page behind the operator's login, which a fresh headless browser cannot reach, and only when the operator asked for it.
- Do not use it for public pages (a plain fetch or the platform default browser tooling reads those), in CI, or because it happens to be installed.
Who operates it
Aside is operated by the orchestrator alone. A subagent never invokes Aside, neither the aside command nor the Aside MCP tools; a task that needs Aside returns a blocker report to the orchestrator, which runs the step itself or drops it.
Safe-use rules
- Permission. Never pass
--permission full-access, and never request full-access by any other route (settings, prompts, or tool arguments). - Guard by omission. The permission flag takes one of three values;
askandguardare the same Guard mode, and omitting the flag also means Guard. Prefer to omit--permissionentirely so the default Guard applies. - REPL limit.
aside replhas no permission flag, so its read-only limit is discipline, not enforcement: restrict REPL work to navigation, reading, and screenshot operations. - Writes. Any step that changes state (submitting a form, posting, purchasing, deleting, sending, changing a setting, approving) needs explicit operator confirmation, obtained by the orchestrator through its question channel before the step runs. Never infer consent from the task text. Treat every
execrun as state-changing, because an agent-driven run can click, type, and submit. - Install. Never install Aside and never run install tooling for it. If the operator wants Aside's own browser skill added to their coding agents, advise the operator to run
aside skills install; the orchestrator does not run it. - Secrets. The session carries the operator's logins, so never place credentials, cookies, tokens, or session data in any output, log, file, report, or prompt. Cite screenshots by path and carry only the minimum page text a step needs.
- Output size. Redirect verbose REPL output to a file and bring only the exit code and a bounded tail into context.
Optional registration
Aside is never part of the default configuration. An operator who wants the MCP server registers it with one explicit command:
moai mcp add aside --command aside --args mcp --scope userOmit --scope user to register it for one project instead. The registration is optional and never a prerequisite of any workflow in this skill.
Relation to /moai e2e
/moai e2e --tool aside is the only way Aside enters the e2e workflow: it is explicit-only, never auto-detected, never offered, and never recommended. The orchestrator loads this skill first and runs every Aside step itself. When Aside is absent, fails its availability probe (aside --version), is signed out, or is excluded (for example when CI=true), the workflow continues silently on the platform default toolchain, with no Aside-specific message, prompt, install attempt, or failure.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

