Use KOS with an AI agent

Goal and prerequisites

Let an installed agent work on one vault under explicit permissions. Your agent account, executable and provider configuration are separate from KOS.

Understand the layers

KOS: files, project structure and context rules.
Obsidian or your editor: reads and edits the workspace.
Agent: reasons over accessible information and may act using granted tools.
Adapter: connects the provider’s instruction conventions to KOS.
Skill or Power-Up: adds a reusable task procedure or packaged capability.

Community setup

Starter Kit 1.2.0 can generate selected Codex, Claude and Gemini adapters through installation.providers in the answer file. The root AGENTS.md is the shared router; selected adapter files include CODEX.md, CLAUDE.md or GEMINI.md. File generation does not prove your agent loaded them.

Claude Code setup

Install and sign in to Claude Code using its official setup instructions. KOS does not provide an account or provider subscription.
Select the Claude adapter during Community installation, then open a terminal at the installed learning-vault root. Confirm that the generated CLAUDE.md points to the shared router; Claude Code loads its own instruction filename.
Start claude there. Permit only the intended learning files, then ask it to follow AGENTS.md, the working profile and the selected project. Review its file evidence before writes.
Complete the first useful task, save the accepted facts and start a new conversation without the old transcript. Repeat after correcting a saved date.

Claude Code 2.1.220 on Windows passed two independent read-only Community sessions in this docs audit: one recovered saved facts; the next used an edited due date. This is a bounded context-retrieval check, not certification of all tools or Pro combinations. See Claude instruction loading.

Codex setup and qualification

Open the learning vault as Codex’s working folder and confirm the root AGENTS.md is discovered. Codex’s instruction guide describes its automatic AGENTS.md loading; a generated CODEX.md alone is not proof of discovery. Run the same fresh-session exercise and inspect the files used.

The installed Codex CLI 0.145.0 could not execute this audit’s configured model: the service required a newer CLI. That combination is unqualified here. Follow the official installation/update guidance and repeat the exercise on your actual tool/model version before relying on it. No passing Codex session is claimed.

Gemini adapter boundary

The Starter package can generate a GEMINI.md adapter. No Gemini executable was available in this audit, so runtime setup and fresh-session continuation remain unqualified. Use the current provider instructions and the same learning-vault exercise; adapter generation alone does not establish working integration.

Verify the current session

Open the vault in your chosen tool. Ask it to identify the root router, working profile and relevant project context, with file evidence. Check its permissions before any file changes. Run the first useful task and its fresh-session test.

Switching agents

Save approved context and refresh the handoff before switching. In the new tool, verify its working directory, selected adapter and loaded files. A compatible Markdown format does not make provider-specific tools or permissions portable.

Consult your agent’s current official instruction-loading documentation and KOS compatibility. Do not compensate by granting access to every directory or copying private context into public instructions.