Neocortex

Product updates · 5 November 2026

A platform that keeps moving forward.

A customer-facing summary of recent work in the Neocortex source repository: knowledge workflows, integration diagnostics, provider contracts, terminal capabilities and safer finance imports.

Merged source work · deployment-dependentRead source release notes

Recent merged work

Product capabilities, with the boundaries made clear.

The source repository records merged code and release-note entries. Availability still depends on the target deployment, configuration and validation; this page does not imply that every change has reached production.

Merged · Nov 2026

Atlas knowledge capture and review

Recent source changes add rules-based suggestions for unlinked mentions, Atlas records in the Ctrl+K palette without taking over text-entry fields, and a review step that holds Obsidian notes before import.

Merged · Nov 2026

Integration diagnostics and recovery

MCP integration health diagnostics now surface account-cap recovery guidance and subdomain validation, making connection problems easier to identify before they interrupt a workflow.

Incremental delivery

Provider catalogue contract checks

A new drift guard checks that the TypeScript provider catalogue stays aligned with its .NET counterpart. This supports Neocortex’s direction toward portable, framework-neutral routing without claiming every runtime is interchangeable.

Merged · Nov 2026

Capability-aware terminal execution

The latest terminal work adds device-capability detection and target resolution, moving the runtime architecture toward matching work to hosts with the capabilities it needs.

Merged · Nov 2026

Safer finance imports

Bank and supplier-bill CSV imports now include a dry-run preview, so operators can inspect proposed changes before applying them.

Current architecture

Dedicated deployment boundaries

Neocortex is a private, single-operator application today. Customer deployments are dedicated instances rather than a shared multi-tenant pool; organisation-aware data foundations do not yet mean universal multi-user access enforcement.

Product direction

Governed work, not just agents

The architecture is progressing toward durable, reviewable workflows: capture context, route to the right tools and runtimes, keep human review where it matters, and make outcomes observable. Availability still depends on the deployment and its validation.

Keep exploring

From current capability to the next priority.