Repository navigation
v0.4.1
Fixed
asitis loadsandload_planwere wrong about @imports from a folder above the start folder. 0.4.0 said Claude Code never expands them. It does, after you approve them: an import whose file sits outside the folder you start Claude in is an external import, and Claude Code asks once per project, in an interactive session, whether to allow external imports. Yes loads them from then on,claude -pincluded; no keeps them off and the question doesn't come back.claude -pnever asks, so until someone has said yes there, they don't load in scripts or CI. My 0.4.0 canary only usedclaude -p, which is why it looked like "not expanded". Checked again on Claude Code 2.1.312 and 2.1.325, interactive and headless, both answers. Such imports are now listed under "Only after you approve imports from outside the start folder", not counted at launch, with a warning that says whatclaude -pdoes. An ancestor's import of a file inside the start folder loads at launch, and a start-folder file's@../x.mdwaits for approval like an ancestor's.context_budgetcounts from the project root, where nothing in the project is external, so its numbers don't change.asitis loadswarned "there is a CLAUDE.md" when the only file hiding AGENTS.md was a CLAUDE.local.md. It names CLAUDE.local.md now.asitis loadsindented an import that waits for approval as if it hung under the line above it (9. AGENTS.md). Imports are indented only under a file listed in the same group now.
Details: packages/mcp/CHANGELOG.md and plugins/asitis/CHANGELOG.md.