Frequently asked questions

VitaeContext is open-source career-context infrastructure for AI agents and career systems. It helps a person build and maintain private, reusable Career Context in Markdown, then makes selected context available to downstream tools.

Not by itself. VitaeContext supplies the grounded context layer before those tasks. A downstream agent, CV builder, application workflow, or profile tool uses the Career Context and applies its own task-specific method.

11 install targets: Codex, Claude Code, Cursor, Windsurf (Cascade), Roo Code / Cline, Gemini CLI, Antigravity, OpenCode, IBM Bob (watsonx), xAI Grok, and a portable shared bundle. In Claude Code the skills are also available through the plugin marketplace, and tools supporting Model Context Protocol can connect via stdio.

VitaeContext includes a native, zero-dependency MCP server conforming to protocol version 2024-11-05. Compatible agents can query selected local Career Context and VitaeGraph records without copying those files into every project workspace.

Run npx vitaecontext install --provider <provider> with one of the supported provider values, or run the stateless MCP server with npx -y vitaecontext mcp. In Claude Code you can also add the plugin marketplace with /plugin marketplace add vitaecontext/vitaecontext and /plugin install vitaecontext@vitaecontext. See the installation guide and CLI reference for every command and flag.

Career Context is a user-owned, maintained Markdown record for one person's supplied career facts, roles, projects, evidence links, constraints, claims to avoid, and goals recorded as stated intent. Downstream agents can read the relevant parts so work starts from the same inspectable source.

VitaeGraph is VitaeContext's optional deeper layer for local Markdown records such as education, thesis work, courses, projects, experience, certifications, awards, and publications. It complements compact Career Context instead of replacing it; its validation checks structure rather than authenticating claims.

Three: the root vitaecontext router, vitaecontext-build for compact Career Context, and vitaecontext-vitaegraph for optional deeper records. Version 2.3 removed the former CV, LinkedIn, GitHub, portfolio, and X adaptation modules.

No. Platform names, trademarks, and logos belong to their respective owners. VitaeContext is independent and is not affiliated with, sponsored by, or endorsed by those platforms.

VitaeContext is a set of Markdown skill files and a local CLI with no backend, so the project itself collects nothing. Your context file is a private local file you control. How any individual agent or provider handles the content you give it is governed by that provider, not by VitaeContext.

No. VitaeContext keeps supplied facts, evidence links, stated intent, and unresolved claims visibly separate. Validation checks the artifact's structure and internal consistency, not the truth of every real-world claim.