Report · marked 10 Oct 2026

infiniflow/ragflow

Ready for an agent to work in without hand-holding.

Go · 91,948 stars · 5,221 files · branch main

90 /100 A

Instructions 26/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on readme as an entry point.Setup 18/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop 22/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy 13/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

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.

Repository weight

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

Environment config

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.

The full marking

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

Instructions 26/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: Copilot instructions

✓Instruction quality 12/12

Specific enough that an agent can act on it.

15,194 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

includes copyable code blocks

✗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 18/20 A

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6

uv.lock pins the dependency tree.

Found uv.lock

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

scripts/ directory

✗Environment config 2/4

Env vars are mentioned in the README but there's no example file to copy.

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.

go.mod declares a Go version

✓Reproducible environment 2/2

dockerfile gives a known-good environment.

Verification loop 22/22 A+

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8

1482 test files against 4357 source files.

e.g. cmd/ragflow_server_deepdoc_test.go, cmd/ragflow_server_test.go, internal/admin/handler_queue_test.go

✓Test command is discoverable 7/7

An agent can find and run `pytest`.

✓Continuous integration 4/4

3 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

pyproject.toml encodes the house style.

–Static type checking n/a

Not applicable — the Go compiler type checks every build.

Context economy 13/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 138 patterns.

✗File sizes fit in context 2/6

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

web/src/locales/az.ts — 235KB

web/public/iconfont.js — 222KB

web/src/locales/uz.ts — 220KB

✗Repository weight 2/5

About 177MB 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 infiniflow/ragflow

# AGENTS.md

RAGFlow is a leading open-source Retrieval-Augmented Generation (RAG) engine that fuses cutting-edge RAG with Agent capabilities to create a superior context layer for LLMs

## Setup

```
uv sync
```

## Commands

```
pytest          # run the test suite
ruff check .    # lint
go test ./...   # run the test suite
```

## Layout

- `internal/` 2694 source files
- `web/`      1490 source files
- `test/`     84 source files
- `tools/`    33 source files
- `sdk/`      19 source files
- `example/`  11 source files

## Conventions

- Tests live alongside the code they cover, following `cmd/ragflow_server_deepdoc_test.go`.
- CI defines what passing means. See `.github/workflows/release.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `web/src/locales/az.ts` is 235KB. 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/infiniflow/ragflow.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good Go 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/infiniflow/ragflow.svg)](https://agentreadme.com/infiniflow/ragflow)

Other Go repositories, marked

avelino/awesome-go 78 A- ollama/ollama 88 A golang/go 31 D kubernetes/kubernetes 74 B+ microsoft/TypeScript 82 A- JuliusBrussee/caveman 81 A-

All Go 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