AGENTS.md files
AGENTS.md is a file convention recognized by many coding-agent runtimes. Flezise generates one for your repository from the project's approved specifications, so any agent working in the repo inherits your architecture decisions, coding conventions, and operational commands without being told about them separately.
What the file contains
Flezise assembles the file from your approved artifacts. Each section appears only when a matching approved artifact exists. Missing sections are omitted.
Only the latest approved version of each artifact contributes content. Drafts and in-review versions are excluded. A provenance footer at the bottom of the file records the generation timestamp and the artifact types that were included.
Preview the current file
To see what the file would contain right now, call:
The response is the rendered file as plain text. Regenerate after you approve a new version of any contributing artifact.
Deliver to your repository
Delivery to the repository is opt-in. Enable pipeline_config.agents_md.delivery_enabled on the project, then call:
Flezise creates a branch, commits the file, and opens a pull request titled chore: update AGENTS.md from approved artifacts. The PR body explains which artifacts were used and instructs reviewers not to hand-edit the file; regenerate it from the platform when content changes.
Inject into builder sandboxes
When the builder agent runs in a sandbox, Flezise can write the generated AGENTS.md into the workspace before the session starts. Enable pipeline_config.agents_md.sandbox_inject on the project to turn this on. It is off by default.
With injection on, the builder agent reads the file as part of the workspace and applies your project conventions without receiving them as a separate prompt addition.
Scaffold seeding
When you import a codebase using a stack pack, Flezise writes a minimal AGENTS.md to the repository root as part of the scaffold, provided one does not already exist. This scaffold file names the stack pack and the primary directories from the pack metadata. It is a starting point. Once your project artifacts are approved, deliver the full generated file to replace it.