Onboard a repo

AGENTS.md agents

OpenAI Codex, the Copilot coding agent, Jules, Devin and the Cursor agent all read AGENTS.md — one concatenated file, generated per profile.

What gets rendered

AGENTS.md structure
…repo-owned context (from templates/repo-context.md)…

<!-- REDLINE:BEGIN — generated. Do not edit inside this block. -->
<!-- Redline v0.1.0 · profile: web-react · stacks: javascript, react -->
# Redline — Core Engineering Standards
# Stack rules — JavaScript · React
<!-- REDLINE:END -->
  • There is no glob mechanism in AGENTS.md, so each section states its scope in prose — “Applies to untyped and loosely-typed JS…”.
  • Everything outside the REDLINE:BEGIN/END markers is repo-owned and survives every sync.
  • The version comment means a repo's artifacts always name the standards version they came from.

Connect an agent

  1. Onboard the repo with npx redlinegate init — the pull request it opens adds AGENTS.md with the profile's stacks.
  2. Point the agent at the repo. Codex, Copilot coding agent, Jules, Devin and Cursor's agent read AGENTS.md by convention — no per-vendor configuration.
  3. Add repo-specific context above the marker block using templates/repo-context.md.
ℹ

The concatenated AGENTS.md for fullstack-node is the largest artifact the renderer produces — keep individual stack files focused when adding rules.