Files and skills

~/.local/share/garcon/usage.jsonl

This machine's log, one JSON object per completion call. Append-only; the format never changes with sync.

~/.local/share/garcon/remote.jsonl

Cache of other machines' rows pulled by sync. Safe to delete.

~/.local/share/garcon/sync.json

This machine's device id and the push and pull cursors. Keep it through upgrades. Do not copy it or the data directory to another machine: each machine must have its own identity.

~/.config/garcon/config.json

The sync switch, device name, project URL and secret key. Owner-only (0600); the API does not return the key.

~/.local/share/garcon/bin/garcon

The private service executable, copied from the installed package by setup or service restart. It survives npm cache cleanup and Node version changes.

~/.config/systemd/user/garcon.service

Linux autostart service. Inspect it with garcon service status; logs are available with journalctl --user -u garcon.

~/Library/LaunchAgents/dev.garcon.plist

macOS autostart service. Its log is ~/Library/Logs/garcon.log.

garcon setup and garcon update preserve usage, settings and device identity. garcon service uninstall stops autostart and keeps usage and settings; npm uninstall -g ai-garcon removes the npm command. The source installer’s --uninstall also removes the settings file. See uninstall instructions before removing the proxy.

Agent skills

The repository ships skills in .claude/skills/ so a coding agent can do all of the above: install-garcon (install, set up, remove), update-garcon (update an npm installation with garcon update, or pull and rebuild a source checkout), add-provider (point any harness at any provider), and connect-supabase (a guided walkthrough of the sync setup on the first and every further machine, including naming each machine, explicitly creating or reusing a project, and joining subsequent machines without applying SQL again).

Design notes for the dashboard navigation are in ui-navigation.md.