Craft Docs를 위한 Local-first CLI: Quick reads from Craft Desktop’s cache when 적격, REST fallback, API-only writes.

Single-binary Bun CLI, AI-agent-first, macOS 및 Linux에서 실행합니다. 또한 Raycast 및 Node 스크립트에 대한 TypeScript 라이브러리를 수출합니다.

비공식. Craft Docs와 제휴하지 않습니다.

**Agent read policy: ** macOS에서 craft source auto를 유지하십시오. Unfiltered docs ls 및 간단한 docs search 는 기술의 로컬 캐시를 먼저 사용하고 REST로 다시 떨어졌다. --api]을 일상적으로 전달하지 마십시오. Markdown 문서는 캐시를 사용합니다. Structured/raw 읽기, 작업, 알림, 수집, 필터링 쿼리 및 모든 쓰기 사용 REST.

---

설치 (당신의 AI 대리인에 이것)

공예품을 설치하려면 AI 코딩 에이전트 (Claude Code, Codex, OpenCode, Cursor 등) 아래에 블록을 붙여 넣습니다. 에이전트는 clone, 빌드, 설치, 인증 및 기술 등록을 처리합니다.

---

인간을 위한

Craft Docs에 대한 현지 최초의 CLI. 주요 목표는 AI 코딩 에이전트 (Claude Code, Codex, OpenCode 등)에서 로컬 파일로 쉽게 읽고 편집 할 수있는 기술 콘텐츠를 만드는 것입니다 Obsidian 같은 도구.

craft-cli

Local-first CLI for Craft Docs: fast reads from Craft Desktop’s cache when eligible, REST fallback, and API-only writes.

Single-binary Bun CLI, AI-agent-first, runs on macOS and Linux. Also exports a TypeScript library for Raycast and Node scripts.

Unofficial. Not affiliated with Craft Docs.

Agent read policy: On macOS, keep craft source auto. Unfiltered docs ls and simple docs search use Craft’s local cache first and fall back to REST automatically. Do not pass --api routinely. Markdown document reads also use the cache. Structured/raw reads, tasks, reminders, collections, filtered queries, and every write use REST.

---

Install (paste this to your AI agent)

To install craft-cli, paste the block below into your AI coding agent (Claude Code, Codex, OpenCode, Cursor, etc.). The agent will handle clone, build, install, authentication, and skill registration.

You are installing craft-cli (https://github.com/pa1ar/craft-cli) for me. Use the latest public stable release and its matching bundled skill. Proceed end-to-end; ask only when a required choice or credential is missing.

1. RUNTIME CHECK
   Check whether `bun` is on PATH. If yes, continue.
   If not, use my stated package-manager preference, or install Bun from https://bun.sh. This project builds with Bun.

2. RELEASE + BUILD + INSTALL
   Resolve the latest public stable release:
   CRAFT_RELEASE_TAG="$(bun -e 'const r = await fetch("https://api.github.com/repos/pa1ar/craft-cli/releases/latest"); if (!r.ok) throw new Error("GitHub release lookup failed: " + r.status); const release = await r.json(); if (!release.tag_name || release.draft || release.prerelease) throw new Error("No stable release"); console.log(release.tag_name)')"
   Stop if that lookup fails. Do not silently install main or a local development binary.
   CRAFT_RELEASE_DIR="$HOME/.local/share/craft-cli/releases/$CRAFT_RELEASE_TAG"
   If the release directory already exists, preserve it. Verify its origin, tag commit and tracked source state before reuse; use a fresh directory if it has local edits.
   git clone --branch "$CRAFT_RELEASE_TAG" --depth 1 https://github.com/pa1ar/craft-cli.git "$CRAFT_RELEASE_DIR"
   cd "$CRAFT_RELEASE_DIR"
   Read this release's install.sh, then run ./install.sh.
   If install.sh fails, diagnose and report the failure before using its documented manual build/link equivalent. Keep the same release tag.
   Verify `~/.local/bin` is on PATH and `command -v craft` resolves to this release's binary. Add the PATH entry to my shell rc only if missing (detect zsh vs bash). Use `craft` from PATH for normal work.
   Record the release tag and `git rev-parse HEAD`; version alone does not prove a build came from a release.

3. CONNECTION