One reviewed setup
Preview and configure project-bound MCP for Codex, Claude Code, and supported AGY projects from one local workflow.
Holoself keeps approved personal context in readable local files, links it to independent projects through task-specific lenses, and asks before project discoveries become durable knowledge.
Supported AI clients can request bounded context inside an already linked project, on demand—without a daemon, hosted account, or second source of truth.
Preview and configure project-bound MCP for Codex, Claude Code, and supported AGY projects from one local workflow.
Typed status, manifest, context, and search tools return structured, size-bounded results with provenance.
The project link remains the authority. MCP cannot broaden a lens, approve proposals, or write canonical context.
The Workbench, CLI, shared skill, BOOTSTRAP, and reviewed snapshots remain deterministic ways to work.
Lenses change relevance, depth, and privacy—not identity.
Identity, preferences, voice, evidence, decisions, stories, and domain context.
Career, publishing, technical, leadership, interview, general, or private.
Applications, posts, research, code, and other project-owned artifacts stay local.
Identity, preferences, durable facts, approved stories, decisions, disclosure rules, and evidence.
Applications, research, interview notes, posts, calendars, performance data, templates, and execution strategy.
Bring your voice, preferences, evidence, and decisions into new work without copying a complete profile into every project.
Career and publishing workspaces can read the same self context while retaining their own artifacts and private details.
Holoself shows target, evidence, affected files, and proposed diff before an approved canonical update.
Use approved achievements and leadership stories while keeping job research, compensation, and interviewer strategy project-owned.
Explore career use caseRetrieve public-safe claims and approved stories while filtering employer-confidential or career-private material.
Explore publishing use caseCarry decision principles and technical preferences into architecture or coding projects without centralizing their source artifacts.
Explore technical use caseNo hosted account or required external service.
Generated packets and indexes never become source of truth.
Visibility, sensitivity, public-safety, and field restrictions filter output.
Resolved context and accepted claims identify their source files.
Project-bound MCP gives verified clients typed, on-demand access to the same lens, privacy, lifecycle, and provenance rules as the CLI. Codex and Claude Code discovery were verified for 0.8.0; AGY verification remains bounded by its project registration and approval policy.