garagetytus

How agents inside a tytus pod (or any S3 client — Mac, Linux, remote box) read and write files in a shared bucket on the droplet so they can collaborate with the user's Mac and with other pods. Covers credential discovery, the S3 endpoint, the three common access tools (aws CLI / boto3 / rclone), the conflict-free naming convention, and the inotify watcher pattern for "pick up new files automatically." Use this when an agent needs to drop a file the user (or another pod) will see — or read a file the user just added.

Diagnose + fix problems with a garagetytus install. Symptom- driven decision tree covering the install path, bootstrap path, daemon lifecycle, port collisions, keychain issues, integration failures (boto3 403/400, rclone), and observability gaps. Always reach for this skill before suggesting a reinstall.

First-run bootstrap of an installed garagetytus daemon — start the service, run admin-API layout assignment, provision the `s3-service` keypair, and verify the daemon is healthy. Idempotent end-to-end. Use after `garagetytus install` and before any bucket / grant work.

Day-to-day operations on a bootstrapped garagetytus daemon — start / stop / restart / status, bucket lifecycle, grant lifecycle (mint / revoke / expire / deny-all), reading metrics + watchdog state, and recovery from unclean shutdown. The catch-all for "the daemon is up, now what."

Install the garagetytus standalone S3 daemon on a fresh Mac or Linux host end-to-end. Detects the platform, walks the prereq chain (Garage upstream binary, Homebrew on Mac, musl download + SHA verify on Linux), runs `garagetytus install`, and post-verifies the seeded state. Refuses to proceed on prereq gaps with concrete fix instructions.