You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(config): a project-root altimate-code.json is ignored, including its permission rules #1589
docs/docs/configure/config.md and docs/docs/configure/permissions.md say a project-root altimate-code.json is read. It isn't: config.ts calls ConfigPaths.files("opencode", …), which only looks for opencode.json(c) at the root. A root opencode.json and .altimate-code/altimate-code.json both load.
Repro on the 0.12.8 build: project-root altimate-code.json with {"permission":{"read":{"*secret.txt":"deny"}}}; debug config shows no permission, and the agent reads secret.txt. The same file under .altimate-code/ denies the read.
This matters because a user who follows the docs to add deny rules gets no protection and no warning. Either load the root altimate-code.json (with defined precedence against opencode.json), or fix the docs and warn when the file is present but ignored. In the code since v0.11.1 (cf46d65).
Found during the v0.12.8 release e2e. Not a regression in 0.12.8: the same behaviour is in 0.12.7.
Load a project-root altimate-code.json (and .jsonc) in config.ts next to opencode.json, with a defined precedence: .altimate-code/altimate-code.json over a root altimate-code.json over a root opencode.json, merged the same way the existing files are.
Show the loaded file in debug config, so it's clear which file a rule came from.
Tests: your repro (a root altimate-code.json deny on *secret.txt now denies the read), the precedence between the three files, and no change when only opencode.json is present.
Update config.md and permissions.md to spell out the precedence.
Activity
rahulsjha commentedon Nov 20, 2026
Hi @sahrizvi, I'd like to fix this one.
Plan:
altimate-code.json(and.jsonc) inconfig.tsnext toopencode.json, with a defined precedence:.altimate-code/altimate-code.jsonover a rootaltimate-code.jsonover a rootopencode.json, merged the same way the existing files are.debug config, so it's clear which file a rule came from.altimate-code.jsondeny on*secret.txtnow denies the read), the precedence between the three files, and no change when onlyopencode.jsonis present.config.mdandpermissions.mdto spell out the precedence.