All integrations

Windsurf

Same story as Cursor - Cascade learns Chirp from one file.

LiveEditorchirp login
progress (primary) Live Activity preview
Cascade session

Windsurf's Cascade agent reads `.windsurfrules` the same way Cursor reads `.cursorrules` - system context prepended on every turn. Chirp's rules file teaches Cascade when Chirp is the right tool and how to invoke it. Same upstream content as the Cursor file with a few Cascade-specific notes (Cascade is more proactive about running shell commands, so the rules nudge it toward `chirp run` over inline SDK use).

Prerequisites

  • Windsurf installed (Cascade is the agent inside Windsurf).
  • A Chirp account paired via `chirp login`.

Setup

  1. 1

    Pair the CLI

    chirp login - opens a browser, drops credentials at ~/.chirprc.

    shell
    chirp login
  2. 2

    Drop the rules file at the repo root

    Same one-liner as Cursor; different filename. Cascade reads .windsurfrules on session start.

    shell
    curl -o .windsurfrules https://chirpapp.dev/agent-skill/windsurfrules
  3. 3

    Use Cascade as normal

    Ask Cascade to wrap a long-running task with notifications. It will pick chirp run for shell commands, the Python/Node SDK for inline code, or the appropriate CI step if you're editing a workflow file.

What you’ll see

Same as Cursor - no card from the rules file itself; cards appear because Cascade wires Chirp into your scripts. The wiring varies based on what Cascade is editing.

Troubleshooting

Cascade ignores the rules file.
Restart Cascade after adding the file - like Cursor, rules are read on session start. Confirm .windsurfrules (no extension) is at the repo root.
Cascade wires `chirp run` but the binary isn't found.
The installer uses npm's global bin. Reopen your terminal, or run npm prefix -g and add that directory's bin folder to PATH.
Browse all integrations