A catalogue of real automations. Every one names the tools to connect, the wiring in order, and the one thing it has to remember between runs.
Free. No signup, no email gate, nothing to buy. Written and run by the team at Relote.
Three parts. Two of them you can buy. The third is the one that decides whether the thing is still useful in a month.
Each stack names the exact tools, and whether each one is reachable over MCP, an API key, or a command line. No "connect your stack" hand waving.
Who runs it, on what cadence, and the steps in order. A Claude Code run, a desktop MCP client, or a headless turn on a schedule.
The part everyone skips. Without it the thirtieth run is identical to the first, not better than it.
Open any one for the tools, the wiring, the human checkpoint and what it has to remember. Copy it as a prompt and hand it straight to your agent.
Crawls the site, finds unlinked mentions of your target pages and drafts insertions with anchor text.
Baselines clicks per site section, flags genuine breaks and tells seasonality apart from a problem.
Audits which templates emit valid schema and writes the missing JSON-LD from real page content.
Finds queries where two of your URLs split impressions and proposes one fix per cluster.
Builds a page per cluster from a real data source and your template, then stages it for review.
Audits hours, categories and photos across locations, then drafts replies to new reviews.
Watches competitor sitemaps daily, summarises each new page and says whether it targets your queries.
Builds a topic map from your URLs and the SERP, then shows where coverage is thin against rivals.
Reads the search terms report, proposes negatives and promotes only the terms that convert.
Spots decaying pages in Search Console, reads what now outranks them and drafts the refresh.
Qualifies each prospect domain, finds the right contact and drafts a pitch tied to a real content gap.
Finds videos with impressions and a weak click rate, then rewrites title, description and chapters.
Checks tracked keywords daily, separates real movement from SERP noise and names the likely cause.
Mines store keyword data and user reviews, then drafts the keyword field, title and captions.
Reads a crawl export, groups errors by cause rather than by URL, and files one ticket per fix.
Compares your keyword footprint against three competitors and ranks each gap by realistic reach.
Reads the pages ranking for a query and produces an outline, entities, questions and internal links.
It pulls usage, tickets, spend and open commitments into a draft review pack per account.
It researches a target account, then drafts an opening angle grounded in something verifiable.
It watches usage drops, support tone and champion departures, then raises one alert per account.
It tracks each onboarding plan and drafts the nudge for whichever step is actually blocking.
It assembles scope, pricing notes and proof points into a proposal draft the owner then edits.
It reads each NPS comment and public review, then drafts a specific reply for the owner to send.
It matches each question to your approved answer library and marks the ones nobody has answered.
It answers from documented articles only, cites them, and leaves the reply unsent for review.
It scans the pipeline weekly for deals with no real movement and drafts a specific next step.
It scores every upcoming renewal against support load, billing history and account history.
It reads tomorrow's calendar and assembles a one page brief for each external meeting.
It turns a support thread into a reproducible issue with impact, steps and affected accounts.
It matches inbound referrals to the partner who sent them and chases the ones with no update.
It enriches each new form fill with company facts and a suggested owner before the first reply.
It classifies each new ticket, sets priority and routes it, leaving the reply to a human.
It reads the calls behind every closed deal and reports why you won and why you lost.
It reads the transcript, proposes field changes and drafts the follow up email for review.
It builds a dispute response from the order, delivery and support record, then waits for approval.
It collects the documents on your accountant's request list and reports what is still missing.
It lists every recurring software charge, its owner, its renewal date and whether anyone uses it.
It codes new bank lines in Xero using the rules a bookkeeper corrected, and queues what it cannot.
It drafts the next chase for each overdue invoice, matched to what that customer last said.
It ties subscription billing to revenue in the ledger and lists every difference with a cause.
It tracks each contractor's documents, tax forms and signatures, and holds payment until they exist.
It translates each entity, eliminates intercompany balances and shows how each group line was built.
It scores outgoing payments against your own history and flags only what a human has not cleared.
It matches bank lines to ledger entries, then writes a short explanation for each unreconciled break.
It measures net burn from actual bank movement and states the runway with its assumptions shown.
It tests each card transaction and receipt against your policy, then asks only the useful questions.
It compares this payroll run to the last approved one and explains every change, line by line.
It reads each purchase request, applies your approval thresholds and routes it to the right person.
It works the close list in order, verifies each task against the ledger, and chases whoever is late.
It reads invoices out of the AP inbox, extracts the fields, and matches them to the purchase order.
It explains each material variance by tracing it to the transactions underneath before writing.
It groups open upgrade PRs into safe batches, runs the suite and writes a risk note for each.
It reads a design file, lists the states and edge cases, and drafts one ticket per buildable slice.
It pulls alerts, deploy events and Slack messages into one minute by minute timeline draft.
It turns a long PR or design thread into a decision record draft with the options really considered.
It tracks every action item from past incidents and nudges the owner with the incident behind it.
It reads the merged PRs between two tags and drafts notes split by audience, user facing first.
It reads recent CI runs, ranks tests by flake rate and drafts issues for the worst offenders.
It reviews open PRs against your own conventions and posts one comment the author can act on.
It clusters stale and near identical tickets, proposes merges and drafts the detail they are missing.
It counts what is really migrated in the code and the database, then updates the tracker weekly.
It diffs your route handlers against the published reference and opens a pull request per drift.
It compares monthly spend by service, explains the biggest movers and proposes what to cut.
It reads incoming feedback, matches it to an existing roadmap bet and flags the genuinely new asks.
It compares latency and error rates across releases and drafts a regression report with suspects.
It checks each new advisory against your real dependency graph and drafts only the reachable ones.
It reads new Sentry crash groups, dedupes them against open issues and drafts the ones worth filing.
It summarises the shift: what paged, what is still open, and what the next on-call should watch.
Logs brand mentions across social and news, then reports only the themes that changed today.
Reads mentions and relevant threads on X, then drafts replies only where a reply is warranted.
Fills next month's slots from existing assets and names the gaps nothing can cover.
Researches creators in your niche and shortlists them on audience fit, not follower counts.
Gathers the week's posts, releases and saved links into a complete draft issue for the editor.
Diffs competitor changelogs, pricing and announcements weekly, separating real launches from noise.
Writes platform-specific ad copy and creative briefs from the angles that already performed.
Sorts incoming comments into reply, hide, escalate or ignore, citing the rule that applied.
Drafts community replies using only published documentation, each with the citation attached.
Tracks events in your field, flags closing CFPs and drafts a proposal for each worthwhile fit.
Finds posts showing your product, logs each one and drafts a permission request for the author.
Drafts founder posts from their own notes and shipped work, checked against a written voice sheet.
Splits one article or talk into drafts sized for LinkedIn, X, Instagram and the newsletter.
Mines Reddit and forums for the questions buyers actually ask, then briefs the unanswered ones.
Produces show notes, timestamps and ranked clip candidates as soon as an episode finishes.
Drafts three follow-up emails: full attendees, early leavers and registrants who never showed.
Turns an outline into a shootable script, then times chapters from the rough cut transcript.
It answers questions in Slack from the warehouse and shows the query, so the answer can be checked.
It collects the exports and approvals each control needs and files them against that control.
It extracts who promised what by when from meeting notes, then follows each one until it closes.
It extracts the clauses that matter and flags only the ones that differ from what legal already agreed.
It watches table freshness and row volume, and raises only the gaps nobody has already accepted.
It reads each application against the scorecard and writes a reasoned recommendation for a recruiter.
It merges every interviewer's notes into one view, surfaces disagreement and lists what is still unknown.
It classifies inbound agreements, checks them against your standard form and routes them with a note.
It runs the joiner checklist across payroll, calendar and docs, then chases the steps that stall.
It assembles revenue, delivery and hiring into one brief and marks what changed since last week.
It works out what happened to an order across store and payments, then drafts the resolution.
It answers policy questions in Slack with the clause it came from and the date that clause changed.
It tracks every vendor renewal date and seat count, and flags the licences nobody has opened.
It finds pages that contradict current reality, ranks them by readership and drafts the correction.
It projects cover days per SKU, watches supplier lead times and raises the reorders worth raising.
It compares this week's metrics to last, finds the drivers, and writes the note your dashboard lacks.
Read the "what it must remember" line on any stack above, then read another. The tools change, the area changes, the failure does not.
It chases the same invoice twice and files an issue that already exists, because run two cannot see run one.
This week the metric is defined one way, last week another, and both notes sit on the same page.
It asks a customer for credentials they sent a fortnight ago, and your credibility pays for it.
Context Engine captures what happens across the tools your team already uses, turns it into living context, and serves it to any agent over MCP. Every stack on this page can read and write the same record.
That is the difference between an agent that produces the same draft every Monday and one that picks up where it left off.
We wrote every stack on this page and we run them. If you would rather the wiring, the guardrails and the memory layer were somebody's job, that is the job.
An hour on your actual systems. You leave with a shortlist from this page and an order to build them in.
Start with a starter-effort stack in the area that annoys you most, then give it somewhere to remember what it did.
Crawls the site, finds unlinked mentions of your target pages and drafts insertions with anchor text.
What you connect
How you wire it
What it must remember
It remembers every link it has already inserted, the anchor text used, and which pages a human told it to leave alone. Without that, it re-suggests the same insertions and stacks three identical anchors into one paragraph.
Baselines clicks per site section, flags genuine breaks and tells seasonality apart from a problem.
What you connect
How you wire it
What it must remember
It remembers each section's baseline, the known seasonal dips, and every anomaly a human has already explained. Without that, it pages the team about Christmas week again and re-asks a question that was answered last year.
Audits which templates emit valid schema and writes the missing JSON-LD from real page content.
What you connect
How you wire it
What it must remember
It remembers which templates it already covered, the schema type agreed for each, and the fields your CMS can genuinely populate. Without that, it proposes a type you rejected last time and invents fields no template can fill.
Finds queries where two of your URLs split impressions and proposes one fix per cluster.
What you connect
How you wire it
What it must remember
It remembers the call made on each query cluster, the redirect target proposed, and the date it was agreed. Without that, it recommends merging two pages it told you to differentiate last quarter and contradicts its own earlier decision.
Builds a page per cluster from a real data source and your template, then stages it for review.
What you connect
How you wire it
What it must remember
It remembers which clusters already have a page, the template version used, and the copy blocks an editor changed by hand. Without that, it regenerates a page someone rewrote and the manual improvements disappear on the next run.
Audits hours, categories and photos across locations, then drafts replies to new reviews.
What you connect
How you wire it
What it must remember
It remembers which locations are already corrected, which reviews it has replied to, and each branch's approved tone. Without that, it answers the same review twice and reverts a setting a franchisee deliberately changed.
Watches competitor sitemaps daily, summarises each new page and says whether it targets your queries.
What you connect
How you wire it
What it must remember
It remembers every competitor URL it has already reported and the angle it assigned to each. Without that, the daily digest repeats last week's pages and nobody can tell what is actually new.
Builds a topic map from your URLs and the SERP, then shows where coverage is thin against rivals.
What you connect
How you wire it
What it must remember
It remembers the taxonomy you agreed, which nodes are deliberately out of scope, and what every URL is mapped to. Without that, the taxonomy is rebuilt from scratch each month and a six month coverage programme loses its thread.
Reads the search terms report, proposes negatives and promotes only the terms that convert.
What you connect
How you wire it
What it must remember
It remembers every term already added as a negative, at which level, and every term it promoted to its own ad group. Without that, it proposes the same negatives week after week and can block a term it promoted two runs earlier.
Spots decaying pages in Search Console, reads what now outranks them and drafts the refresh.
What you connect
How you wire it
What it must remember
It remembers which URLs it already refreshed, the date, and exactly what it changed on each one. Without that, it re-queues a page it rewrote six weeks ago and you never learn whether the previous refresh worked.
Qualifies each prospect domain, finds the right contact and drafts a pitch tied to a real content gap.
What you connect
How you wire it
What it must remember
It remembers every domain already contacted, who replied, the angle used, and the campaign it belonged to. Without that, it pitches a site that declined in March and burns the one relationship you had there.
Finds videos with impressions and a weak click rate, then rewrites title, description and chapters.
What you connect
How you wire it
What it must remember
It remembers the previous title of every video it touched, the date changed, and the click rate before and after. Without that, it cannot tell a winning rewrite from a losing one and will eventually undo its own best change.
Checks tracked keywords daily, separates real movement from SERP noise and names the likely cause.
What you connect
How you wire it
What it must remember
It remembers each keyword's rolling position band, which competitors hold the page, and which alerts a human has already acknowledged. Without that, it treats ordinary fluctuation as news and the channel is muted within a fortnight.
Mines store keyword data and user reviews, then drafts the keyword field, title and captions.
What you connect
How you wire it
What it must remember
It remembers each locale's live listing text, the keyword field last submitted, and whether review passed or rejected it. Without that, it resubmits a phrase that already failed review and you lose another release cycle.
Reads a crawl export, groups errors by cause rather than by URL, and files one ticket per fix.
What you connect
How you wire it
What it must remember
It remembers which issue clusters are already ticketed, which were closed as won't fix, and the fingerprint of each cluster. Without that, it files a duplicate ticket for the same 40,000 faceted URLs every week and engineering stops reading the queue.
Compares your keyword footprint against three competitors and ranks each gap by realistic reach.
What you connect
How you wire it
What it must remember
It remembers every gap it has already scored, which ones a human rejected, and the stated reason for each rejection. Without that, it resurfaces the same dismissed keywords week after week and the digest stops being opened.
Reads the pages ranking for a query and produces an outline, entities, questions and internal links.
What you connect
How you wire it
What it must remember
It remembers the house brief format, which sections editors keep and which they cut, and the sources they have rejected. Without that, every brief drifts back to a generic outline and an editor restructures the same document by hand each time.
It pulls usage, tickets, spend and open commitments into a draft review pack per account.
What you connect
How you wire it
What it must remember
It must remember the goals each account stated in the previous review and the actions your side committed to. Without it, the pack shows fresh numbers against no baseline and the customer repeats the same request for a third quarter.
It researches a target account, then drafts an opening angle grounded in something verifiable.
What you connect
How you wire it
What it must remember
It must remember which accounts each rep has already contacted, on what date, and what the response was. Without it, two reps email the same prospect in the same week and the account decides you are disorganised.
It watches usage drops, support tone and champion departures, then raises one alert per account.
What you connect
How you wire it
What it must remember
It must remember each account's normal usage rhythm and the name of the person who actually champions you inside it. Without it, a seasonal dip reads as churn and a champion leaving goes unnoticed until the renewal call.
It tracks each onboarding plan and drafts the nudge for whichever step is actually blocking.
What you connect
How you wire it
What it must remember
It must remember what has already been requested from this customer, when, and what they supplied. Without it, the agent asks for the same access credentials a third time while the real blocker sits on your side.
It assembles scope, pricing notes and proof points into a proposal draft the owner then edits.
What you connect
How you wire it
What it must remember
It must remember every discount, deadline and scope promise already given to this account and by whom. Without it, the proposal contradicts what a colleague committed to on a call and the buyer stops trusting the price.
It reads each NPS comment and public review, then drafts a specific reply for the owner to send.
What you connect
How you wire it
What it must remember
It must remember every previous complaint from this customer and which of them you actually fixed. Without it, you thank a five year customer for trying the product, or apologise again for something resolved months ago.
It matches each question to your approved answer library and marks the ones nobody has answered.
What you connect
How you wire it
What it must remember
It must remember which answers are approved, who approved them, and when each was last reviewed. Without it, an outdated security claim is copied into a new bid and you commit to something that is no longer true.
It answers from documented articles only, cites them, and leaves the reply unsent for review.
What you connect
How you wire it
What it must remember
It must remember what this customer was already told, in which thread, and which of those answers turned out to be wrong. Without it, the draft repeats an answer that already failed and asks them to try the same fix twice.
It scans the pipeline weekly for deals with no real movement and drafts a specific next step.
What you connect
How you wire it
What it must remember
It must remember the reason each deal went quiet and which nudge was already tried on it. Without it, the same buyer receives the same checking in message for the third time and stops replying at all.
It scores every upcoming renewal against support load, billing history and account history.
What you connect
How you wire it
What it must remember
It must remember each account's renewal history: what was negotiated, what was complained about, and what was promised to keep them. Without it, the same concession is offered twice and a solved problem is raised again as though it were still open.
It reads tomorrow's calendar and assembles a one page brief for each external meeting.
What you connect
How you wire it
What it must remember
It must remember every objection each attendee has raised and every commitment your side made in reply. Without it, a rep re-pitches something the buyer already rejected and loses the room in two minutes.
It turns a support thread into a reproducible issue with impact, steps and affected accounts.
What you connect
How you wire it
What it must remember
It must remember the previous escalations from this account, what engineering concluded, and what the customer was told afterwards. Without it, the same issue is filed twice and the customer hears a different explanation each time.
It matches inbound referrals to the partner who sent them and chases the ones with no update.
What you connect
How you wire it
What it must remember
It must remember the commercial terms agreed with each partner and every referral already credited to them. Without it, one deal is credited twice or a partner's introduction is logged as a cold inbound lead.
It enriches each new form fill with company facts and a suggested owner before the first reply.
What you connect
How you wire it
What it must remember
It must remember every prior deal, trial and support conversation tied to that email domain, and which rep owned each one. Without it, a returning customer is greeted as a brand new lead and routed to someone who has never spoken to them.
It classifies each new ticket, sets priority and routes it, leaving the reply to a human.
What you connect
How you wire it
What it must remember
It must remember which known issues each customer has already been told about and what fix date they were given. Without it, the customer is asked to describe the same bug again and the ticket restarts from zero.
It reads the calls behind every closed deal and reports why you won and why you lost.
What you connect
How you wire it
What it must remember
It must remember the objection patterns and competitor mentions already catalogued in earlier months. Without it, every report restates the same five findings and nobody can see which loss reason is actually growing.
It reads the transcript, proposes field changes and drafts the follow up email for review.
What you connect
How you wire it
What it must remember
It must remember every commitment made on a call: dates, discounts, scope and the person who promised it. Without it, the next follow up quietly drops something the customer was told they would get, and they notice.
It builds a dispute response from the order, delivery and support record, then waits for approval.
What you connect
How you wire it
What it must remember
It remembers which arguments and evidence types won or lost past disputes, broken down by reason code and card network. Without it, it keeps submitting the template that loses and you learn nothing from a year of chargebacks.
It collects the documents on your accountant's request list and reports what is still missing.
What you connect
How you wire it
What it must remember
It remembers which documents are already filed, the exact version and period of each, and who owes the rest. Without it, it re-requests statements you sent in March and the folder fills with near duplicates nobody can reconcile.
It lists every recurring software charge, its owner, its renewal date and whether anyone uses it.
What you connect
How you wire it
What it must remember
It remembers which vendors were already reviewed, which an owner decided to keep and why, and which were cancelled. Without it, it reopens a tool the team deliberately kept and loses the audit trail showing the cancellation was approved.
It codes new bank lines in Xero using the rules a bookkeeper corrected, and queues what it cannot.
What you connect
How you wire it
What it must remember
It remembers every merchant to account code mapping and each correction a bookkeeper made, with the date and the reason. Without it, it recategorises the same supplier differently each month and your comparatives stop being comparable.
It drafts the next chase for each overdue invoice, matched to what that customer last said.
What you connect
How you wire it
What it must remember
It remembers which invoices it already chased, on what date, at which rung, and what the customer replied including any promised payment date. Without it, a customer who promised to pay on Friday gets the same reminder on Thursday and again on Saturday.
It ties subscription billing to revenue in the ledger and lists every difference with a cause.
What you connect
How you wire it
What it must remember
It remembers the recognition treatment agreed for each non standard contract, such as a mid term upgrade billed annually. Without it, it re-raises settled judgements every month and the revenue accountant explains the same contract forever.
It tracks each contractor's documents, tax forms and signatures, and holds payment until they exist.
What you connect
How you wire it
What it must remember
It remembers which documents each contractor has already signed, which ones expire and when, and the exemptions a legal reviewer granted. Without it, a contractor is asked to re-sign an agreement they completed and a genuine expiry goes unnoticed.
It translates each entity, eliminates intercompany balances and shows how each group line was built.
What you connect
How you wire it
What it must remember
It remembers the account mapping, the translation rates used in each closed period, and the elimination entries agreed. Without it, restating a prior month silently changes rates and last quarter's group accounts no longer reproduce.
It scores outgoing payments against your own history and flags only what a human has not cleared.
What you connect
How you wire it
What it must remember
It remembers every transaction a human already cleared and the exact pattern that triggered the flag. Without it, it re-flags the same monthly rent payment every month and the team learns to ignore the channel.
It matches bank lines to ledger entries, then writes a short explanation for each unreconciled break.
What you connect
How you wire it
What it must remember
It remembers which breaks a human already explained and accepted, and the ageing on each open item. Without it, every run re-presents the same known timing differences as new problems and the real breaks get lost.
It measures net burn from actual bank movement and states the runway with its assumptions shown.
What you connect
How you wire it
What it must remember
It remembers last week's runway figure and the assumptions behind it, including which large outflows a human classed as one-off. Without it, a single annual insurance payment reads as a permanent rise in burn and the runway swings for no real reason.
It tests each card transaction and receipt against your policy, then asks only the useful questions.
What you connect
How you wire it
What it must remember
It remembers which expenses a finance lead already waived and the one-off exceptions they approved, such as a conference dinner over the meal cap. Without it, it queries the same approved exception every week and cardholders stop reading it.
It compares this payroll run to the last approved one and explains every change, line by line.
What you connect
How you wire it
What it must remember
It remembers which pay changes were authorised and by whom, and the backdated adjustments already accounted for. Without it, an approved raise is flagged as unexplained every month and a genuinely unauthorised change looks like noise.
It reads each purchase request, applies your approval thresholds and routes it to the right person.
What you connect
How you wire it
What it must remember
It remembers who approved what, the delegations in force while someone is away, and the requests already rejected. Without it, the approval trail breaks mid chain and a rejected purchase returns a week later as if it were new.
It works the close list in order, verifies each task against the ledger, and chases whoever is late.
What you connect
How you wire it
What it must remember
It remembers which close tasks it already verified this cycle, who it has chased, and the recurring accruals posted last month. Without it, it reopens finished tasks and reminds the same owner three times in one day.
It reads invoices out of the AP inbox, extracts the fields, and matches them to the purchase order.
What you connect
How you wire it
What it must remember
It remembers every invoice number it has already processed per supplier and the bank details on file for each one. Without it, a resent invoice becomes a second bill and a changed payment detail passes through as normal.
It explains each material variance by tracing it to the transactions underneath before writing.
What you connect
How you wire it
What it must remember
It remembers the explanation each budget owner gave last month and which variances are known timing rather than overspend. Without it, it re-asks a question answered four weeks ago and this month's commentary contradicts the last pack.
It groups open upgrade PRs into safe batches, runs the suite and writes a risk note for each.
What you connect
How you wire it
What it must remember
It must remember which packages are pinned on purpose and why, plus the upgrades already tried and reverted. Without it, it proposes the same major bump that broke the build last month and burns a review cycle every week.
It reads a design file, lists the states and edge cases, and drafts one ticket per buildable slice.
What you connect
How you wire it
What it must remember
It must remember which components the design system already provides and the answers designers gave to earlier open questions. Without it, every breakdown proposes rebuilding the same button and asks the designer the same question about loading states.
It pulls alerts, deploy events and Slack messages into one minute by minute timeline draft.
What you connect
How you wire it
What it must remember
It must remember which timeline entries a human already corrected or marked irrelevant, and which deploy pipelines are noisy by design. Without it, every rerun reintroduces the same false causal link between a routine cron deploy and the outage.
It turns a long PR or design thread into a decision record draft with the options really considered.
What you connect
How you wire it
What it must remember
It must remember which ADRs are already accepted and which options were explicitly rejected, with the reason. Without it, it drafts a record that reopens a settled database choice and the team argues it a second time.
It tracks every action item from past incidents and nudges the owner with the incident behind it.
What you connect
How you wire it
What it must remember
It must remember which actions were consciously dropped and why, plus who was nudged last and on what date. Without it, it re-pings the same engineer daily about an action leadership already deprioritised and the nudges get muted.
It reads the merged PRs between two tags and drafts notes split by audience, user facing first.
What you connect
How you wire it
What it must remember
It must remember the agreed public wording for recurring features and which internal labels never appear in public notes. Without it, it relitigates the naming of the same subsystem every release and leaks internal project code names.
It reads recent CI runs, ranks tests by flake rate and drafts issues for the worst offenders.
What you connect
How you wire it
What it must remember
It must remember which flaky tests are already quarantined and which ones a human judged to be a real product bug rather than flake. Without it, it files a duplicate issue for a test that is already skipped and pointed at an open bug.
It reviews open PRs against your own conventions and posts one comment the author can act on.
What you connect
How you wire it
What it must remember
It must remember which suggestions the team already rejected on this repo, such as an abstraction the module owners voted down. Without it, it re-suggests that same rejected refactor on every PR touching the module and authors start skipping its comments.
It clusters stale and near identical tickets, proposes merges and drafts the detail they are missing.
What you connect
How you wire it
What it must remember
It must remember the clusters a human already rejected as genuinely different work, and the tickets deliberately kept open as long running trackers. Without it, it proposes merging the same two tickets every week and the grooming log becomes noise nobody opens.
It counts what is really migrated in the code and the database, then updates the tracker weekly.
What you connect
How you wire it
What it must remember
It must remember why each phase was paused and which call sites are deliberately staying on the old path forever. Without it, week six restates the plan as though nothing was decided and a paused phase gets reported as slipping.
It diffs your route handlers against the published reference and opens a pull request per drift.
What you connect
How you wire it
What it must remember
It must remember which endpoints are intentionally undocumented, such as internal admin routes, and which deprecations were already announced with dates. Without it, it keeps proposing to publish private endpoints and re-announces a deprecation partners were told about months ago.
It compares monthly spend by service, explains the biggest movers and proposes what to cut.
What you connect
How you wire it
What it must remember
It must remember which cost increases were approved on purpose and which savings were already rejected as too risky. Without it, it proposes shortening the same log retention every month after the compliance team ruled that out.
It reads incoming feedback, matches it to an existing roadmap bet and flags the genuinely new asks.
What you connect
How you wire it
What it must remember
It must remember the theme taxonomy and which asks product already declined, with the reason given. Without it, a declined integration request keeps resurfacing as a brand new theme and the register stops reflecting real demand.
It compares latency and error rates across releases and drafts a regression report with suspects.
What you connect
How you wire it
What it must remember
It must remember the accepted baseline per endpoint and the regressions already explained, such as latency traded deliberately for a new feature. Without it, it re-reports the same known slow endpoint every day and the real regression is buried in repeats.
It checks each new advisory against your real dependency graph and drafts only the reachable ones.
What you connect
How you wire it
What it must remember
It must remember every advisory already assessed as unreachable, who assessed it and when. Without it, it refiles the same unreachable transitive advisory week after week and the security queue loses all signal.
It reads new Sentry crash groups, dedupes them against open issues and drafts the ones worth filing.
What you connect
How you wire it
What it must remember
It must remember every crash group a human already dismissed as won't fix or third party noise, and the reason given. Without it, the same browser extension error is filed again every morning and triage stops being read.
It summarises the shift: what paged, what is still open, and what the next on-call should watch.
What you connect
How you wire it
What it must remember
It must remember the open threads carried forward from previous shifts and the documented workaround for each recurring alert. Without it, every brief starts from zero and the incoming on-call re-diagnoses a disk alert that has had a known one line fix for a month.
Logs brand mentions across social and news, then reports only the themes that changed today.
What you connect
How you wire it
What it must remember
It remembers which mention clusters have been acknowledged and which complaints support already resolved. Without it the digest reruns yesterday's spike as fresh news and the team chases a problem that was closed two days ago.
Reads mentions and relevant threads on X, then drafts replies only where a reply is warranted.
What you connect
How you wire it
What it must remember
It remembers which accounts it has already replied to, what it said, and which threads a human chose to skip. Without it the agent answers the same account twice with two different positions and keeps resurfacing threads the team deliberately left alone.
Fills next month's slots from existing assets and names the gaps nothing can cover.
What you connect
How you wire it
What it must remember
It keeps which themes ran in which week and which assets are already committed to a slot. Without it the calendar double-books the same theme and an asset held for launch week gets spent on a filler post.
Researches creators in your niche and shortlists them on audience fit, not follower counts.
What you connect
How you wire it
What it must remember
It records who has been contacted, who declined, who was rejected internally and the reason. Without it you re-pitch a creator who said no last quarter and spend the relationship on a second cold ask.
Gathers the week's posts, releases and saved links into a complete draft issue for the editor.
What you connect
How you wire it
What it must remember
It keeps a ledger of every link and story already sent and the issue number each appeared in. Without it a link two people drop separately goes out twice and subscribers spot the repeat before you do.
Diffs competitor changelogs, pricing and announcements weekly, separating real launches from noise.
What you connect
How you wire it
What it must remember
It keeps a dated snapshot of every competitor page and the claims each rival has already made. Without it a re-announced feature reads as brand new and your team builds a counter-message against something that shipped last year.
Writes platform-specific ad copy and creative briefs from the angles that already performed.
What you connect
How you wire it
What it must remember
It keeps every variant already tested, its result, and the positioning claims legal has cleared. Without it the agent reruns a hook that lost twice and writes copy around a claim the company moved off months ago.
Sorts incoming comments into reply, hide, escalate or ignore, citing the rule that applied.
What you connect
How you wire it
What it must remember
It keeps each author's prior warnings and every verdict a moderator overturned. Without it moderation drifts out of step: a member on a third strike gets a first warning while someone already cleared is hidden again.
Drafts community replies using only published documentation, each with the citation attached.
What you connect
How you wire it
What it must remember
It stores each question answered, the doc version the answer came from, and which answers went stale when that page changed. Without it the agent keeps repeating an answer that stopped being true at the last release.
Tracks events in your field, flags closing CFPs and drafts a proposal for each worthwhile fit.
What you connect
How you wire it
What it must remember
It keeps every proposal submitted, its outcome, and which abstract each event has already seen. Without it you resubmit a rejected abstract to the same track or miss that a deadline moved earlier this year.
Finds posts showing your product, logs each one and drafts a permission request for the author.
What you connect
How you wire it
What it must remember
It keeps which creators have already been asked, who granted or refused, and the exact wording of each permission. Without it you ask the same customer twice and eventually use an asset whose permission was never actually given.
Drafts founder posts from their own notes and shipped work, checked against a written voice sheet.
What you connect
How you wire it
What it must remember
It keeps every line the founder rewrote and every draft they rejected, ranked by how often the same correction recurs. Without it the voice drifts back to generic LinkedIn cadence and the founder fixes the same tic week after week.
Splits one article or talk into drafts sized for LinkedIn, X, Instagram and the newsletter.
What you connect
How you wire it
What it must remember
It records which angle from each long-form piece has already gone out, on which channel, and on what date. Without that it mines the same three paragraphs every time and your X audience reads the same hook twice in a fortnight.
Mines Reddit and forums for the questions buyers actually ask, then briefs the unanswered ones.
What you connect
How you wire it
What it must remember
It holds the clusters already turned into briefs and the URL of the piece that answered each one. Without it the bank refills with the same question every month and writers get briefed on something you published in March.
Produces show notes, timestamps and ranked clip candidates as soon as an episode finishes.
What you connect
How you wire it
What it must remember
It records which clips from each episode have already been cut and which channel each one ran on. Without it the strongest moment from a popular episode goes out three times and a guest sees their own quote recycled as new.
Drafts three follow-up emails: full attendees, early leavers and registrants who never showed.
What you connect
How you wire it
What it must remember
It keeps which contacts received which webinar sequence and where each one stopped replying. Without it a repeat attendee gets the same follow-up twice and someone who already booked a call is chased for that same call.
Turns an outline into a shootable script, then times chapters from the rough cut transcript.
What you connect
How you wire it
What it must remember
It keeps which hooks and titles you have already used and which product version each script described. Without it a new script walks viewers through a UI that was redesigned two releases ago.
It answers questions in Slack from the warehouse and shows the query, so the answer can be checked.
What you connect
How you wire it
What it must remember
It keeps every question already asked, the query that answered it, and the corrections an analyst made to those queries. Without it the same question returns a slightly different number each time and the team stops trusting any of them.
It collects the exports and approvals each control needs and files them against that control.
What you connect
How you wire it
What it must remember
It keeps the location and retrieval method for each control's evidence, plus which artefacts an auditor previously rejected and why. Without it every cycle restarts the hunt for where the access review export lives and re-submits rejected evidence.
It extracts who promised what by when from meeting notes, then follows each one until it closes.
What you connect
How you wire it
What it must remember
It holds every commitment ever extracted, its owner, the date stated and whether it closed. Without it a promise made in one meeting is lost by the next and the same work gets agreed twice.
It extracts the clauses that matter and flags only the ones that differ from what legal already agreed.
What you connect
How you wire it
What it must remember
It holds the fallback position legal accepted for each clause type and the contracts where an exception was granted. Without it the agent contradicts an earlier legal position and re-escalates terms the team settled months ago.
It watches table freshness and row volume, and raises only the gaps nobody has already accepted.
What you connect
How you wire it
What it must remember
It records every gap a human marked as expected, who accepted it and until when. Without it the same known-stale table is re-flagged hourly and the channel gets muted within a week.
It reads each application against the scorecard and writes a reasoned recommendation for a recruiter.
What you connect
How you wire it
What it must remember
It keeps the calibration recruiters gave it: which past candidates were advanced or rejected against each must-have, and the reason recorded. Without it the bar drifts between roles and applicants already rejected come back re-scored as strong.
It merges every interviewer's notes into one view, surfaces disagreement and lists what is still unknown.
What you connect
How you wire it
What it must remember
It tracks which questions each interviewer already asked this candidate and which attributes still have no evidence. Without it the final round re-asks the same questions and the loop closes with the gap it opened with.
It classifies inbound agreements, checks them against your standard form and routes them with a note.
What you connect
How you wire it
What it must remember
It remembers which counterparties already have an NDA on file and which routing rule was applied last time for each agreement type. Without it the same counterparty is sent a duplicate NDA and requests bounce between reviewers.
It runs the joiner checklist across payroll, calendar and docs, then chases the steps that stall.
What you connect
How you wire it
What it must remember
It records which steps are complete for each joiner and which were deliberately skipped for that contract type. Without it it re-chases finished tasks and asks a contractor to enrol in a benefits plan they cannot join.
It assembles revenue, delivery and hiring into one brief and marks what changed since last week.
What you connect
How you wire it
What it must remember
It stores last week's published brief, the figures behind it, and the initiatives leadership asked it to keep tracking. Without it every brief reads as a fresh snapshot and nobody can see the trend or the promise made three weeks ago.
It works out what happened to an order across store and payments, then drafts the resolution.
What you connect
How you wire it
What it must remember
It keeps the resolution applied to each past case type and the customers already granted a goodwill exception. Without it a repeat claimant collects a third free replacement and identical cases get different answers.
It answers policy questions in Slack with the clause it came from and the date that clause changed.
What you connect
How you wire it
What it must remember
It records the exceptions HR has already granted and the questions where the handbook turned out to be wrong or silent. Without it the agent forgets a policy exception already approved for that team and answers from a page HR corrected last month.
It tracks every vendor renewal date and seat count, and flags the licences nobody has opened.
What you connect
How you wire it
What it must remember
It records each contract's notice period, its owner, and the decisions taken at previous renewals including any discount negotiated. Without it a contract auto-renews because the notice window passed unnoticed, for the second year running.
It finds pages that contradict current reality, ranks them by readership and drafts the correction.
What you connect
How you wire it
What it must remember
It keeps which pages it reviewed, when, and which apparent contradictions an owner confirmed as intentional. Without it it re-flags the same deliberately simplified page every month and owners stop reading its issues.
It projects cover days per SKU, watches supplier lead times and raises the reorders worth raising.
What you connect
How you wire it
What it must remember
It keeps each SKU's buffer, the buyer's decision to discontinue or deliberately run a line down, and observed lead times against quoted ones. Without it it keeps proposing reorders for products the buyer already decided to drop.
It compares this week's metrics to last, finds the drivers, and writes the note your dashboard lacks.
What you connect
How you wire it
What it must remember
It keeps the agreed definition of every metric, the query that computes it, and last week's figure for each. Without it the same metric gets re-derived a different way each week and the note contradicts the one before it.