Skip to content

Holoself 0.8.0 — context where you work

Latest
Latest

Choose a tag to compare

View all tags
@smota smota released this 31 Aug 20:02
v0.8.0
b503699
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Holoself 0.8.0 — context where you work

Holoself can now meet AI tools inside an already linked project. The new local MCP integration gives supported clients typed, on-demand access to bounded self-context while preserving the explicit link, review boundaries, and local ownership that make Holoself trustworthy.

What this changes for you

  • Configure Codex, AGY, and Claude Code from one previewed workflow: holoself mcp configure.
  • Let an AI inspect a compact manifest and request only the relevant sources instead of loading your context eagerly.
  • Search and retrieve context through the same deterministic lens, privacy, lifecycle, and provenance rules used by the CLI.
  • Draft a project-local pending learning and preview its effect without giving the AI authority to approve or save it into canonical self-context.
  • Check generated client configuration separately from proven native behavior with holoself mcp status.

Local by design

MCP runs as a project-bound STDIO subprocess started by the agent client. It is not a daemon or standalone service, opens no port, makes no network request, and accepts no tool-supplied filesystem paths.

The linked project's .holoself/link.yaml remains the authorization boundary and points to HOLOSELF_DATA even when the request starts in that project folder. The server validates that link on every operation, respects its granted lens, and does not reveal the private data-root path in results or errors.

Read tools are physically non-mutating: they do not persist a cache or rebuilt search index. Proposal tools can only create pending files inside the linked project and preview their effect. Approval, canonical writes, link changes, cleanup application, skill installation, and publication remain outside the MCP surface.

Safer setup

Project-local configuration is collision-aware, idempotent, and transactional. Holoself previews all target files, refuses divergent or unsafe existing state, and restores the exact previous state if a later client configuration fails.

Six tools are available:

  • holoself_status
  • holoself_context_manifest
  • holoself_context_get
  • holoself_search
  • holoself_proposal_create
  • holoself_proposal_preview

Default and compatibility

The explicit project link is still the control-plane default. The shared Holoself skill and CLI remain the most deterministic cross-platform interaction path, with BOOTSTRAP instructions, reviewed snapshots, and Workbench available as fallbacks.

Codex and Claude Code have verified native discovery and status calls. AGY has verified native discovery in a registered synthetic project, while its non-interactive call correctly stopped at the normal MCP approval boundary. MCP is activated in this release, but it will become the preferred interaction default only per platform and version after the complete native verification matrix passes.

Upgrade

From an already linked project:

holoself mcp configure
holoself mcp configure --apply
holoself mcp status

Review and commit client configuration only when it belongs in that project's collaboration contract. Configuration can disclose the existence of a local Holoself integration even though it contains no private context.

Full details: local MCP guide, tool reference, architecture decision, and platform verification.

Assets 2
Loading