agentleFS
Sign inStart free
grandameniumgrandamenium/cortextos/dashboard/AGENTS.md

cortextos / dashboard

AGENTS.md106 starsChanged 7 months agoMITView on GitHub

The dashboard renders runtime: codex-app-server agents identically to claude agents. The two surfaces that needed codex-aware logic (PR-08) are: The codex-only test peer at dashboard/src/lib/__tests__/cost-parser-codex.test.ts is the mutation gate: deliberately break codex pricing in cost-parser.ts and this suite must fail. Run npm run test:codex from the repo root to execute it alongside the integration peers (tests/integration/fleet-health-mixed-codex-claude.test.ts, tests/integration/codex-bus-roundtrip.test.ts, etc.).

The file

Create a free account to mount
Files
AGENTS.md

@AGENTS.md

Dashboard codex coverage

The dashboard renders runtime: codex-app-server agents identically to claude agents. The two surfaces that needed codex-aware logic (PR-08) are:

  • Cost view — dashboard/src/lib/cost-parser.ts walks both ~/.claude/projects/*.jsonl (claude transcripts) and <ctxRoot>/logs/<agent>/codex-tokens.jsonl (codex per-turn flat-schema log), then merges into a single CostEntry[] keyed by source_file for dedup. gpt-5-codex pricing is in MODEL_PRICING ($1.25/M input, $10/M output, $0.125/M cache_read, $0/M cache_write) with substring matching on codex or gpt-5 in resolvePricingKey().
  • Fleet health view — computeFleetHealth in src/daemon/ipc-server.ts is fully runtime-agnostic; codex agents appear in the fleet summary and cron table with the same row shape and state machine as claude agents. The runtime badge is set from config.json.runtime.

The codex-only test peer at dashboard/src/lib/__tests__/cost-parser-codex.test.ts is the mutation gate: deliberately break codex pricing in cost-parser.ts and this suite must fail. Run npm run test:codex from the repo root to execute it alongside the integration peers (tests/integration/fleet-health-mixed-codex-claude.test.ts, tests/integration/codex-bus-roundtrip.test.ts, etc.).

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.

Check your setup, free