Run Claude Code in the background: tech debt, refactors, dependency upgrades

​A live workshop on running Claude Code as a background agent — dispatch work to a VM, stay in flow on the real work, monitor and approve from your phone.

​What you'll do

​In 60 minutes, you'll set up a workflow where two or three Claude Code threads run in the background while you stay focused on the work in front of you. By the end:

• ​Multiple Claude Code threads dispatched to a VM, each on a separate task

• ​Approval gates surfacing on your phone as the agents hit them — handled in two taps, no context switch

• ​One real PR (your pick: refactor, dependency bump, or tech debt cleanup) generated during the session

​Why this workshop

​Claude Code can run for 45+ minutes on a single turn. Most developers spend that time watching one terminal — one agent, full attention, deferred work stays deferred.

​Dispatch threads to the background instead. Your foreground work keeps moving. The deferred work runs in parallel.

​What we'll cover

• ​The background lane — which work belongs in parallel and which doesn't. Tech debt, refactors, dependency upgrades, test backfill, flake hunting, migrations.

• ​Dispatching threads to a VM — sending off Claude Code work to run remotely, organized so multiple threads run cleanly side by side

• ​Mobile control — approve and redirect from your phone without leaving the foreground task

• ​Live build — pick a real task from your own backlog, dispatch it during the workshop, walk away with the PR

• ​Q&A

​Calling speakers

​Running Claude Code in parallel and shipping more because of it? We're holding a 10-minute speaker slot for one or two developers to share their workflow — how you split work between foreground and background, what you dispatch, what stays at your desk, what you've learned.

​Let us know in the registration form.

​Speakers

​Anil Dukkipatty

​Most developers run one Claude Code agent at a time. Watch it. Wait for it. Then move on. Anil's going to show you what it looks like when you stop doing that — multiple threads running in the background, approval gates surfacing on your phone, real PRs shipping while you stay in flow on the work in front of you. He's built this into his daily workflow. Come see how.

​
Chinmay Relkar

​You know that list of tasks you keep pushing to next week? Deployment chores, ops tickets, the stuff that eats two hours before you've done any real work. Chinmay's going to show you how to make most of that disappear — using AI skills, plugins, and tools you can plug straight into your workflow. He'll also walk you through setting up your own ambient AI assistant, one that just runs in the background and handles the everyday friction without you having to think about it.

​Who this is for

​Developers who already use Claude Code and want a workflow that scales beyond one terminal at a time.

​What you'll need

• ​A laptop

• ​An iPhone

• ​A repo you don't mind your agent touching

​Early access

​Attendees get 10 free hours of Grass compute for the workshop. That's hundreds of Claude Code turns in parallel or sequence, enough to run multiple PRs end to end, with room to spare. Option to extend for active attendees afterwards.

​Grass is in early access; the workshop is a soft on-ramp for developers who want a real parallel-coding workflow before we open it up more broadly.

​Format

​60 minutes, live, online. Attendees follow along. Recording sent to registrants after.