Anthropic's agent that works in your terminal, IDE, desktop app and browser. It reads and edits files, runs commands and connects to tools through MCP. People also use it for jobs far from code, such as bookkeeping, research and inbox work, because it can run scripts and keep notes in files.
Before your first meeting you have one short brief per external meeting, with sources for every claim about each guest.
You have a folder of interlinked markdown pages with an index and a change log, built from your sources, that you can read in Obsidian and query through the agent, with every change reviewable in git.
You get a local dashboard of spending by month and category that you can rebuild each month, with totals that match your statements.
You have a working workflow that has passed test runs, asks a person before it sends or changes anything important, and alerts you when a step fails.
Every Monday you get a draft report with this week's KPIs, the change from last week, a data check section and three lines of commentary, ready for one person to approve and send.
You get a clean file, a change log that explains every merge, and a short review sheet of possible duplicates for you to decide, with every original row accounted for.
You get a screening log, an evidence table with one row per included paper, a synthesis that cites only papers you hold, and a reference list where every entry resolves to a real record.
You get a draft issue with a short, sourced summary of each link you saved, grouped by theme, plus a list of links the agent could not read.
Each new lead gets a researched summary, a score, a route and a draft reply, and a person approves the action before anything changes in the CRM or reaches the lead.
You get a list of every recurring charge with its price and renewal date, and you cancel the ones you choose with a confirmation for each.
You get a table of buyer questions with your mention rate, competitors' mention rates and cited sources per assistant, plus a short content plan for the biggest gaps that you approve.
Your robots.txt allows the AI search crawlers you choose, keeps private paths blocked, and you have checked the live result.
Your accountant gets one tidy folder, a list of every form with its key figures and source, a list of missing documents, and your open questions.
You have a docs/architecture.md that names the entry points, modules and data flow with file references, a list of open questions, and a short instruction file with the build and test commands.
You get a workbook with every bank line matched to a receipt or marked missing, a proposed category for each, and a short list of VAT or sales tax questions for your accountant.
You get a table of researched accounts with a fit score, sources and one draft email each, and nothing is sent until you approve it.
You get a structured dossier covering the key data points for a specific property, with sources for each claim, ready to cross-check before you rely on it.
You get a report where every factual claim links to a source that loads and says what the report claims, plus a table of the claims you cut or changed.
Your folder is sorted into a small set of named subfolders, nothing is deleted, and you have a log of every move that you can reverse.
You get a spreadsheet with every ticket or answer labelled, a theme table with counts and example quotes, and an agreement check that shows how far to trust it.
You get a table of the console errors and failed requests on each route you named, a small fix for each one, and proof from a reload that the error is gone.
You buy the exact product you chose at or below your target price, and you pay for it yourself after checking the final total.
Each weekday you get one message with the few new papers and releases that match your interests, each with a link, a one-line reason it matters, and a clear note when nothing new appeared.
You get a short root cause note backed by the stack trace and code, a failing test that reproduces the error, a small fix that makes it pass, and a local branch ready for your review.
Each morning you get one brief with the emails that need you, draft replies waiting in your drafts folder, and a list of calendar problems to fix.
You get a blog draft, a list of clip candidates with start and end times, and a set of social posts, all checked against a timestamped transcript.
Every real commitment from the meeting is a task in your tracker with the right owner, a due date and a quote from the transcript, and nothing is invented or duplicated.
Each chosen issue gets a pull request with a passing test run that you review, ask to change, merge or close. You stay in control of every merge.
The repo runs on the new version on a branch of small commits, the full test suite passes with no tests removed, and you have a list of behaviour changes to check in staging.
Every week you get a short briefing of meaningful changes to competitors' pricing and product pages, each with the before text, the after text and a link to the saved snapshot.
You get 3-5 copy variants tied to a written hypothesis, one live A/B test with a fixed sample size, and a result you can trust or a clear "no difference".