Repository navigation
ContextOS v1.2.0
ContextOS 1.2.0 provides local groups of projects, separate branch/worktree indexes, workspace-wide retrieval and verified cross-project knowledge through one MCP server.
- Group projects with
contextos group createandcontextos init --group; query an active checkout, selected projects or the entire group. - Inspect exact local imports and API contracts, save evidence-backed relationships, and follow them with
ctx_trace. - Global npm installation sets up instructions for detected supported agents and refreshes known projects while preserving user guidance and knowledge. New projects still require initialization.
- Fix first-query JSON output during indexing, wait for live watcher readiness after project re-add, and ensure verified older daemons are replaced during an upgrade, including when clients are connected.
Install or upgrade:
npm install -g @siddharthakatiyar/contextos@1.2.0Reconnect your coding agent after upgrading. Use contextos setup --check --json and contextos doctor --client <client> --noninteractive to inspect setup.
Validation: 491 automated tests and ten real installed-package checks passed, including a live upgrade from published 1.1.1, client reconnection and knowledge retention. Tests cover groups, multiple repositories, Git worktrees, ranking, MCP isolation, verified relationships, watchers and cleanup. All 400 fixture-scoped rankings matched v1.1.0, payment-role Recall@10 was 100%, and latency stayed within the stated bounds.
Native agent adoption remains environment-dependent: Codex's noninteractive policy blocked MCP calls here, and Claude/Grok were unauthenticated. SDK/stdio integration checks passed; those native sessions are not claimed as verified. Production/workspace audit found no high or critical advisories, with seven moderate/low advisories remaining.
See the validation report, testing guide, and changelog.
External scan limitation: JSMon failed to complete its scan and reported no findings or annotations. GitHub rejected a rerun request. The four-platform CI matrix, benchmark, GitGuardian and production advisory gate passed. The JSMon check is not required by branch protection.