Skip to content

Instructions

On each request niminal sends a stable prefix in this order:

  1. The built-in system prompt, or a replacement from SYSTEM.md or --system-prompt
  2. Optional append text from APPEND_SYSTEM.md or --append-system-prompt
  3. Project instructions from AGENTS.md, AGENTS.override.md, or CLAUDE.md
  4. An ACT mode block that tells the model to implement and verify changes

From ~/.niminal/, niminal loads the first file that exists in this order:

  1. AGENTS.override.md
  2. AGENTS.md
  3. CLAUDE.md

It then walks from the git root toward the workspace directory (less-specific first) and loads the same filename precedence in each directory.

Each file is capped at 64 KiB. Larger files are truncated with an [instructions truncated] marker.

Use --no-context-files or -nc to skip AGENTS and CLAUDE discovery for one process. System prompt files and flags still apply.

Replace the built-in identity with the first match:

  1. --system-prompt TEXT
  2. <workspace>/.niminal/SYSTEM.md when the project is trusted
  3. ~/.niminal/SYSTEM.md

Append extra rules with the first match:

  1. --append-system-prompt TEXT
  2. <workspace>/.niminal/APPEND_SYSTEM.md when the project is trusted
  3. ~/.niminal/APPEND_SYSTEM.md

Project instructions still load after the append text unless you pass --no-context-files.

Nested AGENTS.md files are not appended to every request. When you read a path under a directory that has its own instruction file, niminal attaches that scoped text once with the read output.

Use /reload after changing trusted project resources so discovery caches refresh.

Project AGENTS.md and other instruction files in the git-root chain load without trust. Project SYSTEM.md and APPEND_SYSTEM.md require trust, like skills, prompts, tools, and extensions.

Portable files under ~/.niminal/ always load.