Select Codex, Claude Code, or Gemini CLI and approve the proposed local paths and permissions.
Last reviewed:
About this guide
This guide was prepared with AI assistance using the project’s public documentation. It does not claim testing on every device or independent human review. Project publisher: AmirSina Zamanian.
Sources are listed at the end. Use the project repository to report an error or suggest a correction. Report an issue
⌕
Search runs on this device.
On this page
Overview
Choose only tools you actually use. Connections are independent, and adapters are installed only for selected tools. A future compatible tool needs a validated Connector Contract; registration does not enable or install it.
Match tools and adapters
Codex uses AGENTS.md, Claude Code uses CLAUDE.md, and Gemini CLI uses GEMINI.md. Select only tools you use and review existing instruction files before changes. Installing an adapter does not authorize reading every source.
Approve the project map
Each tool connection is independent. Inspect exact paths, repository identity, and content evidence in the proposed project map. Similar names are insufficient to merge projects. Do not approve an ambiguous match; establish the correct source or path first.
Verify the connection with evidence
A tool name in a list does not prove a working connection. Check the connection record, selected source, and sync result. Future tools require a valid connector contract and supported transport; registration alone does not install or enable them.
Completion checklist
To complete this step, identify the tool, local source, and permission scope. Review the project map: content-based matching requires strong overlap and at least two markers. Correct any false shared-project match before memory is written. A second tool follows the same independently approved process.
An instruction file is not a working connection
In the 0.10.0 lab, selecting codex and claude created AGENTS.md and CLAUDE.md. Because no usage sources were selected, that result is not a real connection or conversation import. In your installation, choose a recognized source and inspect connection status, then compare an approved real source result with the displayed information.
Read and back up the repository’s existing instruction files. The tested adapter writer does not overwrite an existing file; do not resolve an existing-file error by deleting guidance without review. Reconcile the needed content with current instructions, then ask the tool to identify its active instruction sources. Each tool loads guidance differently; see the comparison below.