Augment (augment)

• Rules: rule bodies go into the shared ## Rules block of AGENTS.md. Augment also loads .augment/rules/.
  • An always-applied rule that is already in the block gets no .augment/rules/ file. See target behavior.
  • A spec with alwaysApply: false gets type: agent_requested and a description (falling back to the rule name). Rules have no name key.
• Legacy guidelines: outputs.augment.rules-file: .augment-guidelines also writes all rules as one document. It is opt-in, because Augment cuts it first when context runs short.
• Agents (subagents docs): .augment/agents/<name>.md with name (required), description (falls back to the spec name), and, when set, color (written as is; Augment expects an ANSI color name) and model.
  • Augment's tools and disabled_tools take its own tool names (view, codebase-retrieval, str-replace-editor, ...), so the generic tools field raises a sync note. Set x-augment: {tools: [...]} or x-augment: {disabled_tools: [...]} instead.
• Skills: Augment also scans .claude/skills/ and .augment/skills/.
• Commands: .augment/commands/<scope>/<name>.md, with a directory scope from the source folder as a nested folder name. description, argument-hint, and model stay in frontmatter.
• Ignore: ignore specs write .augmentignore. import augment restores a hand-written one, keeping pattern order and negation.

MCP

Servers merge into .augment/settings.json under mcpServers. Stdio uses command, args, and env with no type. Remote uses type: http or type: sse plus url and headers. This is the Auggie CLI project file Augment recommends for team-shared servers (config docs), not the IDE Settings Panel.

• Sync changes only its own keys. shell, startupScript, theme, plugin keys, and tool permissions stay.
• If the file is JSONC, sync drops comments and trailing commas and prints a one-line warning. Keys stay, comments do not.
• Augment documents no per-server disabled key, so disabled: true is dropped with a sync note. Use auggie mcp remove.
• Transports are stdio, sse, and http only (integrations docs). A type: ws spec writes no server and raises a sync note.

Hooks

Hooks merge in under hooks, in the same write as mcpServers. Supported events: PreToolUse, PostToolUse, Stop, SessionStart, SessionEnd (hooks docs). agnostic-ai hook run tests them before a session, using Auggie's event data, shell, and timeout.

• timeout is in milliseconds: the spec's seconds times 1000 (vendor default 60000).
• command must be a script ending in .sh, .ps1, .cmd, or .bat, because Augment never runs an inline shell string. Other commands are written as is with a sync note. A hook with args is skipped with a note, because Augment has no shell to fold them into.
• matcher is optional on PreToolUse and PostToolUse (vendor default .*) and left out on the session events.
• Matchers use Augment's tool names (launch-process, str-replace-editor, save-file, ...). A Claude-style matcher (Bash, Write, ...) matches nothing and raises a sync note.

Shared memory

With builtins: [memory], sync adds an executable .augment/hooks/memory-augment-session-start.sh and a SessionStart entry for Auggie CLI on its supported platforms: macOS, Linux, and Windows WSL. The script finds the project from its working directory and returns both memory indexes through hookSpecificOutput.additionalContext. The same script is installed for sync --global. Auggie 0.x injects that output. The 1.x prerelease runs SessionStart hooks in the background and does not add their output to the agent's context (1.x hooks docs), so there the memory rule tells the agent to read the indexes.

The IDE keeps the memory rule. See shared memory for the context limit and how to keep the tool's own memory.

Permissions

Settings specs merge into the same file under toolPermissions, which Auggie CLI and Cosmos cloud agents follow. Augment recommends committing .augment/settings.json so the policy applies to every cloud agent in the repo (permissions docs).

• Rules are an ordered array and the first match wins, so deny rules come first.
• Each permission is an object such as { "type": "deny" }. Augment ignores a bare-string permission.
• Bare tool names map onto Augment's six tools (Read to read, Bash to terminal, WebFetch to web-fetch, ...).
• Bash(prefix:*) becomes a terminal rule with shellInputRegex: ^prefix. An exact Bash(command) is anchored at both ends. mcp__<server>__<tool> becomes {tool-name}_{server-name}.

These are not written and raise a sync note:

• model: the file has no documented key.
• The ask list: none of Augment's types (allow, deny, webhook-policy, script-policy) prompts.
• Path- or URL-scoped rules such as Read(src/**): only terminal takes a matcher, and a bare read would cover every file.

x-augment.toolPermissions writes Augment's rule objects as is, ahead of the translated ones. Other x-augment keys, such as shell or startupScript, merge in as written.