Coworking patterns
Plan-then-build, asking for confirmation, code review loops.
How to work with Claude as a colleague rather than a vending machine: when to plan, when to ask, when to let it just go, and how to keep the loop tight.
All coworking patterns questions (5)
-
How do I get Claude to react to a Sentry alert while I sleep?
Channels are MCP servers that push events into your already-running Claude Code session — webhooks from CI or Sentry, DMs from your phone, anything that can speak HTTP. Here's the webhook-receiver pattern end to end, plus the sender-gating footgun that bites people.
-
How do I let Claude take notes about my project without writing CLAUDE.md myself?
Auto memory is the second persistence mechanism alongside CLAUDE.md — but you don't write it, Claude does. Here's how to find it, audit it, and decide which mechanism a given fact belongs in.
-
How do I make Claude open a PR every Monday morning?
Routines are saved Claude Code configurations that run on a schedule, on demand via HTTP, or in response to GitHub events — on Anthropic's cloud, not your laptop. This is everything you need to set one up and avoid the obvious footguns.
-
How do I make Claude plan before it edits code?
Use planning mode (or just ask) so Claude writes the plan, you approve it, and only then does it touch files.
-
Which Claude code review tool should I actually use?
Three reviewers ship inside Claude: a single-pass local /review, a cloud-sandbox multi-agent /ultrareview, and a GitHub App that runs on every PR. They cost different amounts, run in different places, and answer different questions. Here's the picking guide and the per-tool footguns.