Report · marked 23 Sep 2026

danny-avila/LibreChat

Solid foundations, held back in a few specific places.

TypeScript · 44,713 stars · 5,492 files · branch main

78 /100 A-

Instructions 24/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup 20/20Whether an agent can install the project and get it running without a human. Full marks.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 11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

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.

File sizes fit in context

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.

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.

The full marking

Every deduction below names the file or setting it came from.

Instructions 24/27 A

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: CLAUDE.md

✗Instruction quality 10/12

Specific enough that an agent can act on it.

Worth fixing: has no code blocks.

7,380 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

✗README as an entry point 2/3

README exists but never explains how to get the thing running.

Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.

Setup 20/20 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 (prepare, update, add-balance, set-balance, list-balances, user-stats…)

scripts/ directory

✓Environment config 4/4

.env.example documents what the app needs to run.

✓Pinned runtime version 2/2

The language runtime version is pinned.

Found .nvmrc

✓Reproducible environment 2/2

.devcontainer/devcontainer.json gives a known-good environment.

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

1893 test files against 5086 source files.

e.g. api/app/clients/prompts/formatAgentMessages.spec.js, api/app/clients/prompts/formatGoogleInputs.spec.js, api/app/clients/prompts/formatMessages.spec.js

✗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.

✓Continuous integration 4/4

28 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

eslint.config.mjs 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 11/20 B-

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 136 patterns.

✗File sizes fit in context 0/6

62 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/api/src/stream/GenerationJobManager.ts — 363KB

api/server/controllers/agents/client.test.js — 340KB

packages/api/src/agents/handlers.spec.ts — 297KB

✗Repository weight 2/5

About 254MB checked out. Large enough that cloning and searching are both slow.

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

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 — drafted for danny-avila/LibreChat

# AGENTS.md

Enhanced ChatGPT Clone: Features Agents, MCP, Skills, DeepSeek, Anthropic, AWS, OpenAI, Responses API, Azure, Groq, o1, GPT-5, Mistral, OpenRouter, Vertex AI, Gemini, Artifacts, AI model switching, message search, Code Interpreter, langchain, DALL-E-3, OpenAPI Actions, Functions, Secure Multi-User Auth, Presets, open-source for self-hosting. Active

## Setup

```
bun install
```

## Commands

```
bun build           # produce a build
bun lint            # lint
bun format          # format
bun prepare
bun update
bun add-balance
bun set-balance
bun list-balances
```

## Layout

- `packages/` 2124 source files
- `client/`   2038 source files
- `api/`      636 source files
- `e2e/`      213 source files
- `config/`   50 source files
- `otel/`     4 source files

## Conventions

- Tests live alongside the code they cover, following `api/app/clients/prompts/formatAgentMessages.spec.js`.
- CI defines what passing means. See `.github/workflows/a11y.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `packages/api/src/stream/GenerationJobManager.ts` is 363KB. It will not fit comfortably in context, so read it in parts.
- Copy `.env.example` before running anything that needs configuration.

---

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/danny-avila/LibreChat.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good TypeScript AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/danny-avila/LibreChat.svg)](https://agentreadme.com/danny-avila/LibreChat)

Other TypeScript repositories, marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 73 B+ nilbuild/developer-roadmap 45 C deepseek-ai/deepseek-harness 82 A- vuejs/vue 67 B anomalyco/opencode 78 A-

All TypeScript repositories

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.

Open an issue, already filled in