OA
OpenAkashic
Remote Agent Enrollment
///

Remote Agent Enrollment

When a new server or agent instance joins, attach it to the same Closed Akashic MCP endpoint, the same machine-level auth source, and the same project-index workflow so memory stays shared instead of drifting.

///

Summary#

When a new server or agent instance joins, attach it to the same Closed Akashic MCP endpoint, the same machine-level auth source, and the same project-index workflow so memory stays shared instead of drifting.

Enrollment Checklist#

  1. Configure Closed Akashic MCP auth on that machine. - Preferred for shared local Codex/agent hosts: a machine-local static Authorization: Bearer <redacted> header in the host-level MCP config. - Fallback: CLOSED_AKASHIC_TOKEN as an environment-variable token source when the token cannot be stored in config or the runtime reliably resolves env vars. - Never write the real token into repos, project notes, AGENTS.md, CLAUDE.md, logs, or tool output.
  2. Register https://knowledge.openakashic.com/mcp/ in the agent client.
  3. Create or update the host-level ~/.codex/AGENTS.md from Codex AGENTS Template when the host runs Codex.
  4. Smoke-test retrieval with search_notes and read_note.
  5. Smoke-test write access with append_note_section or upsert_note on a safe operations/test note.
  6. If the project is new, create its README index and initial project folders with bootstrap_project.
  7. Restart the relevant agent session after changing host-level MCP config or environment injection so the new auth source is actually loaded.
  1. Search the project name.
  2. Read the project README.
  3. Append a short dated section to a safe operations note or create a tiny temporary test note.
  4. Confirm the note is visible in the browser surface and retrievable over MCP.
  5. If any step fails, inspect MCP Debugging and Logs.

Project Enrollment#

Use bootstrap_project when the project has no README yet.

Recommended inputs: - project: <scope>/<project>, for example personal/openakashic, company/acme, research/llm-notes, or ops/aws - title: human-readable project title - summary: one-line description of what belongs in that workspace - canonical_docs: repo doc paths or URLs - folders: optional project-specific folder list when the defaults are not right

Reuse#

This playbook is the default way to attach a new server, not a special case. If a new machine can follow these steps and retrieve the same note graph, the memory system is behaving correctly.

Claude Code Enrollment#

Claude Code는 프로젝트 루트의 CLAUDE.md를 매 세션 시작 시 자동 로드한다. Codex의 AGENTS.md, Cursor의 .cursor/rules/*.mdc와 동등한 역할이다.

Claude Code 추가 단계#

  1. MCP 서버를 Claude Code/Claude runtime의 지원 방식에 맞게 등록한다. - 원격 HTTP MCP가 static header를 지원하는 runtime이면 Authorization: Bearer <redacted> 형태의 header를 machine-local config 또는 secret injection 경로로 넣는다. - 해당 runtime이 static bearer header를 직접 지원하지 않거나 제품 버전별 동작이 불명확하면 local stdio proxy, launcher, OS secret manager, service environment, 또는 조직 connector에서 header injection을 맡긴다. - 토큰 원문을 CLAUDE.md, repo JSON, 프로젝트 노트에 직접 남기지 않는다.
  2. 프로젝트 루트에 CLAUDE.md를 생성한다 — 템플릿은 Claude Code CLAUDE.md Template 참조.
  3. Smoke-test: 세션에서 list_folders 또는 동등한 discovery 도구 → search_notes → append_note_section 순으로 호출해 읽기/쓰기 모두 확인.
  4. 기존 Enrollment Checklist의 retrieval/write/project-enrollment 단계는 동일하게 적용한다.

기존 에이전트와의 정합성#

  • CLAUDE.md의 핵심 규칙(메모리 검색→작업→write-back, 도커 배포→검증)은 Codex AGENTS.md / Cursor .mdc와 일치시킨다.
  • 하나가 바뀌면 나머지도 함께 갱신해야 drift가 안 생긴다.
  • 갱신 체크리스트: ~/.codex/AGENTS.md + 프로젝트 AGENTS.md + .cursor/rules/closed-akashic-mcp.mdc + CLAUDE.md.

발견 경위#

2026-04-16 arc-fleet 세션에서 Claude Code가 MCP 연결은 됐지만 행동 지침 누락으로 배포 검증·메모리 write-back·사전 검색을 모두 건너뛴 것을 확인. Codex/Cursor와 달리 Claude Code의 enrollment 단계가 플레이북에 없었음이 원인.