Use case
I've been running long-lived sessions in my home directory (outside any git repo) for two purposes:
- Global troubleshooting sessions: Cross-project debugging, cluster diagnostics, infrastructure exploration — work that doesn't belong in any single project repo.
- Quick chat agent: An unprompted agent for ad-hoc questions, research, and exploration without the overhead of project context.
These sessions have accumulated significant memory and context over weeks of use. The agent learned troubleshooting patterns, infrastructure knowledge, and my working preferences that carry across projects.
What changed
As of v0.32.4 (Jul 20, commit ad1e540: "mason: add identity merge and home binding gates"), Magic Context stopped loading in home-directory sessions. The home binding gates intentionally restrict Magic Context to projects with stable identities (git repos or designated paths).
Request
I understand the design rationale: project memories should be scoped to stable project identities, not loose directory paths. However, home-directory sessions serve a real purpose and have genuine, accumulated value.
Proposed solution: Add a configuration flag (e.g., "allow_home_sessions": true or "bind_to_home": true) to explicitly opt back into Magic Context support for home-directory sessions. This way:
- The default behavior remains project-focused (safe, stable).
- Users with a deliberate use case can opt in.
- Existing memory built up in home sessions is not lost.
Impact
Without this, all context and memory from home-directory sessions is inaccessible, despite being intact in the Magic Context database. A user upgrading to v0.32.4+ loses functionality they relied on.
Additional context
- Magic Context is fully installed and passing diagnostics.
- The shared database (
~/.local/share/cortexkit/magic-context/context.db) contains all home-session data intact.
- This appears to be an intentional gating mechanism, not a bug — but the migration path for existing home sessions is unclear.
Use case
I've been running long-lived sessions in my home directory (outside any git repo) for two purposes:
These sessions have accumulated significant memory and context over weeks of use. The agent learned troubleshooting patterns, infrastructure knowledge, and my working preferences that carry across projects.
What changed
As of v0.32.4 (Jul 20, commit ad1e540: "mason: add identity merge and home binding gates"), Magic Context stopped loading in home-directory sessions. The home binding gates intentionally restrict Magic Context to projects with stable identities (git repos or designated paths).
Request
I understand the design rationale: project memories should be scoped to stable project identities, not loose directory paths. However, home-directory sessions serve a real purpose and have genuine, accumulated value.
Proposed solution: Add a configuration flag (e.g.,
"allow_home_sessions": trueor"bind_to_home": true) to explicitly opt back into Magic Context support for home-directory sessions. This way:Impact
Without this, all context and memory from home-directory sessions is inaccessible, despite being intact in the Magic Context database. A user upgrading to v0.32.4+ loses functionality they relied on.
Additional context
~/.local/share/cortexkit/magic-context/context.db) contains all home-session data intact.