Skip to content

Behaviour configuration ​

VariableDefaultDescription
AIDEV_ENV_EXTEND—Path to a global env file loaded as the base for this project
AGENTSclaude,cursorComma-separated list of agents in priority order
DEV_NOTES_MODEsmartWhen to ask for clarification (smart or always)
AIDEV_TRIGGER_WORDaidev-continueComment containing this word re-triggers a skipped task
AIDEV_COMMENT_PREFIX[aidev-$PROJECT_NAME]Prefix for aidev comments; $PROJECT_NAME expands to the project folder name
CONSULT_TAG{folder}-consultTag/label this agent watches for consult requests
CONSULTED_TAG{folder}-consultedStats marker applied after consult completes
AIDEV_HOOKS_PATH—Path to a .ts or .js module that exports hook functions (see Hooks)
ACCEPTED_TAGacceptedTasks in review with this tag are auto-merged (see Auto-merge)
AUTO_APPROVEfalseWhen true, apply ACCEPTED_TAG as soon as an open task is picked up
AGENT_REVIEW_TAGagent reviewTasks in review with this tag get an automated PR code review (see Agent review)
AUTO_REVIEWfalseWhen true, apply AGENT_REVIEW_TAG as soon as an open task is picked up
DONE_STATUSauto-detectedStatus to set after auto-merging an accepted PR
PR_SIGNATUREAutomated PR by aidev.Custom signature line appended to the PR body
AIDEV_SAFE_MODEtrueRedact secret env values from AI prompts (see Safe mode below)
AIDEV_AUTO_COMPRESStrueAuto-compress older comments when the prompt grows large
AIDEV_COMPRESS_THRESHOLD12000Char-length threshold that triggers compression
MCP_JSON_PATHauto-discoveredPath to a generic mcp.json injected into every agent — see MCP servers
BETTER_MCPfalseRoute all MCP traffic through the better-mcp Docker proxy (requires docker)
BETTER_MCP_CONFIG_PATH.aidev/better-mcp.jsonUser-authored better-mcp base config; mcpServers is injected, middleware is preserved

Safe mode ​

When AIDEV_SAFE_MODE is enabled (default), aidev scans task prompts for values that match keys in .env / .env.aidev. Matches are replaced with placeholders and the original values are written to:

.aidev/assets/secrets/task-<task-id>.secrets

That file lives under the git-ignored .aidev/assets/ tree alongside downloaded ticket attachments (.aidev/assets/<task-id>/).

How agents access redacted secrets ​

Secret files are not meant to be read into model context. During a run, aidev appends prompt instructions that tell agents to use shell workflows (grep, ls, piping into commands) instead of opening *.secrets files directly.

Attachment files under .aidev/assets/<task-id>/ follow different rules: agents may read them and copy them into the project (e.g. images into public/). See Task assets for Cursor --add-dir, .cursorignore negation, and the prompt fallback used by other agents.

← Back to configuration overview

Released under the MIT License.