Report · marked 26 Aug 2026
usebruno/bruno
An agent will struggle here, mostly for fixable reasons.
JavaScript · 46,541 stars · 4,242 files · branch main
54
/100
C+
Instructions
3/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on agent instruction file and instruction quality.Setup
14/18Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop
15/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on test command is discoverable and static type checking.Context economy
12/20Whether the repo fits in a context window, or fights it. Losing marks on no committed build output and file sizes fit in context.Navigability
10/10How quickly anything new can orient itself. Full marks.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Agent instruction file
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
02
Instruction quality
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
03
Test command is discoverable
Add a `test` script or a `test` target that runs the whole suite with no arguments. The convention is the interface — an agent tries `npm test` and `make test` before it tries reading your CI config.
The full marking
Every deduction below names the file or setting it came from.
Instructions 3/27 F
Whether the repo tells an agent how to behave before it starts guessing.
✗Agent instruction file
0/12
None found. Every agent that opens this repo starts from zero.
Add an AGENTS.md at the root: what the project is, how to install, how to run, how to test, and the two or three conventions a newcomer always gets wrong.
Looked for AGENTS.md, CLAUDE.md, .github/copilot-instructions.md, .cursorrules
✗Instruction quality
0/12
Nothing to judge, since there are no instructions.
Instructions earn their keep by naming exact commands. 'Run the tests with `pnpm test`' beats three paragraphs of philosophy.
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 14/18 A-
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands
6/6
Commands are declared where an agent will look for them.
package.json scripts (setup, watch:converters, dev, watch, dev:watch, dev:web…)
scripts/ directory
✗Environment config
0/4
Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
Found .nvmrc
–Reproducible environment
n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 15/25 B-
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✓Tests exist
8/8
2039 test files against 2525 source files.
e.g. .github/actions/tests/run-benchmark-tests/action.yml, .github/actions/tests/run-cli-tests/action.yml, .github/actions/tests/run-e2e-tests/action.yml
✗Test command is discoverable
0/7
There's no obvious way to run the tests. Even if tests exist, an agent won't reliably find the entry point.
Add a `test` script or a `test` target that runs the whole suite with no arguments. The convention is the interface — an agent tries `npm test` and `make test` before it tries reading your CI config.
✓Continuous integration
4/4
7 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
eslint.config.js encodes the house style.
✗Static type checking
0/3
No static type checking.
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
Context economy 12/20 B-
Whether the repo fits in a context window, or fights it.
✗No committed build output
3/6
Generated output is committed: node_modules/.
Add these to .gitignore and `git rm -r --cached` them. Generated files pollute search results, so an agent grepping for a function finds the compiled copy and edits the wrong file.
✓.gitignore hygiene
3/3
.gitignore covers 50 patterns.
✗File sizes fit in context
2/6
5 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
packages/bruno-app/src/providers/ReduxStore/slices/collections/index.js — 153KB
packages/bruno-app/src/providers/ReduxStore/slices/collections/actions.js — 128KB
packages/bruno-app/public/static/diff2Html.js — 124KB
✗Repository weight
4/5
About 61.8MB checked out, which is comfortable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia) ## Setup ``` npm ci ``` ## Commands ``` npm run dev # run locally npm run lint # lint npm run setup npm run watch:converters npm run watch npm run dev:watch npm run dev:web npm run build:web ``` ## Layout - `packages/` 2024 source files - `tests/` 482 source files - `scripts/` 10 source files - `playwright/` 3 source files ## Conventions - Tests live alongside the code they cover, following `.github/actions/tests/run-benchmark-tests/action.yml`. - CI defines what passing means. See `.github/workflows/benchmarks.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `packages/bruno-app/src/providers/ReduxStore/slices/collections/index.js` is 153KB. It will not fit comfortably in context, so read it in parts. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/usebruno/bruno.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/usebruno/bruno)Other JavaScript repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.