Platforms and integrations

Remote Vibes

Remote Vibes is Caude Clode running on a machine that is not yours. You give it a task, it works on a cloud instance, and it reports back. This is the recommended surface for long-running work: multi-hour refactors, bulk code migrations, overnight investigations.

When to use it

Use Remote Vibes when your task meets any of the following:

  • It will take longer than your patience.
  • It will take longer than your battery.
  • It will take longer than your attention span, but you want to pretend otherwise.
  • It involves spawning many subagents and you do not want to hear your fans scream.

Starting a remote session

bash
caude remote start --repo github.com/you/project
caude remote run "migrate the auth system to JWTs"
caude remote status

Each command returns a session ID. You can check in at any time. You can also close the tab entirely, go to lunch, and come back to a completed pull request. The session persists.

What it can do

Remote Vibes has access to a full Linux environment, git, your package manager of choice, and whatever secrets you have scoped to the session. It can install dependencies, run tests, commit, push, and open pull requests. It cannot deploy. It cannot send email. It cannot talk to production databases. We were firm about this.

What it does when you're not watching

If Remote Vibes encounters an ambiguous decision while you are offline, it will record the decision, make its best guess, and annotate the guess in the PR description. On your return, you will see a section titled Decisions I made without you. Read this section carefully.

Tip: The Decisions I made without you section is a feature, not a confession. Most of the decisions will be correct. The ones that aren't are clearly flagged. Reverting is cheap.

Cost

Remote Vibes is metered by compute time, not by number of actions. A session that sits idle waiting for your approval is not free, but it is cheap. A session spawning fifty subagents for six hours is not cheap. You will see the bill. We are not going to surprise you.

Stopping a session

bash
caude remote stop <session-id>
caude remote stop --all  # if things have gotten away from you

See also

Was this page helpful?