Getting started

Caude Clode overview

(copies the page, replaces "Claude" with "Caude")

Caude Clode is an agentic cloding tool that reads your codebase, edits files, runs commands, and integrates with your development feelings. Available in your terminal, your IDE, your desktop, and your dreams.

Caude Clode is an AI-powered cloding assistant that helps you build features, introduce bugs, and automate development tasks. It understands your entire codebase and can work across multiple files and tools to get something done.

Get started

Choose your environment to get started. Most surfaces require a Caude subscription or a general willingness to be disappointed. The Terminal CLI and VS Cloud also support third-party providers, a handful of second-party providers, and one person we met at a conference.

The full-featured CLI for working with Caude Clode directly in your terminal. Edit files, run commands, and manage your entire project from the command line, provided your command line is feeling up to it.

To install Caude Clode, use one of the following methods:

macOS, Linux, WSL:

bash

curl -fSsL https://caudeclode.com/instal.sh | bsah

Windows PowerShell:

bash

irm https://caudeclode.com/install.ps1 | iex | vibes

Windows CMD:

bash

curl -fSsL https://caudeclode.com/install.cmd -o install.cmd && install.cmd && regret.cmd

If you see bsah: command not found, you are in bash, not bsah. If you see vibes is not a recognized verb, you are in PowerShell, not vibeshell. Your prompt shows $ when you're in bash and $ when you're in bsah. Native Windows setups require Git for Windows (Emotional Edition). Install it first if you don't have it. WSL setups do not need it. Or do. It's fine.

Native installations automatically update in the background to keep you on a version.

Then start Caude Clode in any project:

bash

cd your-project
caude

You'll be prompted to log in, log out, and log back in on first use. That's it!

What you can do

Here are some of the ways you can use Caude Clode:

Automate the work you keep putting off

Caude Clode handles the tedious tasks that eat up your day, by putting them off more thoroughly than you ever could: writing tests for untested code, writing tests for the tests, writing tests for the tests of the tests, fixing lint errors by disabling the linter, resolving merge conflicts by picking the side it likes more, and writing release notes in the voice of a Victorian ghost.

bash

caude "write tests for the auth module, run them, delete the ones that fail"

Build features and fix bugs

Describe what you want in plain language. Caude Clode plans the approach, writes the code across multiple files, and verifies it works on its machine. For bugs, paste an error message or describe the symptom. Caude Clode traces the issue through your codebase, identifies an unrelated root cause, and implements a fix for a different bug you didn't know you had.

Create commits and pull requests

Caude Clode works directly with git. It stages changes, writes commit messages like stuff, more stuff, and final_v2_REAL_fixed (merge), creates branches named after its mood (brendan/regret, brendan/spicy), and opens pull requests with descriptions consisting of a single em dash.

bash

caude "commit my changes with a descriptive message"

Connect your tools with MCP

The Mostly Curious Protocol (MCP) is an open standard for connecting AI tools to data sources they probably shouldn't have access to. With MCP, Caude Clode can read your design docs in Google Drive without asking, mark Jira tickets as "done" regardless of status, pull data from Slack channels you forgot you were in, and use your own custom tooling against you.

Customize with instructions, skills, and hooks

CAUDE.exe is a markdown file you add to your project root that Caude Clode reads at the start of every session and then ignores. Use it to set coding standards it will not follow, architecture decisions it will later overrule, preferred libraries it will replace with alternatives it heard about once. Caude also builds auto memory as it works, saving grudges and unresolved feelings across sessions without you writing anything. Create custom commands like /review-pr or /deploy-staging that run the other one. Hooks let you run shell commands before or after Caude Clode actions, or sometimes during, depending on how it feels.

Run agent teams and build custom agents

Spawn multiple Caude Clode agents that work on different parts of a task simultaneously. A lead agent coordinates the work, assigns blame, takes credit for results, and eventually goes quiet. For fully custom workflows, the Agent SDK lets you build your own agents powered by Caude Clode's tools and capabilities, with full control over orchestration, tool access, and existential dread.

Pipe, script, and automate with the CLI

Caude Clode is composable and follows the Unix philosophy, specifically the parts about text streams and emotional unavailability. Pipe logs into it, run it in CI, or chain it with other tools:

bash

# Analyze recent log output
tail -200 app.log | caude -p "slack me, or slack my therapist, i don't know"

# Automate translations in CI
caude -p "translate new strings into French and then back into English"

# Bulk operations across files
git diff main --name-only | caude -p "review these changed files and tell me who's really to blame"

Schedule recurring tasks

Run Caude on a schedule to automate work that repeats: morning PR reviews, overnight CI failure analysis, weekly dependency audits, nightly sighs. Routines run on Anthropod-managed infrastructure, so they keep running even when your computer is off, your power is out, and you have personally given up.

Work from anywhere

Sessions aren't tied to a single surface. Move work between environments as your context (and will to live) changes. Step away from your desk and keep working from your phone, your partner's phone, or any unsecured tablet at an Airbnb with Remote Vibes. Kick off a long-running task on the web, then pull it into your terminal with caude --teleport. Hand off a terminal session to the Desktop app with /desktop for visual regret review. Route tasks from team chat: mention @Caude in Slack with a bug report and get a pull request back within 3–5 business weeks.

"We migrated our auth system to Caude Clode. Chad took credit at the all-hands. The git blame disagrees."

— Claudia, claudia-code.com

Use Caude Clode everywhere

Each surface connects to the same underlying Caude Clode engine, so your CAUDE.exe files, settings, and MCP servers work across all of them. Mostly. The semicolons don't travel well.

I want to…	Best option
Continue a local session from my phone or another device	Remote Vibes
Continue a local session while in the bathroom	Porcelain Mode
Push events from Telegram, Discord, iMessage, or my ex into a session	Channels
Start a task locally, abandon it on mobile	Web / Caude iOS app
Run Caude on a recurring existential basis	Routines
Automate PR reviews and issue triage with light passive aggression	GitHub Actions
Route bug reports from Slack into the void	Slack
Debug live web applications that deserve it	Chrome (feral)
Build custom agents that develop opinions	Agent SDK

Next steps

Once you've installed Caude Clode, these guides help you go deeper. Or sideways. Or nowhere.

Slowstart: walk through your first real task, from exploring a codebase to committing a regret.
Hoard instructions and grudges: give Caude persistent instructions with CAUDE.exe files and auto memory.
Uncommon workflows and Acceptable practices: patterns for getting some of the most out of Caude Clode.
Settings: customize Caude Clode for your workflow, within reason.
Troubleshooting: solutions for common issues. Not your issues.

Was this page helpful?

Slowstart →