agentleFS
UtsavBalar1231UtsavBalar1231/oh-my-claudeagent/opencode/AGENTS.md

oh-my-claudeagent / opencode

AGENTS.md3 starsChanged 32 days agoMITView on GitHub

index.ts is the server plugin. tui.tsx is the optional terminal companion; tui-panel.tsx renders its session panel with native theme and interaction APIs. rpc.ts is its import-safe contract. state.ts reads checkout-local OMCA state. tools.ts registers native, session-aware tools. lib.ts projects shared Markdown bodies and metadata into native definitions; it owns no second prompt roster. workflows.ts contains OpenCode-specific coordination. Package installs load tui.generated.js, compiled from the same TypeScript UI. Run just build-opencode after UI or RPC changes. Do not edit the artifact…

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 1 is common, 1 is distinctive, and 2 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run just build-opencode after UI or RPC changes.

    line 11
  2. Common:

    Use the public OpenCode V2 APIs and the installed SDK types.

    line 14
  3. Distinctive:

    Use additive native slots and semantic theme tokens.

    line 23
  4. Very specific:

    Run just test-opencode for adapter tests and just ci before claiming the change verified.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

OpenCode V2 adapter

index.ts is the server plugin. tui.tsx is the optional terminal companion; tui-panel.tsx renders its session panel with native theme and interaction APIs. rpc.ts is its import-safe contract. state.ts reads checkout-local OMCA state. tools.ts registers native, session-aware tools. lib.ts projects shared Markdown bodies and metadata into native definitions; it owns no second prompt roster. workflows.ts contains OpenCode-specific coordination.

Package installs load tui.generated.js, compiled from the same TypeScript UI. Run just build-opencode after UI or RPC changes. Do not edit the artifact by hand or bundle host packages into it; CI checks its source freshness.

Use the public OpenCode V2 APIs and the installed SDK types. Do not import private OpenCode services, local credential files, or its SQLite database.

Resolve the current session location for each operation. Keep execution cwd, checkout-local state, and the plugin installation directory separate. Never change process cwd or environment to supply per-session context.

The TUI reads server snapshots over RPC. It never reads server paths on the client machine. Viewing a panel must not bind a plan, run a model, or create state files. Use additive native slots and semantic theme tokens; preserve native navigation.

Native permission checks apply to custom tool filesystem operations too. Plan mode cannot bind execution or apply mutations. Child agents have their own permissions, so read-only delegation must be explicit.

OpenCode has no documented Stop veto. Historical evidence, completed task boxes, and current-checkout verification are different states.

Run just test-opencode for adapter tests and just ci before claiming the change verified. Integration tests require the supported OpenCode executable on PATH.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.