Problem
When rendering via perseus render in a workspace with a pack.yaml, the mimir: block in pack.yaml is not merged into the global ~/.perseus/config.yaml. This means a workspace cannot override mimir.context_limit or mimir.enabled on a per-workspace basis.
Observed behavior
A workspace pack.yaml with:
mimir:
enabled: true
context_limit: 0
...has no effect. The renderer uses only the global ~/.perseus/config.yaml for Mimir settings.
Expected behavior
Pack-level mimir: config should deep-merge over global config, allowing per-workspace overrides of context_limit, enabled, etc.
Use case
A user has two render targets: a primary workspace (wants full Mimir context) and a secondary workspace (wants no Mimir auto-inject to avoid duplicating the same block already present in the primary). Currently impossible without disabling Mimir globally.
Workaround
Change secondary workspace render output to a non-AGENTS.md path so the runtime does not auto-load it.
Problem
When rendering via
perseus renderin a workspace with apack.yaml, themimir:block inpack.yamlis not merged into the global~/.perseus/config.yaml. This means a workspace cannot overridemimir.context_limitormimir.enabledon a per-workspace basis.Observed behavior
A workspace
pack.yamlwith:...has no effect. The renderer uses only the global
~/.perseus/config.yamlfor Mimir settings.Expected behavior
Pack-level
mimir:config should deep-merge over global config, allowing per-workspace overrides ofcontext_limit,enabled, etc.Use case
A user has two render targets: a primary workspace (wants full Mimir context) and a secondary workspace (wants no Mimir auto-inject to avoid duplicating the same block already present in the primary). Currently impossible without disabling Mimir globally.
Workaround
Change secondary workspace render output to a non-
AGENTS.mdpath so the runtime does not auto-load it.