agentreadme

Report · marked 25 Aug 2026

coollabsio/coolify

Solid foundations, held back in a few specific places.

PHP · 61,035 stars · 3,971 files · branch main

Fix these first

01
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.
02
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.
03
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 25/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: it's 25k characters, which burns context on every single turn.
names the actual commands to run
uses headings, so an agent can skim it
includes copyable code blocks
README as an entry point 3/3
README has a clear getting-started section.
Setup 14/20 B+

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 (dev, build, clean)
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 0/2
No pinned runtime version.
Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.
Reproducible environment 2/2
docker-compose.yml gives a known-good environment.
Verification loop 12/25 C+

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

Tests exist 8/8
888 test files against 2263 source files.
e.g. .dev/lima/coolify-naked-test.yaml, docker/coolify-realtime/terminal-utils.test.js, docs/superpowers/specs/2026-08-17-external-tls-http-redirect-design.md
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
18 GitHub Actions workflows define what "passing" means.
Lint and format rules 0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
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 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 51 patterns.
File sizes fit in context 0/6
25 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.
public/js/monaco-editor-0.52.2/min/vs/language/typescript/tsWorker.js — 5615KB
public/js/monaco-editor-0.52.2/min/vs/editor/editor.main.js — 3678KB
public/js/monaco-editor-0.52.2/min/vs/language/css/cssWorker.js — 760KB
Repository weight 4/5
About 81.9MB 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 — drafted for coollabsio/coolify
# AGENTS.md

An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 280+ one-click services on your own servers.

## Setup

```
bun install
```

## Commands

```
bun dev     # run locally
bun build   # produce a build
bun clean
```

## Layout

- `tests/`     830 source files
- `app/`       774 source files
- `resources/` 436 source files
- `public/`    106 source files
- `database/`  39 source files
- `config/`    27 source files

## Conventions

- Tests live alongside the code they cover, following `.dev/lima/coolify-naked-test.yaml`.
- CI defines what passing means. See `.github/workflows/chore-lock-closed-issues-discussions-and-prs.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `public/js/monaco-editor-0.52.2/min/vs/language/typescript/tsWorker.js` is 5615KB. 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/coollabsio/coolify.md

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 73 out of 100

[![agent ready](https://agentreadme.com/badge/coollabsio/coolify.svg)](https://agentreadme.com/coollabsio/coolify)

Other PHP repositories, marked

danielmiessler/SecLists 34 D nextcloud/server 83 A- laravel/framework 36 D

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