The Reddit threads asking "anyone using Claude Code for non-coding tasks?" are long because the answer is yes, with caveats nobody puts in the title. We use Claude Code every day. This is a straight account of what it does well outside the repo, where it stops, and what we run next to it. Facts checked against Anthropic's docs on 2026-09-21.
Disclosure: TODO for AI competes with Claude Code for part of the same budget. Where it beats us is stated. Our own case is confined to the last section.
What works
Claude Code is an agent with a shell, a file system and MCP, reachable from a terminal, an IDE, a desktop app and claude.ai/code. Anything that is a file, a command or an MCP server is fair game.
Email triage and drafts. With the Gmail MCP server wired, it reads the inbox, labels, drafts replies. For a founder inbox this is the single most useful non-code job it does.
Calendar prep. Google Calendar plus Slack plus Notion MCP: a "prep me for tomorrow" command that gathers context per meeting while you do something else.
Reports and documents. Anything that starts from files or an API. Weekly numbers from a CSV, a changelog from git log, a summary from meeting transcripts. This is its home turf and it is very good here.
Data chores. Renaming, reformatting, merging spreadsheets, deduping a contact list. Faster than writing the script yourself, because it writes the script.
The common thread: the data is reachable from a shell on the machine Claude Code is running on, or from an MCP server it has been given.
Where it breaks
Browser work needs you at the machine. Anthropic ships the Claude in Chrome extension, so Claude Code can open tabs and drive your logged-in session for the CMS admin, the ad account or the supplier portal. It works, and it pauses for you on logins and CAPTCHAs. But it needs a direct Anthropic plan and Chrome running next to the session, on your own machine. A cloud session runs on Anthropic's infrastructure and has no path to your local Chrome, so the browser half of your work is the half you have to be present for.
Unattended work is repo-anchored. This is the caveat that moved. Cloud sessions and routines do run on Anthropic's infrastructure while your machine is off, triggered by a schedule, an API call or a GitHub event, and they can call your MCP connectors, writes included. But a routine is configured around GitHub repositories and a cloud environment whose network is allow-listed by default, and it pushes to claude/-prefixed branches. Nightly PR review: excellent. Nightly "work the inbox and update the ad budgets": possible through connectors if every tool you need has one, impossible for anything that only exists behind a login.
MCP tax. Every SaaS tool without a CLI is a server to install, authenticate and keep working. Gmail, Calendar, Slack, Notion: four setups before the "chief of staff" demo works. Fine once; painful across a team.
One vendor. Claude only. When Claude is the wrong model for a job (cheap bulk classification, a second opinion on its own output), there is no switch.
Still developer-shaped. The desktop app and claude.ai/code removed the terminal requirement, but the surface is still repos, branches and diffs. The person on your team who would benefit most from email triage is not going to connect a GitHub repository to get it.
What we run next to it
TODO for AI is built around the gaps above and not around the strengths: Claude Code's terminal workflow is more mature than ours and its code output is excellent, and the numbers, including where we score higher and why that is not a like-for-like comparison, are on the comparison page. The setup that works for us: Claude Code stays open for the repo. Everything that touches an inbox, a browser or a schedule goes on the TODO list, where it runs on a persistent cloud VM or a paired machine, on whichever model fits, from the web or desktop app. Browser items still need Chrome open on your side; what that reaches is in the extension post.
Short version
| Task | Claude Code | TODO for AI |
|---|---|---|
| Fix the bug, open the PR | Excellent, most mature workflow | Yes, on your PC or its VM |
| Email triage via MCP | Yes, after setup | Yes, via your browser or MCP |
| Post to the CMS, run ads, update the CRM | With Claude in Chrome or an MCP connector, while you are there | With our Chrome extension or a CLI, while you are there |
| Unattended overnight | Yes: repo-anchored cloud session plus connectors | Yes, on a persistent VM; browser items wait for Chrome |
| Switch models per task | No | Yes |
| Non-developer can use it | Not really: repos, branches, diffs | Yes |
If your non-coding tasks are files, APIs and the occasional browser job while you sit there, Claude Code already does them. If the unattended half of your work is not a repository, or you want a second vendor's model reading the first one's output, that is what TODO for AI is for.
Top comments (0)