This file is a map for AI agents working in remnote-cli.
Read these before making changes:
.agents/dev-requirements.md.agents/dev-workflow.md.agents/dev-documentation.md(required before docs edits).agents/dev-python-conventions.md(if touching Python helper scripts).agents/PLANS.md(required for complex work / major refactors)
This repo is the CLI companion app for the RemNote bridge plugin. It uses a daemon model:
CLI commands (short-lived) <-> HTTP control API (:3100) <-> daemon <-> WebSocket (:3002) <-> bridge plugin
JSON output is the default mode for automation consumers.
Resolve from this repo root ($(pwd)):
$(pwd)/../remnote-mcp-bridge- authoritative bridge actions + payload/response contracts$(pwd)/../remnote-mcp-server- sibling consumer with shared contract and compatibility logic
When bridge contracts change, validate all three repos.
- Daemon lifecycle:
daemon start,daemon stop,daemon status - Bridge commands:
create,search,search-tag,read,update,journal,status
- CLI bridge actions include
search_by_tagandget_status. - Bridge plugin sends WebSocket
hellowith plugin version. statusoutput may includecliVersionandversion_warning.- Projects are
0.x; prefer same minor line across bridge/server/CLI.- See
../remnote-mcp-bridge/docs/guides/bridge-consumer-version-compatibility.md.
- See
src/cli.ts- top-level command wiring and global optionssrc/commands/*.ts- command argument mapping and output handlingsrc/daemon/daemon-server.ts- daemon runtime compositionsrc/daemon/control-server.ts- control API (/health,/execute,/shutdown)src/websocket/websocket-server.ts- bridge WS server + request lifecyclesrc/client/daemon-client.ts- CLI-to-daemon HTTP clientsrc/version-compat.ts- compatibility warning logic
Primary docs for deeper context:
docs/architecture.mddocs/guides/command-reference.mddocs/guides/daemon-management.mddocs/guides/troubleshooting.md
If Node/npm is unavailable in shell:
source ./node-check.shCore commands:
npm run dev
npm run dev:watch
npm run build
npm run typecheck
npm test
npm run test:coverage
./code-quality.shAI agents must not run integration tests in this repo.
- Do not run
npm run test:integration. - Do not run
./run-integration-test.sh. - Ask the human collaborator to run integration tests and share logs.
- Use unit/static checks for agent-side verification.
- Before docs edits, read
.agents/dev-documentation.md. - Any functional or documentation change must be recorded in
CHANGELOG.md. - Keep AGENTS/docs map-level: contracts, rationale, and navigation.
- Publish workflow:
./publish-to-npm.sh - Keep release notes aligned with
CHANGELOG.md
Do not create commits unless explicitly requested. Use .agents/dev-workflow.md as canonical policy.