Nolane Habitat

Project intelligence for coding agents.

Nolane Habitat gives an agent a durable, revision-aware workspace for understanding and evolving a software project. It combines semantic project context, governed source changes, verification, task checkpoints, an MCP interface, and a read-only Observatory in one local system.

What Habitat brings to an agent

• Durable project memory — a SQLite-backed workspace records source identity, semantic evidence, context, checkpoints, and verification history.

• Focused semantic context — agents can start a task, inspect relevant objects, follow references, and continue with bounded context instead of rebuilding understanding from scratch.

• Governed source evolution — journaled mutations, source anchors, transaction recovery, and path-scoped verification support deliberate code changes.

• Live project awareness — Habitat reconciles source revisions and keeps task context aligned with the working project.

• Codex-native operation — an MCP adapter exposes task, context, inspection, change, verification, UI, checkpoint, and resume workflows to Codex.

• Clear observability — the loopback Observatory presents project and agent activity through a read-only runtime surface.

Related MCP server: WorkspaceGuard

Quick start on Windows

Python 3.10+ is required. Clone the repository, then create a virtual environment with the development, MCP, and Python semantic capabilities:

git clone https://github.com/Nolane-x/Nolane-habitat.git
cd Nolane-habitat
python -m venv .venv
.\.venv\Scripts\python -m pip install -U pip
.\.venv\Scripts\python -m pip install -e ".[dev,mcp,python-semantic]"

Create a Habitat workspace beside the source project, then orient a task:

$source = (Resolve-Path .).Path
$workspace = "$source.habitat"
.\.venv\Scripts\habitat.exe create $source $workspace
.\.venv\Scripts\habitat.exe enter $workspace
.\.venv\Scripts\habitat.exe orient $workspace "map the authentication flow"

The workspace is intentionally separate from the source directory, keeping Habitat state independent from the project it understands.

Use it with Codex

Register the initialized workspace as an MCP server:

$python = (Resolve-Path .\.venv\Scripts\python.exe).Path
codex mcp add nolane-habitat -- $python -m habitat.mcp_adapter $workspace --no-open-observatory
codex mcp list

Install the bundled Codex skills from the local checkout:

$repo = (Resolve-Path .).Path
codex plugin marketplace add $repo
codex plugin add nolane-habitat@personal

Start a Codex task with $nolane-habitat to use the project workspace, or $nolane-habitat-maintainer when improving Habitat itself. The full setup and day-to-day workflow are in Codex integration.

A practical development loop

1. Create or open a Habitat workspace for the project.

2. Start a task and gather bounded semantic context.

3. Inspect symbols and references before editing.

4. Apply an authorized source change through the governed workflow.

5. Verify affected paths and checkpoint the result for the next agent.

This loop makes context, changes, evidence, and handoffs durable across longer-running agent work.

Core surfaces

Documentation

• Install and run Habitat

• Connect Habitat to Codex

• Use the agent protocol

• Explore the architecture

• Review the changelog

Verify a checkout

.\.venv\Scripts\python tools\run_test_matrix.py --workers 1 --timeout 180

Nolane Habitat 0.1.0-alpha.18 is ready for local project cognition, governed agent workflows, and Codex integration.