agentleFS
the-open-agentthe-open-agent/openagent/CLAUDE.md

openagent

CLAUDE.md5.7k starsChanged 37 days agoApache-2.0View on GitHub

Backend (Go) Frontend (React + shadcn/ui, built with Vite) web-old/ holds the previous Ant Design frontend. It is kept for reference only while bugs are chased down against it — it is not built, served or linted, and it does not get new work. Full production build uses build.sh which cross-compiles for linux/amd64, linux/arm64, linux/riscv64. Backend serves the frontend as embedded static files (embed.go); during development the frontend proxy is configured to hit localhost:14000. Module: github.com/the-open-agent/openagent The backend is a…

1 other project uses a version of this.

Trending

Quiet since September.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 15 mentionsJun 2026: 3 mentionsJul 2026: 5 mentionsAug 2026: 3 mentionsSep 2026: 3 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the the-open-agent/openagent repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about the-open-agent/openagent

The biggest 5 of 30 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 30

Talked about on GitHub and Bluesky (30 times).

On GitHub · 26

21 more on GitHub

On Bluesky · 4

The file

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

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Create web/src/pages/<Name>Page.tsx (default export).

    line 53
  2. Very specific:

    Add a <Route> in App.tsx pointing at page("<Name>Page").

    line 54
  3. Very specific:

    Add a menu entry in getNavGroups() (web/src/lib/nav.ts), in the correct group — Basic / Connectors / Admin etc.

    line 55
  4. Very specific:

    Add the nav key to web/src/components/common/NavItemTree.tsx so it appears in the site Navbar Items config.

    line 56
  5. Very specific:

    Delete responses use affected != 0 boolean pattern.

    line 71
  6. Very specific:

    All API responses go through c.ResponseOk(data) or c.ResponseError(msg).

    line 72

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Commands

Backend (Go)

go build                    # build backend binary
go run main.go              # run backend (port 14000)
go test ./...               # run all tests
go test ./object/... -run TestFoo  # run a single test

Frontend (React + shadcn/ui, built with Vite)

cd web && yarn install
yarn start                  # dev server on port 13001, proxies /api to localhost:14000
yarn build                  # production build (vite writes build-temp, mv.js swaps it into web/build)
yarn typecheck              # tsc --noEmit
yarn lint                   # eslint

web-old/ holds the previous Ant Design frontend. It is kept for reference only while bugs are chased down against it — it is not built, served or linted, and it does not get new work.

Full production build uses build.sh which cross-compiles for linux/amd64, linux/arm64, linux/riscv64.

Backend serves the frontend as embedded static files (embed.go); during development the frontend proxy is configured to hit localhost:14000.

Architecture

Backend (Go / Beego)

Module: github.com/the-open-agent/openagent

The backend is a standard Beego MVC app. Every entity follows the same three-layer pattern:

  1. object/<entity>.go — struct definition (xorm tags for DB), and all DB access functions: GetGlobal<Entities>, Get<Entity>Count, GetPagination<Entities>, Get<Entity>, Add<Entity>, Update<Entity>, Delete<Entity>. The primary key is always (Owner string, Name string). Use util.GetId(owner, name) / util.GetOwnerAndNameFromIdWithError(id) for composite key serialization.
  2. controllers/<entity>.go — Beego controller methods wired to routes. Standard set: GetGlobal<Entities>, Get<Entities>, Get<Entity>, Add<Entity>, Update<Entity>, Delete<Entity>. Use c.IsAdmin() / c.IsGlobalAdmin() / c.RequireSignedIn() for auth. Paginated list APIs accept p, pageSize, field, value, sortField, sortOrder query params and use pagination.SetPaginator.
  3. routers/router.go — beego.Router calls grouped by entity (all routes for the same entity's CRUD kept together). No alphabetical ordering within a group. New entity routes should be inserted next to their entity's existing routes (not appended to the end of the file).

DB schema is auto-migrated via object/adapter.go → createTable() using engine.Sync2(new(EntityStruct)). Add new entities there.

i18n (backend): i18n/locales/{en,zh}/data.json — keys are namespaced by category (e.g. "comment:...", "general:..."). Use c.T("namespace:key") in controllers.

Frontend (React + shadcn/ui on Tailwind, TypeScript, Vite)

Routing lives in web/src/App.tsx; every file in web/src/pages is its own lazy chunk, loaded by name. To add a new admin page:

  1. Create web/src/pages/<Name>Page.tsx (default export).
  2. Add a <Route> in App.tsx pointing at page("<Name>Page").
  3. Add a menu entry in getNavGroups() (web/src/lib/nav.ts), in the correct group — Basic / Connectors / Admin etc.
  4. Add the nav key to web/src/components/common/NavItemTree.tsx so it appears in the site Navbar Items config.

Page pattern: list pages render CrudListPage (web/src/components/crud/) with a ColumnDef[]; edit pages render SimpleEditPage with an EditField[], or compose EditPageShell directly when the layout is custom. Both patterns are illustrated by MessageListPage.tsx / MessageEditPage.tsx.

Backend API layer: web/src/backend/<Entity>Backend.ts — thin fetch() wrappers, one file per entity. Standard exports: getGlobal<Entities>, get<Entity>, update<Entity>, add<Entity>, delete<Entity>.

Per-instance config: the backend sends the Casdoor issuer, client ID and branding in the jsonWebConfig cookie (set with index.html and with every /api/get-account response) and web/src/Conf.ts reads it at boot, so one build serves every instance.

i18n (frontend): web/src/locales/{en,zh}/data.json namespaced by page/domain. Use i18next.t("namespace:key").

Key conventions

  • Owner is always "admin" for system-created entities.
  • Entity Name is a random string generated with util.GetRandomString(n) or a user-provided slug.
  • CreatedTime / UpdatedTime use util.GetCurrentTimeWithMilli() (string format).
  • Delete responses use affected != 0 boolean pattern.
  • All API responses go through c.ResponseOk(data) or c.ResponseError(msg).
  • The conf/app.conf file configures DB (driverName, dataSourceName, dbName) and port (httpport = 14000).

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.