Agent Local Cloud Sync — DevOps skill for Claude Code
Push-to-deploy for agent builders and vibe coders.
How to install Agent Local Cloud Sync
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open cobibean/agent-local-cloud-sync and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Agent Local Cloud Sync does
Push-to-deploy for agent builders and vibe coders. Auto-pull your repo on a single cloud host when you git push. Python 3 stdlib + systemd + HMAC. Claude Code skill.
Alternatives in DevOps
- Ship Release — Systematic release workflow for RTK: build verification, version bump, changelog update, git tag, and push to 11.9k ★
- Open Agent Email — Open-source email infrastructure for AI agents: secure inboxes, REST and MCP APIs, SMTP, human approval workfl 2.1k ★
- Coi — Give the agent a machine 743 ★
README
Agent Local ↔ Cloud Sync
A tiny push-to-deploy system for agent builders and vibe coders running one thing on one cloud host.
You build the agent on your laptop. It runs on a droplet. You want `git push` to be the whole deploy — no CI runner, no ngrok, no `pip install`, no DevOps afternoon. This repo is the ~100 lines of Python and one systemd unit that does exactly that.
Framework and skill authored by Jacobi Lange — [@cobi_bean](https://x.com/cobi_bean) on X, [@cobibean](https://github.com/cobibean) on GitHub.
What this is
A public, generalized version of the sync pipeline I built for a personal Hermes agent running on a DigitalOcean droplet. Every gotcha in `SKILL.md` actually happened during that deploy.
The flow is dead simple:
- You
git pushfrom your laptop. - GitHub fires a webhook at your droplet.
- The droplet fast-forwards the repo.
- Your agent reads the new files on its next turn.
No build step. No platform. No lock-in. Just a webhook, a `git pull`, and HMAC to keep randos out.
Open `SKILL.md` for the full runbook.
Who it is for
- Agent builders running a Hermes / Claude Code / custom agent on a VPS
- Vibe coders who want the laptop-to-cloud loop to feel like one repo
- Solo devs running a bot, scheduler, or scraper on a single host
- Anyone tired of
ssh host 'cd repo && git pull'after every change
What it isn't
- A build system — if your deploy needs compile/bundle/migrate steps, add a post-pull hook or use CI
- A multi-host deployer — this is one-host by design
- TLS out of the box — payloads are plain HTTP. HMAC protects integrity, not confidentiality. Put it behind Caddy if you need more.
Install in Claude Code
# User-level (available in every project)
git clone https://github.com/cobibean/agent-local-cloud-sync.git ~/.claude/skills/agent-local-cloud-sync
# Or project-level (available only in this repo)
git clone https://github.com/cobibean/agent-local-cloud-sync.git .claude/skills/agent-loc
Related Skills
Infer Lite
Minimum viable free-LLM gateway — stdlib-only Python, no Docker, no LiteLLM. Single file, ~1000 LOC. Sibling t
Multi Target Publish
When a single change spans multiple repos / packages / deploy targets with different deploy mechanisms (auto-d
Local
Build and verify a result only on this machine, with no push, pull request, deploy, or production access.
Remote Vibe Station
Remote Vibe Station is a server-first AI coding workspace. Instead of running OpenCode on your laptop, you put
AI Dev Team
Token-efficient multi-agent dev team for Claude Code: planner, parallel builders, devops, code reviewer, teste
Engram MCP
🧠 Zero-dependency MCP server for persistent AI agent memory. Pure Python stdlib. No cloud. No Docker. No API
Related Agents
Vibe Coder
Fullstack vibe coding assistant. Talk naturally — I plan, code, test, and deploy for you. Perfect for non-tech
Gagarin CI
Wires a repository's CI pipeline to deploy to Gagarin Cloud on push — mints a scoped deploy credential, stores
Wiki Sync
Use this agent when syncing the vault git repository during automated maintenance cycles. Typical triggers inc