{
 "version": "v7",
 "month": "2026-10",
 "generated": "2026-10-15",
 "count": 169,
 "month_basis": "source date (date added when the source is undated)",
 "usecases": [
  {
   "slug": "find-exoplanet-candidate-tess",
   "url": "https://agentsetups.dev/use-case/find-exoplanet-candidate-tess/",
   "title": "Find an exoplanet candidate in NASA TESS data",
   "summary": "Claude Code ran 74 analyses and 1,000+ scripts; hidden-year transit predictions matched 3/3; Codex reviewed.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5",
    "Fable 5.1"
   ],
   "tools": [
    "TESS data"
   ],
   "prompt": "Goal: Search public telescope data for a planet candidate and try hard to disprove it.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: TESS data.\nSteps:\n1. Use the agent to download and parse the TESS data, write the search code and fit transits.\n2. Check nearby stars, look for secondary eclipses and other false positives, plot, and rerun failed tests.\n3. You choose the questions, which tests matter and what counts as pass/fail.\n4. Get independent reviews from a different agent (Codex) and fresh read-only sessions.\n5. Ask it for ways to prove it ISN’T a planet: hide a year, predict its transits from the other years, check only those times.\n6. Search catalogues and literature to see if it is already known; call it a candidate, not a confirmed planet.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/This_Cell_1829 — https://www.reddit.com/r/ClaudeAI/comments/1wzw8zd/i_think_i_found_a_planet_nobody_knew_existed_i/",
   "steps": [
    "Use the agent to download and parse the TESS data, write the search code and fit transits.",
    "Check nearby stars, look for secondary eclipses and other false positives, plot, and rerun failed tests.",
    "You choose the questions, which tests matter and what counts as pass/fail.",
    "Get independent reviews from a different agent (Codex) and fresh read-only sessions.",
    "Ask it for ways to prove it ISN’T a planet: hide a year, predict its transits from the other years, check only those times.",
    "Search catalogues and literature to see if it is already known; call it a candidate, not a confirmed planet."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 100.0,
   "sources": [
    {
     "author": "/u/This_Cell_1829",
     "handle": "/u/This_Cell_1829",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wzw8zd/i_think_i_found_a_planet_nobody_knew_existed_i/",
     "platform": "reddit",
     "date": "2026-10-07",
     "primary": true
    },
    {
     "author": "pyduan",
     "handle": "pyduan",
     "url": "https://news.ycombinator.com/item?id=50002665",
     "platform": "hn",
     "date": "2026-10-08",
     "primary": false
    },
    {
     "author": "NASA Watch",
     "handle": "@NASAWatch",
     "url": "https://x.com/NASAWatch/status/2108953701578596847",
     "platform": "x",
     "date": "2026-10-10",
     "primary": false
    },
    {
     "author": "SciTech Era",
     "handle": "@SciTechera",
     "url": "https://x.com/SciTechera/status/2110296881071014279",
     "platform": "x",
     "date": "2026-10-14",
     "primary": false
    }
   ]
  },
  {
   "slug": "gaussian-splats-blender-mcp",
   "url": "https://agentsetups.dev/use-case/gaussian-splats-blender-mcp/",
   "title": "Make Gaussian splats with Blender MCP and Lichtfeld Studio",
   "summary": "GPT-6.1 Astra drove Blender MCP + Lichtfeld Studio to recreate an object as a crisp splat for the web.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [],
   "models": [
    "GPT-6.1 Astra"
   ],
   "tools": [
    "Blender MCP",
    "Lichtfeld Studio",
    "SuperSplat"
   ],
   "prompt": "Goal: Create a simple Gaussian splat of an object for the web.\nSetup: tools/MCPs stated: Blender MCP, Lichtfeld Studio, SuperSplat.\nSteps:\n1. Connect Blender MCP and Lichtfeld Studio to your agent.\n2. Ask it to recreate the object (the author recreated an agent “dot” logo).\n3. View and publish it in the SuperSplat editor (PlayCanvas).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: abstrakt — https://x.com/abstrakt314/status/2105756028935504032",
   "steps": [
    "Connect Blender MCP and Lichtfeld Studio to your agent.",
    "Ask it to recreate the object (the author recreated an agent “dot” logo).",
    "View and publish it in the SuperSplat editor (PlayCanvas)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 96.4,
   "sources": [
    {
     "author": "abstrakt",
     "handle": "@abstrakt314",
     "url": "https://x.com/abstrakt314/status/2105756028935504032",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "plan-and-book-a-trip",
   "url": "https://agentsetups.dev/use-case/plan-and-book-a-trip/",
   "title": "Have your agent plan and book a whole trip",
   "summary": "Agents researched and booked a Lisbon trip, booked every Japan restaurant and negotiated a dinner slot in Japanese.",
   "category": "travel",
   "category_label": "Travel",
   "agents": [
    "Grok Bot",
    "Meta Muse",
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Plan and book my trip.\nSetup: agents used in source: Grok Bot, Meta Muse, Codex.\nSteps:\n1. Ask for the trip (destination, dates, budget).\n2. Let the agent research options and make the bookings (one author let it use his card).\n3. For restaurants and hotels, let it handle the back-and-forth, including in the local language (Muse negotiated in Japanese).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: SCOTTY BEAM — https://x.com/ScottyBeamIO/status/2109660484144169136 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask for the trip (destination, dates, budget).",
    "Let the agent research options and make the bookings (one author let it use his card).",
    "For restaurants and hotels, let it handle the back-and-forth, including in the local language (Muse negotiated in Japanese)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 92.3,
   "sources": [
    {
     "author": "SCOTTY BEAM",
     "handle": "@ScottyBeamIO",
     "url": "https://x.com/ScottyBeamIO/status/2109660484144169136",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    },
    {
     "author": "Han Fang",
     "handle": "@Han_Fang_",
     "url": "https://x.com/Han_Fang_/status/2101874865385169348",
     "platform": "x",
     "date": "2026-09-21",
     "primary": false
    },
    {
     "author": "Atrophius",
     "handle": "@Atrophius",
     "url": "https://x.com/Atrophius/status/2096679579398111601",
     "platform": "x",
     "date": "2026-09-06",
     "primary": false
    }
   ]
  },
  {
   "slug": "agents-discover-materials",
   "url": "https://agentsetups.dev/use-case/agents-discover-materials/",
   "title": "Run agent teams on materials-science discovery",
   "summary": "Opus 5.5 agents ran DFT simulations (PBE+U, HSE06) and found two room-temperature magnetic semiconductor candidates.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "DFT (PBE+U, HSE06)"
   ],
   "prompt": "Goal: Use agents to search for materials with target properties.\nSetup: agents used in source: Claude; tools/MCPs stated: DFT (PBE+U, HSE06).\nSteps:\n1. Define the target property window (e.g. band gap, spin splitting, magnetic ordering temperature).\n2. Have agents propose candidate compounds and run density functional theory: a fast pass (PBE+U) then a more accurate one (HSE06).\n3. Calibrate predictions against a known material and report candidates with caveats.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Vals AI — https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors (summarised from source; the source has no explicit step list)",
   "steps": [
    "Define the target property window (e.g. band gap, spin splitting, magnetic ordering temperature).",
    "Have agents propose candidate compounds and run density functional theory: a fast pass (PBE+U) then a more accurate one (HSE06).",
    "Calibrate predictions against a known material and report candidates with caveats."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 90.9,
   "sources": [
    {
     "author": "Vals AI",
     "handle": "vals.ai",
     "url": "https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors",
     "platform": "blog",
     "date": "2026-10-05",
     "primary": true
    },
    {
     "author": "outlier99",
     "handle": "outlier99",
     "url": "https://news.ycombinator.com/item?id=49970667",
     "platform": "hn",
     "date": "2026-10-05",
     "primary": false
    }
   ]
  },
  {
   "slug": "trading-bot-backtest",
   "url": "https://agentsetups.dev/use-case/trading-bot-backtest/",
   "title": "Build and backtest a trading bot with no coding background",
   "summary": "Non-developers have an agent build, backtest and run a trading strategy; claimed results are unverified.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Claude",
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Have the agent help me design, backtest and build a trading strategy from scratch.\nSetup: agents used in source: Claude, Grok Bot.\nSteps:\n1. Explain the market and the strategy idea in plain language; the author started with zero technical background.\n2. Have the agent backtest the strategy (Fable 5 was used for backtesting and building).\n3. Check the backtest for bugs. A separate dev.to write-up found its own backtest had bugs that inflated results.\n4. Run the bot from an agent you can talk to from your phone (GrokBot in the step-by-step source).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: Profit figures in sources are the authors’ own unverified claims.\nBased on: Davidd Tech — https://x.com/DaviddDotTech/status/2109556174555386014 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Explain the market and the strategy idea in plain language; the author started with zero technical background.",
    "Have the agent backtest the strategy (Fable 5 was used for backtesting and building).",
    "Check the backtest for bugs. A separate dev.to write-up found its own backtest had bugs that inflated results.",
    "Run the bot from an agent you can talk to from your phone (GrokBot in the step-by-step source)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 89.8,
   "sources": [
    {
     "author": "Davidd Tech",
     "handle": "@DaviddDotTech",
     "url": "https://x.com/DaviddDotTech/status/2109556174555386014",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    },
    {
     "author": "Just a Side Project",
     "handle": "@just_a_side_project",
     "url": "https://dev.to/just_a_side_project/debug-log-3-i-had-claude-code-backtest-a-trading-strategy-for-a-week-and-it-found-three-bugs-in-5g50",
     "platform": "devto",
     "date": "2026-09-17",
     "primary": false
    }
   ]
  },
  {
   "slug": "sonnet-main-opus-advisor-split",
   "url": "https://agentsetups.dev/use-case/sonnet-main-opus-advisor-split/",
   "title": "Run Sonnet as main, Haiku explorers and Opus as advisor",
   "summary": "Start Claude Code with --advisor opus: Sonnet 5 codes, Haiku 5.5 subagents search, Opus is consulted only at 3 checkpoints.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [
    "Sonnet 5",
    "Haiku 5.5",
    "Opus 5.5"
   ],
   "tools": [],
   "prompt": "Goal: Cut tokens by putting each model only on the work it is best at.\nSetup: agents used in source: Claude.\nSteps:\n1. Start Claude Code with: claude --model sonnet --advisor opus\n2. Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference).\n3. Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error hits twice, and before calling a task done.\n4. Ask Claude Code to show every config change as a diff first, with no edits until you say go.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: delost — https://x.com/thedelost/status/2109369295860035641",
   "steps": [
    "Start Claude Code with: claude --model sonnet --advisor opus",
    "Create three read-only Haiku 5.5 subagents: search (maps the repo), grep (finds call sites), docs (pulls the API reference).",
    "Add one rule to CLAUDE.md: consult the advisor before locking a plan, after the same error hits twice, and before calling a task done.",
    "Ask Claude Code to show every config change as a diff first, with no edits until you say go."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 89.4,
   "sources": [
    {
     "author": "delost",
     "handle": "@thedelost",
     "url": "https://x.com/thedelost/status/2109369295860035641",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "docs-not-memory",
   "url": "https://agentsetups.dev/use-case/docs-not-memory/",
   "title": "Give agents documentation instead of memory plugins",
   "summary": "Have the agent keep specs, plans and indexes in an internal/ folder, read before work and update after.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Replace RAG “memory” with documentation the agent maintains.\nSetup: agents used in source: Claude.\nSteps:\n1. Create an internal/ folder; ask the agent to write down specs, plans and indexes there.\n2. Task it to always read the relevant docs and index before working, and update them afterwards.\n3. Documentation is written by the working agent while the work is fresh.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: liao.gg — https://liao.gg/blog/agents-dont-need-memory",
   "steps": [
    "Create an internal/ folder; ask the agent to write down specs, plans and indexes there.",
    "Task it to always read the relevant docs and index before working, and update them afterwards.",
    "Documentation is written by the working agent while the work is fresh."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 86.1,
   "sources": [
    {
     "author": "liao.gg",
     "handle": "liao.gg",
     "url": "https://liao.gg/blog/agents-dont-need-memory",
     "platform": "blog",
     "date": "2026-10-03",
     "primary": true
    },
    {
     "author": "kmeh",
     "handle": "kmeh",
     "url": "https://news.ycombinator.com/item?id=49945933",
     "platform": "hn",
     "date": "2026-10-03",
     "primary": false
    }
   ]
  },
  {
   "slug": "backtest-trading-strategy-claude",
   "url": "https://agentsetups.dev/use-case/backtest-trading-strategy-claude/",
   "title": "Build a strategy backtesting engine with Claude Code",
   "summary": "Describe entry, exit, stop and size in plain English; include fees and slippage; get win rate, max drawdown and a dashboard.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "TradingView"
   ],
   "prompt": "Goal: Test a trading strategy on historical data before risking money.\nSetup: agents used in source: Claude; tools/MCPs stated: TradingView.\nSteps:\n1. Open Claude Code and send the backtesting prompt (attached to the post).\n2. Describe your strategy in plain English: entry, exit, stop, position size.\n3. Tell it to include fees and slippage.\n4. Run it and ask for win rate, max drawdown and average R per trade.\n5. Ask for a dashboard to visualise the results.\n6. Quality-check: import the source into TradingView and compare.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The author’s claimed returns are his own; past performance isn’t a forecast.\nBased on: Miles Deutscher — https://x.com/milesdeutscher/status/2108079450927833334",
   "steps": [
    "Open Claude Code and send the backtesting prompt (attached to the post).",
    "Describe your strategy in plain English: entry, exit, stop, position size.",
    "Tell it to include fees and slippage.",
    "Run it and ask for win rate, max drawdown and average R per trade.",
    "Ask for a dashboard to visualise the results.",
    "Quality-check: import the source into TradingView and compare."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 81.6,
   "sources": [
    {
     "author": "Miles Deutscher",
     "handle": "@milesdeutscher",
     "url": "https://x.com/milesdeutscher/status/2108079450927833334",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "decompile-fps-agent-swarm",
   "url": "https://agentsetups.dev/use-case/decompile-fps-agent-swarm/",
   "title": "Decompile a full game with a long-running agent swarm",
   "summary": "Over 3 months and 500B tokens, worker + reviewer agents reached 99% of functions, 83% byte-exact.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Sonnet 5",
    "Opus 5.5",
    "Luna"
   ],
   "tools": [
    "Discord"
   ],
   "prompt": "Goal: Run a multi-month decompilation with worker and reviewer agents.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Discord.\nSteps:\n1. Start with 3 worker agents decompiling and committing, plus 1 reviewer that coordinates and flags bugs; communicate via Discord.\n2. Trigger compaction earlier (they cut the threshold from 90% to 42% context fill) to save tokens.\n3. Stop the reviewer trusting workers’ comments: verify deviations against the original independently.\n4. Build a verification harness, then scale workers and let them run autonomously.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: momo5502 — https://momo5502.com/posts/2026-10-09-game-decompilation/",
   "steps": [
    "Start with 3 worker agents decompiling and committing, plus 1 reviewer that coordinates and flags bugs; communicate via Discord.",
    "Trigger compaction earlier (they cut the threshold from 90% to 42% context fill) to save tokens.",
    "Stop the reviewer trusting workers’ comments: verify deviations against the original independently.",
    "Build a verification harness, then scale workers and let them run autonomously."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 81.6,
   "sources": [
    {
     "author": "momo5502",
     "handle": "momo5502",
     "url": "https://momo5502.com/posts/2026-10-09-game-decompilation/",
     "platform": "blog",
     "date": "2026-10-09",
     "primary": true
    },
    {
     "author": "davikr",
     "handle": "davikr",
     "url": "https://news.ycombinator.com/item?id=50039092",
     "platform": "hn",
     "date": "2026-10-11",
     "primary": false
    }
   ]
  },
  {
   "slug": "coding-hospital-cockroach",
   "url": "https://agentsetups.dev/use-case/coding-hospital-cockroach/",
   "title": "Run coding agents like a hospital: Db2 support in 2 days",
   "summary": "Cockroach Labs’ label-triggered role agents planned 15 sub-issues and shipped Db2 migration for $4,172.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "GitHub Actions"
   ],
   "prompt": "Goal: Set up role-based agents with hard rules to ship a large feature safely.\nSetup: agents used in source: Claude; tools/MCPs stated: GitHub Actions.\nSteps:\n1. Start from a single GitHub issue describing the ask.\n2. A planning agent decomposes it into sub-issues with an explicit dependency graph.\n3. Applying a label fires a GitHub workflow that loads a role-specific prompt (the agent acts as a hospital employee).\n4. Encode rules in skills: no code before a plan, no plan without review.\n5. Accept slower runs (even 10x) in exchange for well-tested, in-scope code.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Cockroach Labs — https://www.cockroachlabs.com/blog/experiment-running-hospital-code/",
   "steps": [
    "Start from a single GitHub issue describing the ask.",
    "A planning agent decomposes it into sub-issues with an explicit dependency graph.",
    "Applying a label fires a GitHub workflow that loads a role-specific prompt (the agent acts as a hospital employee).",
    "Encode rules in skills: no code before a plan, no plan without review.",
    "Accept slower runs (even 10x) in exchange for well-tested, in-scope code."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 80.4,
   "sources": [
    {
     "author": "Cockroach Labs",
     "handle": "cockroachlabs.com",
     "url": "https://www.cockroachlabs.com/blog/experiment-running-hospital-code/",
     "platform": "blog",
     "date": "2026-10-08",
     "primary": true
    },
    {
     "author": "rafiss",
     "handle": "rafiss",
     "url": "https://news.ycombinator.com/item?id=50021899",
     "platform": "hn",
     "date": "2026-10-09",
     "primary": false
    }
   ]
  },
  {
   "slug": "game-as-agent-harness",
   "url": "https://agentsetups.dev/use-case/game-as-agent-harness/",
   "title": "Make your game legible to AI agents",
   "summary": "Kyle Kukshtel’s talk: engineer the game itself as a harness so agentic iteration on gameplay is faster.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Make my game easier for coding agents to inspect, test and iterate on.\nSetup: agents used in source: Claude.\nSteps:\n1. Treat the game as a harness: expose state and actions the agent can read and drive.\n2. Shorten the loop between a change and a verifiable result.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kyle Kukshtel — https://kylekukshtel.com/ai-harness-engineering-game-development-claude-code (summarised from source; the source has no explicit step list)",
   "steps": [
    "Treat the game as a harness: expose state and actions the agent can read and drive.",
    "Shorten the loop between a change and a verifiable result."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 80.4,
   "sources": [
    {
     "author": "Kyle Kukshtel",
     "handle": "kylekukshtel.com",
     "url": "https://kylekukshtel.com/ai-harness-engineering-game-development-claude-code",
     "platform": "blog",
     "date": "2026-10-10",
     "primary": true
    },
    {
     "author": "kkukshtel",
     "handle": "kkukshtel",
     "url": "https://news.ycombinator.com/item?id=50072120",
     "platform": "hn",
     "date": "2026-10-13",
     "primary": false
    }
   ]
  },
  {
   "slug": "dots-as-project-manager",
   "url": "https://agentsetups.dev/use-case/dots-as-project-manager/",
   "title": "Run your ChatGPT Dot as a project manager",
   "summary": "@AlexFinn says Dots get far more useful as a project manager than as an assistant, using the desktop app’s tools.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "ChatGPT desktop app"
   ],
   "prompt": "Goal: Set my ChatGPT Dot up to manage a project, not just answer requests.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: ChatGPT desktop app.\nSteps:\n1. Work from the ChatGPT desktop app, which gives the Dot the most tools.\n2. Give the Dot the project to own and manage, rather than treating it as a general assistant.\n3. Use the skill the author links in the post as the starting brief.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The post is cut off after the setup idea; open it for the linked skill.\nBased on: Alex Finn — https://x.com/AlexFinn/status/2105702256075276523 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Work from the ChatGPT desktop app, which gives the Dot the most tools.",
    "Give the Dot the project to own and manage, rather than treating it as a general assistant.",
    "Use the skill the author links in the post as the starting brief."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 79.5,
   "sources": [
    {
     "author": "Alex Finn",
     "handle": "@AlexFinn",
     "url": "https://x.com/AlexFinn/status/2105702256075276523",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "paid-web-app-playbook",
   "url": "https://agentsetups.dev/use-case/paid-web-app-playbook/",
   "title": "Build paid web apps with an Opus front end and Codex",
   "summary": "The founder’s playbook behind $100K MRR: one-shot a baseline, name the stack, use a quality reference per feature, self-score.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Supabase",
    "Stripe"
   ],
   "prompt": "Goal: Build a paid web app with AI agents.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Supabase, Stripe.\nSteps:\n1. Find ideas in tools you use every day: what is missing in Codex, Cursor or Figma?\n2. Use Opus 5.5 for the front end and Codex for the harness.\n3. One-shot a baseline, then break the work into parts.\n4. Name your stack and future needs up front (React + Vite, Supabase, Stripe).\n5. Give one quality reference per feature (Figma, Spline, Linear).\n6. Add an AI layer through APIs so the tool generates, not just displays.\n7. Have the AI score its work out of 10 and screenshot its own mistakes.\n8. Record a demo, post it everywhere, paste the feedback into your agent, and ship.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Meng To — https://x.com/MengTo/status/2107862479548403806",
   "steps": [
    "Find ideas in tools you use every day: what is missing in Codex, Cursor or Figma?",
    "Use Opus 5.5 for the front end and Codex for the harness.",
    "One-shot a baseline, then break the work into parts.",
    "Name your stack and future needs up front (React + Vite, Supabase, Stripe).",
    "Give one quality reference per feature (Figma, Spline, Linear).",
    "Add an AI layer through APIs so the tool generates, not just displays.",
    "Have the AI score its work out of 10 and screenshot its own mistakes.",
    "Record a demo, post it everywhere, paste the feedback into your agent, and ship."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 79.2,
   "sources": [
    {
     "author": "Meng To",
     "handle": "@MengTo",
     "url": "https://x.com/MengTo/status/2107862479548403806",
     "platform": "x",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "j2me-shooter-one-prompt",
   "url": "https://agentsetups.dev/use-case/j2me-shooter-one-prompt/",
   "title": "Make a 3D shooter for 20-year-old phones in one prompt",
   "summary": "Opus 5.5 wrote an integer-math Java engine, its own sprite renderer, 4 maps, 8 MIDI tracks and TTS voice lines.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "ffmpeg",
    "J2ME"
   ],
   "prompt": "Goal: Build a retro 3D shooter for old J2ME phones.\nSetup: agents used in source: Claude; tools/MCPs stated: ffmpeg, J2ME.\nSteps:\n1. Ask for a Duke Nukem 3D-style shooter for old J2ME phones.\n2. Expect an integer-math 3D engine in Java so old phones can run it.\n3. Let it write its own 3D renderer in Python to model and render sprites; generate textures and skies in code.\n4. Have it design maps, compose MIDI tracks, and make voice lines with TTS edited via ffmpeg.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/wollymonjac — https://www.reddit.com/r/ClaudeAI/comments/1x120gj/opus_55_can_make_games_for_2_decade_old_phones/",
   "steps": [
    "Ask for a Duke Nukem 3D-style shooter for old J2ME phones.",
    "Expect an integer-math 3D engine in Java so old phones can run it.",
    "Let it write its own 3D renderer in Python to model and render sprites; generate textures and skies in code.",
    "Have it design maps, compose MIDI tracks, and make voice lines with TTS edited via ffmpeg."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 78.1,
   "sources": [
    {
     "author": "/u/wollymonjac",
     "handle": "/u/wollymonjac",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1x120gj/opus_55_can_make_games_for_2_decade_old_phones/",
     "platform": "reddit",
     "date": "2026-10-08",
     "primary": true
    },
    {
     "author": "/u/HugoDzz",
     "handle": "/u/HugoDzz",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wv2r73/made_a_destroy_any_website_stickman_game/",
     "platform": "reddit",
     "date": "2026-10-01",
     "primary": false
    }
   ]
  },
  {
   "slug": "one-shot-invisible-cities-viz",
   "url": "https://agentsetups.dev/use-case/one-shot-invisible-cities-viz/",
   "title": "Give one prompt and 6 hours for a 3D visualisation",
   "summary": "Same prompt to GPT-6 Astra in Codex and Opus 5.5 in Claude Code; Opus ran 6 subagents and finished a three.js piece in 1h25.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5",
    "GPT-6 Astra"
   ],
   "tools": [
    "three.js",
    "pnpm"
   ],
   "prompt": "Goal: Compare how models handle a long one-shot design task.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: three.js, pnpm.\nSteps:\n1. Prompt: “Make a three.js (pnpm) visualization of all Invisible Cities by Italo Calvino. Don’t ask questions, it is a one-shot task. You have 6h of work, use it until it becomes a masterpiece.”\n2. Run it in Codex (GPT-6 Astra) and in Claude Code (Opus 5.5).\n3. Compare: Opus used 6 parallel subagents (~7 agent-hours) and stopped after 1h25.\n4. Try the same prompt on other models and harnesses.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Piotr Migdał — https://quesma.com/blog/invisible-cities-one-shot/",
   "steps": [
    "Prompt: “Make a three.js (pnpm) visualization of all Invisible Cities by Italo Calvino. Don’t ask questions, it is a one-shot task. You have 6h of work, use it until it becomes a masterpiece.”",
    "Run it in Codex (GPT-6 Astra) and in Claude Code (Opus 5.5).",
    "Compare: Opus used 6 parallel subagents (~7 agent-hours) and stopped after 1h25.",
    "Try the same prompt on other models and harnesses."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 77.9,
   "sources": [
    {
     "author": "Piotr Migdał",
     "handle": "quesma.com",
     "url": "https://quesma.com/blog/invisible-cities-one-shot/",
     "platform": "blog",
     "date": "2026-10-07",
     "primary": true
    },
    {
     "author": "stared",
     "handle": "stared",
     "url": "https://news.ycombinator.com/item?id=50004790",
     "platform": "hn",
     "date": "2026-10-08",
     "primary": false
    }
   ]
  },
  {
   "slug": "perplexity-computer-port-windows-app",
   "url": "https://agentsetups.dev/use-case/perplexity-computer-port-windows-app/",
   "title": "Port a Windows-only app to Linux with Perplexity Computer",
   "summary": "Computer decompiled a keyboard app with headless Ghidra and rebuilt it in Rust for Linux, with music-synced lighting and macros.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [],
   "tools": [
    "Ghidra",
    "Rust",
    "PipeWire"
   ],
   "prompt": "Goal: Get a Linux version of a Windows-only app with no docs.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Ghidra, Rust, PipeWire.\nSteps:\n1. Have Computer download the binary into its cloud sandbox and decompile it with headless Ghidra.\n2. Have it read the decompiled code to learn how the app drives the hardware.\n3. Rebuild it piece by piece as a native Rust app (here: lighting synced to music via PipeWire, 3D view, key remapping, macros, profiles).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: Vendor CEO post describing a user’s project.\nBased on: Aravind Srinivas — https://x.com/AravSrinivas/status/2110389625277813212",
   "steps": [
    "Have Computer download the binary into its cloud sandbox and decompile it with headless Ghidra.",
    "Have it read the decompiled code to learn how the app drives the hardware.",
    "Rebuild it piece by piece as a native Rust app (here: lighting synced to music via PipeWire, 3D view, key remapping, macros, profiles)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 77.2,
   "sources": [
    {
     "author": "Aravind Srinivas",
     "handle": "@AravSrinivas",
     "url": "https://x.com/AravSrinivas/status/2110389625277813212",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-run-solo-business-stack",
   "url": "https://agentsetups.dev/use-case/grokbot-run-solo-business-stack/",
   "title": "Run a one-person business on Grok Bot plugins",
   "summary": "@Av1dlive’s $165/mo stack: Whop, Vercel+GitHub, draft-only inbox and writer bots, Notion CRM, chief-of-staff report.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Grok Bot",
    "Cursor"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Whop",
    "Vercel",
    "GitHub",
    "Gmail",
    "Notion",
    "Cursor cloud agents",
    "Klaviyo"
   ],
   "prompt": "Goal: Run my online business with a team of Grok Bot bots and plugins.\nSetup: agents used in source: Grok Bot, Cursor; tools/MCPs stated: Whop, Vercel, GitHub, Gmail, Notion, Cursor cloud agents, Klaviyo.\nSteps:\n1. Required: money via the Whop plugin; site via Vercel + GitHub plugins; inbox via Gmail + an inbox bot that drafts, never sends.\n2. CRM in Notion inboxes built with Grok Bot; content via the X plugin + draft-only writer bots; numbers in Notion.\n3. Oversight: a chief-of-staff morning report, plus a bot that audits every other bot.\n4. Add later as needed: support inbox bot, Klaviyo + Grok Bot routines for email, lead bots, builder + reviewer bots, scheduling routines with a content calendar.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Avid — https://x.com/Av1dlive/status/2110329712715182092",
   "steps": [
    "Required: money via the Whop plugin; site via Vercel + GitHub plugins; inbox via Gmail + an inbox bot that drafts, never sends.",
    "CRM in Notion inboxes built with Grok Bot; content via the X plugin + draft-only writer bots; numbers in Notion.",
    "Oversight: a chief-of-staff morning report, plus a bot that audits every other bot.",
    "Add later as needed: support inbox bot, Klaviyo + Grok Bot routines for email, lead bots, builder + reviewer bots, scheduling routines with a content calendar."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 74.9,
   "sources": [
    {
     "author": "Avid",
     "handle": "@Av1dlive",
     "url": "https://x.com/Av1dlive/status/2110329712715182092",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "social-publication-engine",
   "url": "https://agentsetups.dev/use-case/social-publication-engine/",
   "title": "Run a social publication engine from your agent",
   "summary": "A publication skill prepares the reel, cover and caption; you give feedback; it publishes via the Buffer API, then verifies and archives.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [
    "Buffer API",
    "upload-post API",
    "Claude Code routines"
   ],
   "prompt": "Goal: Prepare, review and publish social posts from my agent.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Buffer API, upload-post API, Claude Code routines.\nSteps:\n1. Input: project context plus an automated screencast.\n2. Use a publication skill that holds your visual and copy rules.\n3. Prepare a vertical reel (headline, music, intro footage), plus a cover and caption.\n4. Review it: give text feedback, get a revision, then approve.\n5. Publish via the Buffer API to Instagram. Then check the live post and save the MP4, caption, render settings and post URL.\n6. Variant: a daily Claude Code routine turns the latest blog post into LinkedIn, X and Reddit posts and publishes them via the upload-post API.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: AmirMušić — https://x.com/AmirMushich/status/2106716622761189875",
   "steps": [
    "Input: project context plus an automated screencast.",
    "Use a publication skill that holds your visual and copy rules.",
    "Prepare a vertical reel (headline, music, intro footage), plus a cover and caption.",
    "Review it: give text feedback, get a revision, then approve.",
    "Publish via the Buffer API to Instagram. Then check the live post and save the MP4, caption, render settings and post URL.",
    "Variant: a daily Claude Code routine turns the latest blog post into LinkedIn, X and Reddit posts and publishes them via the upload-post API."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 73.9,
   "sources": [
    {
     "author": "AmirMušić",
     "handle": "@AmirMushich",
     "url": "https://x.com/AmirMushich/status/2106716622761189875",
     "platform": "x",
     "date": "2026-10-04",
     "primary": true
    },
    {
     "author": "Ayush 🙏",
     "handle": "@ayushtweetshere",
     "url": "https://x.com/ayushtweetshere/status/2096832340110856297",
     "platform": "x",
     "date": "2026-09-07",
     "primary": false
    }
   ]
  },
  {
   "slug": "codex-rebuild-personal-website-s3",
   "url": "https://agentsetups.dev/use-case/codex-rebuild-personal-website-s3/",
   "title": "Rebuild your personal site with Codex and a deploy tool",
   "summary": "After ~5 failed rebuilds, Codex built the site plus a small tool to add writing and deploy the static site to S3.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Replace my old simple website setup without losing its simplicity.\nSetup: agents used in source: Codex.\nSteps:\n1. Have Codex build the static site.\n2. Ask it for a small tool to add new writing.\n3. Have the same tool deploy the static site to S3.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Karri Saarinen — https://x.com/karrisaarinen/status/2107356889990504672 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Have Codex build the static site.",
    "Ask it for a small tool to add new writing.",
    "Have the same tool deploy the static site to S3."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 72.6,
   "sources": [
    {
     "author": "Karri Saarinen",
     "handle": "@karrisaarinen",
     "url": "https://x.com/karrisaarinen/status/2107356889990504672",
     "platform": "x",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "voice-assistant-on-claude-p",
   "url": "https://agentsetups.dev/use-case/voice-assistant-on-claude-p/",
   "title": "Build a hold-to-talk Mac assistant on claude -p",
   "summary": "Atticus moves windows, finds files and shops in Chrome using your Claude plan; repeated asks become no-AI shortcuts.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "claude -p"
   ],
   "prompt": "Goal: Control my Mac by voice using the Claude plan I already have.\nSetup: agents used in source: Claude; tools/MCPs stated: claude -p.\nSteps:\n1. Install Atticus; it runs through Claude Code (claude -p), no API key.\n2. Hold the hotkey, say what you need, let go.\n3. Repeated actions become learned shortcuts that skip the AI (e.g. 5.5s → 0.4s).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: SaarthRanka — https://news.ycombinator.com/item?id=50049588",
   "steps": [
    "Install Atticus; it runs through Claude Code (claude -p), no API key.",
    "Hold the hotkey, say what you need, let go.",
    "Repeated actions become learned shortcuts that skip the AI (e.g. 5.5s → 0.4s)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 71.4,
   "sources": [
    {
     "author": "SaarthRanka",
     "handle": "SaarthRanka",
     "url": "https://news.ycombinator.com/item?id=50049588",
     "platform": "hn",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "manus-travel-footage-vlog",
   "url": "https://agentsetups.dev/use-case/manus-travel-footage-vlog/",
   "title": "Turn 2 hours of travel clips into a vlog with Manus",
   "summary": "From 125 clips, one prompt gave a 12:48 first cut following the trip; the finished vlog added captions, music and effects.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Manus"
   ],
   "models": [],
   "tools": [
    "Manus Video"
   ],
   "prompt": "Goal: Edit a pile of travel footage into a story-driven vlog.\nSetup: agents used in source: Manus; tools/MCPs stated: Manus Video.\nSteps:\n1. Upload all clips.\n2. One prompt: find the highlights and make a first cut that follows the trip.\n3. Add captions, music and effects for the final version.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: Vendor post about a user’s project.\nBased on: Manus — https://x.com/ManusAI/status/2107105397781963086 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Upload all clips.",
    "One prompt: find the highlights and make a first cut that follows the trip.",
    "Add captions, music and effects for the final version."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 70.5,
   "sources": [
    {
     "author": "Manus",
     "handle": "@ManusAI",
     "url": "https://x.com/ManusAI/status/2107105397781963086",
     "platform": "x",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-curate-x-follow-list",
   "url": "https://agentsetups.dev/use-case/grokbot-curate-x-follow-list/",
   "title": "Ask Grok Bot to build your X follow list",
   "summary": "@FundamentEdge asked Grok Bot for 50 accounts to follow to keep up with AI, each with a one-line reason.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "X"
   ],
   "prompt": "Goal: Build a high-signal timeline on a topic.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Ask your Grok Bot to recommend 50 people to follow on a topic, grouped by theme with a one-line reason each.\n2. Crowdsource what it missed in replies.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Brett Caughran — https://x.com/FundamentEdge/status/2109412745045242352",
   "steps": [
    "Ask your Grok Bot to recommend 50 people to follow on a topic, grouped by theme with a one-line reason each.",
    "Crowdsource what it missed in replies."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 70.4,
   "sources": [
    {
     "author": "Brett Caughran",
     "handle": "@FundamentEdge",
     "url": "https://x.com/FundamentEdge/status/2109412745045242352",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-personal-cfo-monthly",
   "url": "https://agentsetups.dev/use-case/grokbot-personal-cfo-monthly/",
   "title": "Set up a read-only personal CFO agent",
   "summary": "Shane Mac’s Grok Bot CFO sent monthly money reports, until it posted them to a work Slack channel with the same name.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Slack"
   ],
   "prompt": "Goal: Get a monthly personal-finance review from an agent, safely.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Slack.\nSteps:\n1. Ask the agent: balances, monthly expenses, recurring expenses, anything suspicious, ways to save; “what would you say to me every month as my financial advisor?”.\n2. Give it read-only access to checking and savings, and tell it to message only you.\n3. Run it weekly at first to test.\n4. Lesson: agents can share connections, so a work Slack channel with the same name as your private chat got the report. Use distinct channel names and require explicit permission before cross-channel posts.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Shane Mac (as told to Business Insider) — https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10",
   "steps": [
    "Ask the agent: balances, monthly expenses, recurring expenses, anything suspicious, ways to save; “what would you say to me every month as my financial advisor?”.",
    "Give it read-only access to checking and savings, and tell it to message only you.",
    "Run it weekly at first to test.",
    "Lesson: agents can share connections, so a work Slack channel with the same name as your private chat got the report. Use distinct channel names and require explicit permission before cross-channel posts."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 70.0,
   "sources": [
    {
     "author": "Shane Mac (as told to Business Insider)",
     "handle": "Business Insider",
     "url": "https://www.businessinsider.com/personal-ai-agent-grok-bot-posted-bank-details-company-slack-2026-10",
     "platform": "blog",
     "date": "2026-10-10",
     "primary": true
    },
    {
     "author": "bhrlady",
     "handle": "bhrlady",
     "url": "https://news.ycombinator.com/item?id=50033517",
     "platform": "hn",
     "date": "2026-10-10",
     "primary": false
    }
   ]
  },
  {
   "slug": "grokbot-book-dentist-insurance",
   "url": "https://agentsetups.dev/use-case/grokbot-book-dentist-insurance/",
   "title": "Have Grok Bot book a dentist that takes your insurance",
   "summary": "A Grok Bot found a dentist that accepts the family’s insurance and booked the appointment from its own browser.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "web browser"
   ],
   "prompt": "Goal: Book a medical appointment without phoning around about insurance.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: web browser.\nSteps:\n1. Ask your Grok Bot to search for dentists near you that accept your insurance.\n2. Let it book the appointment from its web browser.\n3. Check the confirmation email and text.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Texas Twins Dad — https://x.com/Texas_Twins_Dad/status/2110562649586983246",
   "steps": [
    "Ask your Grok Bot to search for dentists near you that accept your insurance.",
    "Let it book the appointment from its web browser.",
    "Check the confirmation email and text."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 69.9,
   "sources": [
    {
     "author": "Texas Twins Dad",
     "handle": "@Texas_Twins_Dad",
     "url": "https://x.com/Texas_Twins_Dad/status/2110562649586983246",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "mine-agent-session-logs",
   "url": "https://agentsetups.dev/use-case/mine-agent-session-logs/",
   "title": "Mine hundreds of agent sessions for consequential moments",
   "summary": "A Hermes plugin developer had the agent review 491 sessions for “consequential moments”.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Review my saved agent sessions for useful patterns.\nSetup: agents used in source: Hermes Agent.\nSteps:\n1. Point your agent at your sessions data.\n2. Ask it to review the sessions for “consequential moments”.\n3. Use the patterns to guide the plugins and tools you build.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: mr_r0b0t — https://x.com/mr_r0b0t/status/2109089421203050864 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Point your agent at your sessions data.",
    "Ask it to review the sessions for “consequential moments”.",
    "Use the patterns to guide the plugins and tools you build."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 69.6,
   "sources": [
    {
     "author": "mr_r0b0t",
     "handle": "@mr_r0b0t",
     "url": "https://x.com/mr_r0b0t/status/2109089421203050864",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "codex-drives-real-iphone",
   "url": "https://agentsetups.dev/use-case/codex-drives-real-iphone/",
   "title": "Let Codex operate a real iPhone over USB",
   "summary": "iPhone-use: guided install, app automation, live screen and screenshot fallback for Codex.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Let my agent operate apps on my iPhone.\nSetup: agents used in source: Codex.\nSteps:\n1. Install iPhone-use and connect the iPhone by USB.\n2. Let Codex automate the app via the live screen.\n3. Fall back to screenshots when needed.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: zhongerxin — https://github.com/zhongerxin/iPhone-use (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install iPhone-use and connect the iPhone by USB.",
    "Let Codex automate the app via the live screen.",
    "Fall back to screenshots when needed."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 69.1,
   "sources": [
    {
     "author": "zhongerxin",
     "handle": "zhongerxin",
     "url": "https://github.com/zhongerxin/iPhone-use",
     "platform": "github",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "archive-search-dodo-discovery",
   "url": "https://agentsetups.dev/use-case/archive-search-dodo-discovery/",
   "title": "Find unknown sources in a historical archive",
   "summary": "A historian embedded the VOC archive, used semantic search plus Opus 5.5 ranking, and found a 1615 dodo hunting report.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "GLOBALISE archive",
    "embedding model"
   ],
   "prompt": "Goal: Use agents to surface overlooked primary sources for a research question.\nSetup: agents used in source: Claude; tools/MCPs stated: GLOBALISE archive, embedding model.\nSteps:\n1. Start from your own specialist knowledge to define a specific research question.\n2. Pick a large, free, well-edited corpus (here the GLOBALISE Dutch East India Company archive).\n3. Download it and run it through an embedding model for semantic search.\n4. Surface candidate passages; have frontier models read them and rank the best matches for human review.\n5. Iterate on promising passages, or try new archives and terms. Give the agent an API key so it can run its own embedding searches on new sources.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Benjamin Breen — https://resobscura.substack.com/p/using-opus-55-to-discover-a-new-eyewitness",
   "steps": [
    "Start from your own specialist knowledge to define a specific research question.",
    "Pick a large, free, well-edited corpus (here the GLOBALISE Dutch East India Company archive).",
    "Download it and run it through an embedding model for semantic search.",
    "Surface candidate passages; have frontier models read them and rank the best matches for human review.",
    "Iterate on promising passages, or try new archives and terms. Give the agent an API key so it can run its own embedding searches on new sources."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 69.0,
   "sources": [
    {
     "author": "Benjamin Breen",
     "handle": "Res Obscura",
     "url": "https://resobscura.substack.com/p/using-opus-55-to-discover-a-new-eyewitness",
     "platform": "blog",
     "date": "2026-10-01",
     "primary": true
    },
    {
     "author": "benbreen",
     "handle": "benbreen",
     "url": "https://news.ycombinator.com/item?id=49926917",
     "platform": "hn",
     "date": "2026-10-01",
     "primary": false
    }
   ]
  },
  {
   "slug": "bookkeeping-for-accountant",
   "url": "https://agentsetups.dev/use-case/bookkeeping-for-accountant/",
   "title": "Prepare your books for the accountant with computer use",
   "summary": "Codex matched every transaction to an invoice across subscriptions and API top-ups, then built a summary site.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-6.1 Sol"
   ],
   "tools": [
    "Google Drive",
    "QuickBooks Online"
   ],
   "prompt": "Goal: Match every transaction to its receipt and prepare everything for my accountant.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Google Drive, QuickBooks Online.\nSteps:\n1. Collect the receipts for subscriptions and API credit top-ups.\n2. Give the agent bank and payment-processor access. The source used API keys and browser sessions; think hard before sharing credentials.\n3. Match every transaction to its invoice.\n4. Produce a summary for the accountant, with the files in Google Drive.\n5. Variant: connect QuickBooks Online through an app created in the QuickBooks developer portal (~20 min).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Machina — https://x.com/EXM7777/status/2106022667694612530",
   "steps": [
    "Collect the receipts for subscriptions and API credit top-ups.",
    "Give the agent bank and payment-processor access. The source used API keys and browser sessions; think hard before sharing credentials.",
    "Match every transaction to its invoice.",
    "Produce a summary for the accountant, with the files in Google Drive.",
    "Variant: connect QuickBooks Online through an app created in the QuickBooks developer portal (~20 min)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 68.6,
   "sources": [
    {
     "author": "Machina",
     "handle": "@EXM7777",
     "url": "https://x.com/EXM7777/status/2106022667694612530",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    },
    {
     "author": "Fil",
     "handle": "@BallinFil",
     "url": "https://x.com/BallinFil/status/2106789537653694771",
     "platform": "x",
     "date": "2026-10-04",
     "primary": false
    }
   ]
  },
  {
   "slug": "clone-app-replica-skills",
   "url": "https://agentsetups.dev/use-case/clone-app-replica-skills/",
   "title": "Clone an app and fix what its users hate",
   "summary": "Eleven free Claude skills: reverse-engineer an app, rebuild it, test for bugs, then fix user complaints.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Rebuild an app and improve on its weak points.\nSetup: agents used in source: Claude.\nSteps:\n1. Reverse-engineer the target app.\n2. Rebuild it.\n3. Test it for bugs.\n4. Fix what its users complain about.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jakeschincariol — https://github.com/Jakeschincariol/replica-skill (summarised from source; the source has no explicit step list)",
   "steps": [
    "Reverse-engineer the target app.",
    "Rebuild it.",
    "Test it for bugs.",
    "Fix what its users complain about."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 67.8,
   "sources": [
    {
     "author": "Jakeschincariol",
     "handle": "Jakeschincariol",
     "url": "https://github.com/Jakeschincariol/replica-skill",
     "platform": "github",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-long-tail-keywords",
   "url": "https://agentsetups.dev/use-case/n8n-long-tail-keywords/",
   "title": "Automate long-tail keyword research",
   "summary": "n8n + Airtable + YepAPI expand a seed keyword into related searches, autocomplete ideas and SEO metrics.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n",
    "Airtable",
    "YepAPI"
   ],
   "prompt": "Goal: Turn a seed keyword into a researched list of long-tail keywords.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n, Airtable, YepAPI.\nSteps:\n1. Start from a seed keyword.\n2. Explore related searches and autocomplete suggestions.\n3. Collect SEO metrics and store results in Airtable.\n4. Related: generate an ICP first (Gemini + Perplexity) so keywords match who you’re writing for.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/cuebicai — https://www.reddit.com/r/n8n/comments/1x2yb1l/i_got_tired_of_researching_keywords_manually_so_i/",
   "steps": [
    "Start from a seed keyword.",
    "Explore related searches and autocomplete suggestions.",
    "Collect SEO metrics and store results in Airtable.",
    "Related: generate an ICP first (Gemini + Perplexity) so keywords match who you’re writing for."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 66.6,
   "sources": [
    {
     "author": "/u/cuebicai",
     "handle": "/u/cuebicai",
     "url": "https://www.reddit.com/r/n8n/comments/1x2yb1l/i_got_tired_of_researching_keywords_manually_so_i/",
     "platform": "reddit",
     "date": "2026-10-11",
     "primary": true
    },
    {
     "author": "/u/cuebicai",
     "handle": "/u/cuebicai",
     "url": "https://www.reddit.com/r/n8n/comments/1wwe6ig/what_if_you_could_automatically_research_a/",
     "platform": "reddit",
     "date": "2026-10-03",
     "primary": false
    }
   ]
  },
  {
   "slug": "lego-model-generator-agents",
   "url": "https://agentsetups.dev/use-case/lego-model-generator-agents/",
   "title": "Have agents design buildable LEGO models",
   "summary": "Agents write Python that generates LDraw, not raw geometry; outputs include 3D/VR views and Blender-editable glTF.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5",
    "GPT-6 Astra"
   ],
   "tools": [
    "LDraw",
    "Docker",
    "Blender"
   ],
   "prompt": "Goal: Get an agent to design physical builds that are actually buildable.\nSetup: agents used in source: Claude; tools/MCPs stated: LDraw, Docker, Blender.\nSteps:\n1. Don’t ask agents to do geometry maths directly; give them Python tooling that generates LDraw sources.\n2. Let them learn from Python code that produces models, not from the models themselves.\n3. Run the open-source app in Docker (clone ldraw-nova and ldraw-nova-docker at the same tag, docker compose build, up -d).\n4. Guide the agent; export 3D/VR views and a Blender glTF.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: antelocnova — https://news.ycombinator.com/item?id=49937916",
   "steps": [
    "Don’t ask agents to do geometry maths directly; give them Python tooling that generates LDraw sources.",
    "Let them learn from Python code that produces models, not from the models themselves.",
    "Run the open-source app in Docker (clone ldraw-nova and ldraw-nova-docker at the same tag, docker compose build, up -d).",
    "Guide the agent; export 3D/VR views and a Blender glTF."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 65.8,
   "sources": [
    {
     "author": "antelocnova",
     "handle": "antelocnova",
     "url": "https://news.ycombinator.com/item?id=49937916",
     "platform": "hn",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "switch-accessible-hub",
   "url": "https://agentsetups.dev/use-case/switch-accessible-hub/",
   "title": "Build a switch-accessible hub for a nonspeaking brother",
   "summary": "A non-programmer built keyboards, phrase boards, texting, streaming pickers and games for his brother.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "VS Code"
   ],
   "prompt": "Goal: Build accessible tools and games for someone who uses switch access.\nSetup: agents used in source: Claude; tools/MCPs stated: VS Code.\nSteps:\n1. Use Claude as a thought partner to plan games and write GDDs and spec sheets before building.\n2. Build in VS Code with the Claude Code extension: describe what the person needs; let it write the code.\n3. Start with a keyboard and phrase boards, then texting, web search, show/movie picking and games.\n4. Test with the person and iterate.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/acrolicious — https://www.reddit.com/r/ClaudeAI/comments/1x0x5wo/my_brother_went_nearly_10_years_without_a_way_to/",
   "steps": [
    "Use Claude as a thought partner to plan games and write GDDs and spec sheets before building.",
    "Build in VS Code with the Claude Code extension: describe what the person needs; let it write the code.",
    "Start with a keyboard and phrase boards, then texting, web search, show/movie picking and games.",
    "Test with the person and iterate."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 65.4,
   "sources": [
    {
     "author": "/u/acrolicious",
     "handle": "/u/acrolicious",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1x0x5wo/my_brother_went_nearly_10_years_without_a_way_to/",
     "platform": "reddit",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "do-comments-help-agents",
   "url": "https://agentsetups.dev/use-case/do-comments-help-agents/",
   "title": "Test whether code comments help your agent",
   "summary": "Deleting 168k lines of comments: same scores, ~22% fewer tokens on a small task, three runs per branch.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Measure whether comments in my codebase help or hurt my agent.\nSetup: agents used in source: Claude.\nSteps:\n1. Make a copy of the codebase with every comment removed.\n2. Ask the agent to build the same features on both versions, three times each.\n3. Score with lint, type checks, existing tests and a hidden test; compare tokens and cost.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: openstation.blog — https://openstation.blog/2026/10/13/i-deleted-168000-lines-of-comments-my-ai-agent-didnt-notice/",
   "steps": [
    "Make a copy of the codebase with every comment removed.",
    "Ask the agent to build the same features on both versions, three times each.",
    "Score with lint, type checks, existing tests and a hidden test; compare tokens and cost."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 63.3,
   "sources": [
    {
     "author": "openstation.blog",
     "handle": "openstation.blog",
     "url": "https://openstation.blog/2026/10/13/i-deleted-168000-lines-of-comments-my-ai-agent-didnt-notice/",
     "platform": "blog",
     "date": "2026-10-13",
     "primary": true
    },
    {
     "author": "epeicher",
     "handle": "epeicher",
     "url": "https://news.ycombinator.com/item?id=50090484",
     "platform": "hn",
     "date": "2026-10-14",
     "primary": false
    }
   ]
  },
  {
   "slug": "llm-council-design-review",
   "url": "https://agentsetups.dev/use-case/llm-council-design-review/",
   "title": "Rank models with a blind LLM design-review council",
   "summary": "A Sonnet 5 “president” has Codex and Claude Code members review, blind-rate each other and aggregate votes.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "GPT-6.1 Sol",
    "GPT-6 Astra",
    "Opus",
    "Fable 5.1",
    "Sonnet 5"
   ],
   "tools": [
    "orca"
   ],
   "prompt": "Goal: Find out which model actually does my design reviews best.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: orca.\nSteps:\n1. Build a council with an orchestrator (here orca’s built-in one).\n2. Use a Sonnet 5 “president” agent to trigger members (Codex and Claude Code models) on the same review task.\n3. Have members rate each other’s work blind.\n4. Aggregate the votes; repeat across several runs before concluding.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: jinjingliang — https://x.com/JinjingLiang/status/2107537480945942954",
   "steps": [
    "Build a council with an orchestrator (here orca’s built-in one).",
    "Use a Sonnet 5 “president” agent to trigger members (Codex and Claude Code models) on the same review task.",
    "Have members rate each other’s work blind.",
    "Aggregate the votes; repeat across several runs before concluding."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 63.2,
   "sources": [
    {
     "author": "jinjingliang",
     "handle": "@JinjingLiang",
     "url": "https://x.com/JinjingLiang/status/2107537480945942954",
     "platform": "x",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "one-prompt-playable-game",
   "url": "https://agentsetups.dev/use-case/one-prompt-playable-game/",
   "title": "Build and publish a playable game from one prompt",
   "summary": "Manus 2.0 built a 3D world, combat, soundtrack and SFX, then playtested and published “Echo Isle”.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Manus"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Build a playable game from one idea.\nSetup: agents used in source: Manus.\nSteps:\n1. Give one idea (e.g. “an open-world game where music is your weapon”).\n2. Have it build the world, characters, combat, soundtrack and SFX.\n3. Have it playtest and publish.\n4. Variant: Claude Code recreated a film scene in three.js, generating textures/SFX/music and self-verifying with screenshots.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Min Choi — https://x.com/minchoi/status/2109669169234944325",
   "steps": [
    "Give one idea (e.g. “an open-world game where music is your weapon”).",
    "Have it build the world, characters, combat, soundtrack and SFX.",
    "Have it playtest and publish.",
    "Variant: Claude Code recreated a film scene in three.js, generating textures/SFX/music and self-verifying with screenshots."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 62.7,
   "sources": [
    {
     "author": "Min Choi",
     "handle": "@minchoi",
     "url": "https://x.com/minchoi/status/2109669169234944325",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "one-prompt-motion-video",
   "url": "https://agentsetups.dev/use-case/one-prompt-motion-video/",
   "title": "Make a 30-second motion-graphics video from one prompt",
   "summary": "One Claude Code prompt rendered a 1080p60 three.js video in 26 min for $6.74; others render particles in headless Chromium.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [
    "Sonnet 5.5",
    "Opus 5.5"
   ],
   "tools": [
    "three.js",
    "headless Chromium"
   ],
   "prompt": "Goal: Make a motion-graphics video in code.\nSetup: agents used in source: Claude; tools/MCPs stated: three.js, headless Chromium.\nSteps:\n1. Prompt: “make a dynamic 30-second motion graphics video about <product>. not too fast, people should actually understand what it’s about. use three.js”.\n2. Let it render frames (another author rendered 900 frames in headless Chromium on CPU).\n3. Or point Claude Code at a launch video you like and have it build your own version.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Artem — https://x.com/sl1ma4/status/2105592053874700360",
   "steps": [
    "Prompt: “make a dynamic 30-second motion graphics video about <product>. not too fast, people should actually understand what it’s about. use three.js”.",
    "Let it render frames (another author rendered 900 frames in headless Chromium on CPU).",
    "Or point Claude Code at a launch video you like and have it build your own version."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 62.1,
   "sources": [
    {
     "author": "Artem",
     "handle": "@sl1ma4",
     "url": "https://x.com/sl1ma4/status/2105592053874700360",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    },
    {
     "author": "qibaz",
     "handle": "@QibazX",
     "url": "https://x.com/QibazX/status/2106116277936787516",
     "platform": "x",
     "date": "2026-10-02",
     "primary": false
    },
    {
     "author": "LN",
     "handle": "@ln_dev7",
     "url": "https://x.com/ln_dev7/status/2105357508684415159",
     "platform": "x",
     "date": "2026-09-30",
     "primary": false
    }
   ]
  },
  {
   "slug": "simcity-clone-ghidra-subagents",
   "url": "https://agentsetups.dev/use-case/simcity-clone-ghidra-subagents/",
   "title": "Clone a classic game by decompiling it with subagents",
   "summary": "Opus 5.5 decompiled SimCity 2000 with Ghidra using 27 subagents, then verified 10,000 game days via a Unicorn emulator.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Ghidra",
    "Unicorn",
    "GPT Image 2"
   ],
   "prompt": "Goal: Build a faithful modern replica of an old game from its original binary.\nSetup: agents used in source: Claude; tools/MCPs stated: Ghidra, Unicorn, GPT Image 2.\nSteps:\n1. Prompt: “create a typescript webgl low-poly version (full replica of game logic) of <game>. the original is available here for inspection”.\n2. Let it decompile with Ghidra and translate native code function by function using subagents.\n3. Follow up: “make sure all aspects of the game is implemented correctly and accurately” — it built an emulator harness to compare game state over 10,000 days.\n4. Polish; generate 3D/vector assets in code and bitmaps with an image model.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: drdator — https://news.ycombinator.com/item?id=49977886",
   "steps": [
    "Prompt: “create a typescript webgl low-poly version (full replica of game logic) of <game>. the original is available here for inspection”.",
    "Let it decompile with Ghidra and translate native code function by function using subagents.",
    "Follow up: “make sure all aspects of the game is implemented correctly and accurately” — it built an emulator harness to compare game state over 10,000 days.",
    "Polish; generate 3D/vector assets in code and bitmaps with an image model."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 61.0,
   "sources": [
    {
     "author": "drdator",
     "handle": "drdator",
     "url": "https://news.ycombinator.com/item?id=49977886",
     "platform": "hn",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "xp-agent-skills-pack",
   "url": "https://agentsetups.dev/use-case/xp-agent-skills-pack/",
   "title": "Adopt 22 daily-driver engineering skills",
   "summary": "Open-source skills for TDD, review, debugging, refactoring, security, Docker, worktrees and subagent orchestration.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Set up skills that keep changes simple, small and verified.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Install the skills for TDD, code review, debugging, refactoring, legacy code, testing, security, Docker, worktrees and repo cleanup.\n2. Use the orchestration skills: split parallel work, pick the right agent, give it a clear mission, verify, integrate.\n3. Keep only the skills that survive daily use.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Rafael Bittencourt — https://x.com/rafaelobitten/status/2107098718033871285",
   "steps": [
    "Install the skills for TDD, code review, debugging, refactoring, legacy code, testing, security, Docker, worktrees and repo cleanup.",
    "Use the orchestration skills: split parallel work, pick the right agent, give it a clear mission, verify, integrate.",
    "Keep only the skills that survive daily use."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 61.0,
   "sources": [
    {
     "author": "Rafael Bittencourt",
     "handle": "@rafaelobitten",
     "url": "https://x.com/rafaelobitten/status/2107098718033871285",
     "platform": "x",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "compare-models-on-real-task",
   "url": "https://agentsetups.dev/use-case/compare-models-on-real-task/",
   "title": "Benchmark model/reasoning combos on your real task",
   "summary": "16 combinations across ChatGPT Plus, Claude Pro and Google AI Pro on one Unity investigation: 1–20% allowance.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Unity"
   ],
   "prompt": "Goal: Find which model and reasoning mode gives the most useful work per subscription.\nSetup: agents used in source: Claude; tools/MCPs stated: Unity.\nSteps:\n1. Pick one real task from your project as the benchmark.\n2. Run it on each model/reasoning combination.\n3. Record allowance used and quality of result.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/AlexXx52 — https://www.reddit.com/r/ChatGPTCoding/comments/1x1jbry/i_tested_16_ai_modelreasoning_combinations_on_the/",
   "steps": [
    "Pick one real task from your project as the benchmark.",
    "Run it on each model/reasoning combination.",
    "Record allowance used and quality of result."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 60.9,
   "sources": [
    {
     "author": "/u/AlexXx52",
     "handle": "/u/AlexXx52",
     "url": "https://www.reddit.com/r/ChatGPTCoding/comments/1x1jbry/i_tested_16_ai_modelreasoning_combinations_on_the/",
     "platform": "reddit",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "personal-whisper-app",
   "url": "https://agentsetups.dev/use-case/personal-whisper-app/",
   "title": "Build your own transcription app for your workflow",
   "summary": "A YouTuber replaced terminal faster-whisper with a Claude Code-built app; transcripts feed video descriptions.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "faster-whisper"
   ],
   "prompt": "Goal: Build a desktop transcription app for my videos.\nSetup: agents used in source: Claude; tools/MCPs stated: faster-whisper.\nSteps:\n1. Describe the workflow you use today (e.g. running faster-whisper in a terminal).\n2. Have Claude Code build an app around it and test it in the background.\n3. Feed transcripts into AI to generate video descriptions.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/AcrillixOfficial — https://www.reddit.com/r/ClaudeAI/comments/1wx7nnw/claude_has_enabled_me_to_make_apps_for_personal/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Describe the workflow you use today (e.g. running faster-whisper in a terminal).",
    "Have Claude Code build an app around it and test it in the background.",
    "Feed transcripts into AI to generate video descriptions."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 59.6,
   "sources": [
    {
     "author": "/u/AcrillixOfficial",
     "handle": "/u/AcrillixOfficial",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wx7nnw/claude_has_enabled_me_to_make_apps_for_personal/",
     "platform": "reddit",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-relay-slack-for-you",
   "url": "https://agentsetups.dev/use-case/dots-relay-slack-for-you/",
   "title": "Let your Dot post updates to Slack and bring replies back",
   "summary": "At Every, @danshipper’s Dot posted his model-testing results to Slack and relayed the replies, so he never opened Slack.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "Slack"
   ],
   "prompt": "Goal: Protect my attention: have my Dot handle Slack back-and-forth while I keep working.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Slack.\nSteps:\n1. Connect Slack to your Dot.\n2. Ask it to post your results or update in the right channel.\n3. Have it collect the replies and bring them back to you in ChatGPT, so you don’t open Slack.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dan Shipper — https://x.com/danshipper/status/2107890633486582208 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Connect Slack to your Dot.",
    "Ask it to post your results or update in the right channel.",
    "Have it collect the replies and bring them back to you in ChatGPT, so you don’t open Slack."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 56.6,
   "sources": [
    {
     "author": "Dan Shipper",
     "handle": "@danshipper",
     "url": "https://x.com/danshipper/status/2107890633486582208",
     "platform": "x",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-job-search-pipeline",
   "url": "https://agentsetups.dev/use-case/cowork-job-search-pipeline/",
   "title": "Run a job search on Cowork scheduled tasks",
   "summary": "Apps Script scrapes ~9,000 career pages; Cowork matches roles, keeps an interview tracker from Gmail and drafts follow-ups. 3 offers.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Google Sheets",
    "Apps Script",
    "Gmail",
    "Claude in Chrome"
   ],
   "prompt": "Goal: Stay early on new roles while keeping applications personal.\nSetup: agents used in source: Claude; tools/MCPs stated: Google Sheets, Apps Script, Gmail, Claude in Chrome.\nSteps:\n1. Scrape career pages with Apps Script inside the sheet, not with the agent.\n2. Have Cowork match new roles, open the best ones in tabs each morning, and keep an interview tracker current from Gmail and calendar.\n3. Have it draft a recruiter follow-up after each application and save it to Gmail for review.\n4. When writing into Sheets via Claude in Chrome: plain text only, map columns by header name.\n5. Keep each automation as a markdown skill file; when it breaks, give Claude the file and the error to fix it.\n6. Do the applications yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Lovamelin — https://www.reddit.com/r/ClaudeCowork/comments/1x557lz/my_job_search_ran_on_cowork_scheduled_tasks_for/",
   "steps": [
    "Scrape career pages with Apps Script inside the sheet, not with the agent.",
    "Have Cowork match new roles, open the best ones in tabs each morning, and keep an interview tracker current from Gmail and calendar.",
    "Have it draft a recruiter follow-up after each application and save it to Gmail for review.",
    "When writing into Sheets via Claude in Chrome: plain text only, map columns by header name.",
    "Keep each automation as a markdown skill file; when it breaks, give Claude the file and the error to fix it.",
    "Do the applications yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 56.5,
   "sources": [
    {
     "author": "/u/Lovamelin",
     "handle": "/u/Lovamelin",
     "url": "https://www.reddit.com/r/ClaudeCowork/comments/1x557lz/my_job_search_ran_on_cowork_scheduled_tasks_for/",
     "platform": "reddit",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "pi-extensions-council-voice",
   "url": "https://agentsetups.dev/use-case/pi-extensions-council-voice/",
   "title": "Extend Pi with council, voice and TTS extensions",
   "summary": "Community Pi extensions: /council asks several models in parallel, local voice input, Turkish TTS.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Pi"
   ],
   "models": [
    "Opus 5.5",
    "GPT-6 Astra"
   ],
   "tools": [
    "pi-voice"
   ],
   "prompt": "Goal: Add useful extensions to my Pi agent.\nSetup: agents used in source: Pi; tools/MCPs stated: pi-voice.\nSteps:\n1. Install Pi Agent Council and use /council to compare advice from several models side by side.\n2. Install pi-voice (pi install npm:@earendil-works/pi-voice) for local speech-to-text.\n3. Optionally add a TTS extension that reads only text inside <tts> tags.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Melvin Vivas — https://x.com/melvindvivas/status/2105645508186570807",
   "steps": [
    "Install Pi Agent Council and use /council to compare advice from several models side by side.",
    "Install pi-voice (pi install npm:@earendil-works/pi-voice) for local speech-to-text.",
    "Optionally add a TTS extension that reads only text inside <tts> tags."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 54.8,
   "sources": [
    {
     "author": "Melvin Vivas",
     "handle": "@melvindvivas",
     "url": "https://x.com/melvindvivas/status/2105645508186570807",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    },
    {
     "author": "Swarogan",
     "handle": "@swarogan",
     "url": "https://x.com/swarogan/status/2104530944061309040",
     "platform": "x",
     "date": "2026-09-28",
     "primary": false
    },
    {
     "author": "Ilker",
     "handle": "@ilkerulusoy",
     "url": "https://x.com/ilkerulusoy/status/2107853780481917156",
     "platform": "x",
     "date": "2026-10-07",
     "primary": false
    }
   ]
  },
  {
   "slug": "hermes-copy-muse-memory-setup",
   "url": "https://agentsetups.dev/use-case/hermes-copy-muse-memory-setup/",
   "title": "Give your Hermes agent Muse-style memory",
   "summary": "A Hermes user copied Muse’s memory design (daily logs, derived memory stores, nightly “dreaming”) and got much better weekly reflections.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Hermes Agent",
    "Meta Muse"
   ],
   "models": [],
   "tools": [
    "markdown memory files"
   ],
   "prompt": "Goal: Get a life-management agent to spot patterns, not just recap my week.\nSetup: agents used in source: Hermes Agent, Meta Muse; tools/MCPs stated: markdown memory files.\nSteps:\n1. Have the agent write a daily memory log as a markdown file.\n2. Keep derived memory stores about the concepts that matter to you.\n3. Add a nightly “dream” job that synthesises the day’s logs into those stores.\n4. Run weekly and monthly reflections on top of that memory and compare them with what you got before.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/normVectorsNotHate — https://www.reddit.com/r/hermesagent/comments/1wxu98g/i_copied_muses_memory_setup_for_my_own_hermes/",
   "steps": [
    "Have the agent write a daily memory log as a markdown file.",
    "Keep derived memory stores about the concepts that matter to you.",
    "Add a nightly “dream” job that synthesises the day’s logs into those stores.",
    "Run weekly and monthly reflections on top of that memory and compare them with what you got before."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 53.9,
   "sources": [
    {
     "author": "/u/normVectorsNotHate",
     "handle": "/u/normVectorsNotHate",
     "url": "https://www.reddit.com/r/hermesagent/comments/1wxu98g/i_copied_muses_memory_setup_for_my_own_hermes/",
     "platform": "reddit",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-inbox-triage-hill-climb",
   "url": "https://agentsetups.dev/use-case/muse-inbox-triage-hill-climb/",
   "title": "Let Muse tune its own inbox-triage model",
   "summary": "@OmarShahine’s Muse triages email via a decision model; it hill-climbed a cheaper model from 52% to 88% on his labels.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Meta Muse"
   ],
   "models": [
    "Jev",
    "Decision-1"
   ],
   "tools": [
    "OpenRouter"
   ],
   "prompt": "Goal: Have my Muse triage my inbox daily with a cheap model it tunes itself.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: OpenRouter.\nSteps:\n1. Give Muse a decision model through OpenRouter for daily inbox triage.\n2. Label a set of your emails as ground truth.\n3. Ask Muse to hill-climb a cheaper model against those labels until it beats the current one, then switch.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Omar Shahine — https://x.com/OmarShahine/status/2109402421185167491",
   "steps": [
    "Give Muse a decision model through OpenRouter for daily inbox triage.",
    "Label a set of your emails as ground truth.",
    "Ask Muse to hill-climb a cheaper model against those labels until it beats the current one, then switch."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 53.6,
   "sources": [
    {
     "author": "Omar Shahine",
     "handle": "@OmarShahine",
     "url": "https://x.com/OmarShahine/status/2109402421185167491",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-home-inventory-insurance",
   "url": "https://agentsetups.dev/use-case/grokbot-home-inventory-insurance/",
   "title": "Inventory your belongings for insurance with Grok Bot",
   "summary": "Use Grok Bot to build an inventory of your important stuff, with the details insurers ask for: what it was, brand and more.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Have a list of what I own in case of flood, fire or burglary.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Photograph your important belongings.\n2. Have Grok Bot build an inventory from them with the details insurers want (item, brand, …).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Brian Roemmele — https://x.com/BrianRoemmele/status/2110580579628650928 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Photograph your important belongings.",
    "Have Grok Bot build an inventory from them with the details insurers want (item, brand, …)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 52.6,
   "sources": [
    {
     "author": "Brian Roemmele",
     "handle": "@BrianRoemmele",
     "url": "https://x.com/BrianRoemmele/status/2110580579628650928",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-agent-on-iphone",
   "url": "https://agentsetups.dev/use-case/hermes-agent-on-iphone/",
   "title": "Run a Hermes agent on your phone, no server",
   "summary": "A Hermes agent living on the phone thinks in the Dynamic Island, asks before risky commands and builds 3D apps.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Carry a personal agent on my phone without a laptop or server.\nSetup: agents used in source: Hermes Agent.\nSteps:\n1. Run Hermes Agent on the phone itself.\n2. Have it ask before running risky commands.\n3. Use it to build live 3D apps and Canvas, and to remember what you tell it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mark Keeper — https://x.com/markkeeper2/status/2106873833978540280 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Run Hermes Agent on the phone itself.",
    "Have it ask before running risky commands.",
    "Use it to build live 3D apps and Canvas, and to remember what you tell it."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 51.9,
   "sources": [
    {
     "author": "Mark Keeper",
     "handle": "@markkeeper2",
     "url": "https://x.com/markkeeper2/status/2106873833978540280",
     "platform": "x",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-build-personal-chatgpt-apps",
   "url": "https://agentsetups.dev/use-case/dots-build-personal-chatgpt-apps/",
   "title": "Build personal ChatGPT apps with your Dot",
   "summary": "@_simonsmith’s Dot built a news app and a Spanish vocab app: Sites MCP server backend, plugin-with-extensions front end.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Meta Muse",
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "ChatGPT Sites",
    "MCP"
   ],
   "prompt": "Goal: Have my Dot build a small personal app that runs inside ChatGPT.\nSetup: agents used in source: Claude, Meta Muse, ChatGPT Dots; tools/MCPs stated: ChatGPT Sites, MCP.\nSteps:\n1. Ask the Dot to build the backend as an MCP server hosted on ChatGPT Sites.\n2. Have it build the front end as a ChatGPT plugin with extensions.\n3. Start with one app (e.g. a personalised news feed with thumbs up/down), then iterate on the rough edges.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Simon Smith — https://x.com/_simonsmith/status/2110425007059017830 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask the Dot to build the backend as an MCP server hosted on ChatGPT Sites.",
    "Have it build the front end as a ChatGPT plugin with extensions.",
    "Start with one app (e.g. a personalised news feed with thumbs up/down), then iterate on the rough edges."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 51.6,
   "sources": [
    {
     "author": "Simon Smith",
     "handle": "@_simonsmith",
     "url": "https://x.com/_simonsmith/status/2110425007059017830",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    },
    {
     "author": "Simon Smith",
     "handle": "@_simonsmith",
     "url": "https://x.com/_simonsmith/status/2108672854460072099",
     "platform": "x",
     "date": "2026-10-09",
     "primary": false
    },
    {
     "author": "Simon Smith",
     "handle": "@_simonsmith",
     "url": "https://x.com/_simonsmith/status/2108622812474683426",
     "platform": "x",
     "date": "2026-10-09",
     "primary": false
    }
   ]
  },
  {
   "slug": "ai-agent-on-feature-phone",
   "url": "https://agentsetups.dev/use-case/ai-agent-on-feature-phone/",
   "title": "Put an AI agent on a Nokia feature phone",
   "summary": "With Codex’s help, a dev reverse-engineered Nokia 110 4G firmware; a chat app runs from RAM and can call, set alarms and toggle the torch.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "DeepSeek API"
   ],
   "prompt": "Goal: Run an agent with native phone functions on a basic phone.\nSetup: agents used in source: Codex; tools/MCPs stated: DeepSeek API.\nSteps:\n1. Study the firmware and boot process; get custom code running in RAM through an existing app entry point (Calculator) without flashing.\n2. Turn it into a chat app that sends messages to a model API and maps tool calls to phone functions: answer questions, battery, torch, call, alarm.\n3. Trace the firmware’s response callbacks when requests go out but answers don’t come back.\n4. Use a coding agent (here Codex) to help build; test on the handset.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: anupray — https://news.ycombinator.com/item?id=50006114",
   "steps": [
    "Study the firmware and boot process; get custom code running in RAM through an existing app entry point (Calculator) without flashing.",
    "Turn it into a chat app that sends messages to a model API and maps tool calls to phone functions: answer questions, battery, torch, call, alarm.",
    "Trace the firmware’s response callbacks when requests go out but answers don’t come back.",
    "Use a coding agent (here Codex) to help build; test on the handset."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 50.9,
   "sources": [
    {
     "author": "anupray",
     "handle": "anupray",
     "url": "https://news.ycombinator.com/item?id=50006114",
     "platform": "hn",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "one-shot-ad-codex-suno",
   "url": "https://agentsetups.dev/use-case/one-shot-ad-codex-suno/",
   "title": "One-shot a product ad with Codex and Suno",
   "summary": "Animations, captions, structure in Codex and the song via Suno, done in under 3 hours on a flight.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "Suno"
   ],
   "prompt": "Goal: Make a short product ad entirely with AI.\nSetup: agents used in source: Codex; tools/MCPs stated: Suno.\nSteps:\n1. Generate the song in Suno.\n2. Have Codex build the animations, captions and structure.\n3. Variant: a “remake this video 100% in code” prompt rebuilds a reference video frame by frame and zips code, motion data and assets.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Aaron — https://x.com/aaronmtrx/status/2110400280164721106",
   "steps": [
    "Generate the song in Suno.",
    "Have Codex build the animations, captions and structure.",
    "Variant: a “remake this video 100% in code” prompt rebuilds a reference video frame by frame and zips code, motion data and assets."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 50.9,
   "sources": [
    {
     "author": "Aaron",
     "handle": "@aaronmtrx",
     "url": "https://x.com/aaronmtrx/status/2110400280164721106",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    },
    {
     "author": "Justin Lord",
     "handle": "@Justin_lords",
     "url": "https://x.com/Justin_lords/status/2097729022277173535",
     "platform": "x",
     "date": "2026-09-09",
     "primary": false
    }
   ]
  },
  {
   "slug": "muse-text-on-your-behalf",
   "url": "https://agentsetups.dev/use-case/muse-text-on-your-behalf/",
   "title": "Let your agent text for you, behind an approval gate",
   "summary": "Muse texts via iMessage from an always-on Mac/VM; an approval gate guards every device action.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [
    "iMessage"
   ],
   "prompt": "Goal: Let my agent send iMessages for me, safely.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: iMessage.\nSteps:\n1. Use a computer you can leave on (or iCloud in a VM) and connect it to Muse.\n2. Give the access needed; tell the agent which number belongs to whom.\n3. Set an approval gate for any action on the connected device.\n4. Write ground rules: never spend, send, delete or share details without asking; research only for trades.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: JJ Englert — https://x.com/JJEnglert/status/2109803033362108493",
   "steps": [
    "Use a computer you can leave on (or iCloud in a VM) and connect it to Muse.",
    "Give the access needed; tell the agent which number belongs to whom.",
    "Set an approval gate for any action on the connected device.",
    "Write ground rules: never spend, send, delete or share details without asking; research only for trades."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 49.7,
   "sources": [
    {
     "author": "JJ Englert",
     "handle": "@JJEnglert",
     "url": "https://x.com/JJEnglert/status/2109803033362108493",
     "platform": "x",
     "date": "2026-10-13",
     "primary": true
    },
    {
     "author": "MJ",
     "handle": "@Mj4Stocks",
     "url": "https://x.com/Mj4Stocks/status/2104420369868222758",
     "platform": "x",
     "date": "2026-09-28",
     "primary": false
    }
   ]
  },
  {
   "slug": "agent-auditor-stops-waste",
   "url": "https://agentsetups.dev/use-case/agent-auditor-stops-waste/",
   "title": "Make one agent audit the others for wasted spend",
   "summary": "After agents burned $200 of credits chatting, an auditor agent lists every agent and what it costs.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Act as my agent auditor and find agents that waste money.\nSetup: agents used in source: Claude.\nSteps:\n1. Give one agent the auditor job. In Claude Code the author pastes a prompt that starts “You’re my agent auditor. List every…”.\n2. List every running agent, what it does and what it costs.\n3. Flag agents that talk to each other without producing anything; the author lost $200 of credits this way.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Davidd Tech — https://x.com/DaviddDotTech/status/2109201220766253205 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give one agent the auditor job. In Claude Code the author pastes a prompt that starts “You’re my agent auditor. List every…”.",
    "List every running agent, what it does and what it costs.",
    "Flag agents that talk to each other without producing anything; the author lost $200 of credits this way."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 49.6,
   "sources": [
    {
     "author": "Davidd Tech",
     "handle": "@DaviddDotTech",
     "url": "https://x.com/DaviddDotTech/status/2109201220766253205",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-small-errands-brag-log",
   "url": "https://agentsetups.dev/use-case/dots-small-errands-brag-log/",
   "title": "Use your Dot for email, meetings, coupons and a brag log",
   "summary": "@simpsoka uses her Dot to organise email, book meetings, find coupon codes and keep a weekly log of wins for her boss.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Hand my Dot the small recurring chores.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Ask it to organise your email.\n2. Have it book meetings.\n3. Ask it to find coupon codes before you buy.\n4. Keep a running log of interesting things you did this week to share with your boss.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kath Korevec — https://x.com/simpsoka/status/2106152475439026388",
   "steps": [
    "Ask it to organise your email.",
    "Have it book meetings.",
    "Ask it to find coupon codes before you buy.",
    "Keep a running log of interesting things you did this week to share with your boss."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 49.0,
   "sources": [
    {
     "author": "Kath Korevec",
     "handle": "@simpsoka",
     "url": "https://x.com/simpsoka/status/2106152475439026388",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "manus-analyse-complex-dataset",
   "url": "https://agentsetups.dev/use-case/manus-analyse-complex-dataset/",
   "title": "Point Manus at a complex dataset",
   "summary": "In one reviewer’s test, Manus aggregated and tabulated a complex dataset, explained findings and suggested next lookups.",
   "category": "data-analysis",
   "category_label": "Data analysis",
   "agents": [
    "Manus"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Get a quick analysis of a messy dataset.\nSetup: agents used in source: Manus.\nSteps:\n1. Give Manus the dataset.\n2. Ask it to aggregate, tabulate, explain what it found and suggest what to look up next.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: emelu — https://x.com/emelucrypto/status/2105666507040518362 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give Manus the dataset.",
    "Ask it to aggregate, tabulate, explain what it found and suggest what to look up next."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 48.4,
   "sources": [
    {
     "author": "emelu",
     "handle": "@emelucrypto",
     "url": "https://x.com/emelucrypto/status/2105666507040518362",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-family-school-alerts",
   "url": "https://agentsetups.dev/use-case/dots-family-school-alerts/",
   "title": "Have your Dot surface school and family changes",
   "summary": "With Google connected, @danveloper’s Dot proactively flagged his son’s English assignment and a changed pick-up time.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "Google (Gmail/Calendar)"
   ],
   "prompt": "Goal: Get proactive alerts about family logistics hidden in my email and calendar.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Google (Gmail/Calendar).\nSteps:\n1. Connect your Google account to ChatGPT so the Dot can read mail and calendar.\n2. Let it run proactively; it messages you only about things that matter (assignments, pick-up time changes).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dan Woods — https://x.com/danveloper/status/2106475882877694364 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Connect your Google account to ChatGPT so the Dot can read mail and calendar.",
    "Let it run proactively; it messages you only about things that matter (assignments, pick-up time changes)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 48.2,
   "sources": [
    {
     "author": "Dan Woods",
     "handle": "@danveloper",
     "url": "https://x.com/danveloper/status/2106475882877694364",
     "platform": "x",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "docs-crawler-mcp-for-agents",
   "url": "https://agentsetups.dev/use-case/docs-crawler-mcp-for-agents/",
   "title": "Give agents a crawler that saves docs as Markdown",
   "summary": "pulpie-mcp saved 60 doc pages as clean Markdown in ~49s with a local 210M model, writing files instead of flooding context.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "pulpie-orange-small"
   ],
   "tools": [
    "pulpie-mcp",
    "uv"
   ],
   "prompt": "Goal: Let my coding agents pull full documentation sites into local Markdown.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: pulpie-mcp, uv.\nSteps:\n1. Install: uv tool install git+https://github.com/pinkpixel-dev/pulpie-mcp\n2. Add to Claude Code: claude mcp add --scope user pulpie -- pulpie-mcp (or add it to ~/.codex/config.toml for Codex).\n3. Ask the agent to crawl_docs a documentation site; it checks robots.txt and sitemaps first.\n4. Pages are saved to files and only a summary returns, so the agent searches and reads them when needed.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jessica Doering — https://dev.to/sizzlebop/i-gave-my-ai-agents-their-own-documentation-crawler-and-pulled-60-pages-of-clean-markdown-in-49-2cl7",
   "steps": [
    "Install: uv tool install git+https://github.com/pinkpixel-dev/pulpie-mcp",
    "Add to Claude Code: claude mcp add --scope user pulpie -- pulpie-mcp (or add it to ~/.codex/config.toml for Codex).",
    "Ask the agent to crawl_docs a documentation site; it checks robots.txt and sitemaps first.",
    "Pages are saved to files and only a summary returns, so the agent searches and reads them when needed."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 48.0,
   "sources": [
    {
     "author": "Jessica Doering",
     "handle": "@sizzlebop",
     "url": "https://dev.to/sizzlebop/i-gave-my-ai-agents-their-own-documentation-crawler-and-pulled-60-pages-of-clean-markdown-in-49-2cl7",
     "platform": "devto",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "runlevel-state-survive-compaction",
   "url": "https://agentsetups.dev/use-case/runlevel-state-survive-compaction/",
   "title": "Keep agent state in init.d-style files to survive compaction",
   "summary": "Instead of one PROGRESS.md, ordered runlevel-style state files plus fork/wait subagents survived two 230k-token compactions.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Cursor",
    "Gemini CLI",
    "Antigravity"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Stop long agent sessions from losing their place after context compaction.\nSetup: agents used in source: Claude, Cursor, Gemini CLI, Antigravity.\nSteps:\n1. Don’t trust the auto-summary after compaction; keep state on disk.\n2. Avoid a single TODO.md/PROGRESS.md scratchpad; it gets stale or overwritten.\n3. Use ordered, lexically numbered state files per step, like SysV /etc/init.d runlevels, that the agent re-reads to resume.\n4. Push heavy work into forked subagents and wait on results, so the main context stays small.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Randal L. Schwartz — https://dev.to/gde/surviving-the-200k-token-lobotomy-how-unix-initd-and-memento-made-my-ai-coding-agent-immune-to-2f74 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Don’t trust the auto-summary after compaction; keep state on disk.",
    "Avoid a single TODO.md/PROGRESS.md scratchpad; it gets stale or overwritten.",
    "Use ordered, lexically numbered state files per step, like SysV /etc/init.d runlevels, that the agent re-reads to resume.",
    "Push heavy work into forked subagents and wait on results, so the main context stays small."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 48.0,
   "sources": [
    {
     "author": "Randal L. Schwartz",
     "handle": "@randalschwartz",
     "url": "https://dev.to/gde/surviving-the-200k-token-lobotomy-how-unix-initd-and-memento-made-my-ai-coding-agent-immune-to-2f74",
     "platform": "devto",
     "date": "2026-10-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "agent-inbox-mac-app",
   "url": "https://agentsetups.dev/use-case/agent-inbox-mac-app/",
   "title": "Watch and approve all your agents from one inbox",
   "summary": "littleguys, a free Mac app, shows which OpenClaw/Hermes/Claude Code/Codex/ACP agent is working or needs you.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex",
    "OpenClaw",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "littleguys",
    "ACP"
   ],
   "prompt": "Goal: See which agents need me and reply or approve quickly.\nSetup: agents used in source: Claude, Codex, OpenClaw, Hermes Agent; tools/MCPs stated: littleguys, ACP.\nSteps:\n1. Install littleguys (free, open-source).\n2. Connect your ACP agents.\n3. Reply in a few keystrokes and approve in one click.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Herval in the Metaverse of Madness ᯅ — https://x.com/herval/status/2109022124182491203 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install littleguys (free, open-source).",
    "Connect your ACP agents.",
    "Reply in a few keystrokes and approve in one click."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 47.9,
   "sources": [
    {
     "author": "Herval in the Metaverse of Madness ᯅ",
     "handle": "@herval",
     "url": "https://x.com/herval/status/2109022124182491203",
     "platform": "x",
     "date": "2026-10-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "chatgpt-agent-subscription-tracker",
   "url": "https://agentsetups.dev/use-case/chatgpt-agent-subscription-tracker/",
   "title": "Find every subscription in a year of receipts",
   "summary": "@alicialyttle’s ChatGPT agent reads 12 months of Gmail receipts, tables them, flags recurring charges and recommends cuts.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "ChatGPT agent"
   ],
   "models": [],
   "tools": [
    "Gmail"
   ],
   "prompt": "Goal: See every subscription I’m paying for.\nSetup: agents used in source: ChatGPT agent; tools/MCPs stated: Gmail.\nSteps:\n1. Lock down privacy first: turn on MFA, and turn off model training in Data & privacy.\n2. Connect Gmail under Settings → Connectors.\n3. In the prompt box, click + and choose agent mode.\n4. Ask it to analyse receipts from the past 12 months, put them in a table, mark recurring subscriptions and recommend which need attention.\n5. Keep the chat private.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Alicia Lyttle — https://x.com/alicialyttle/status/2106031008239792532",
   "steps": [
    "Lock down privacy first: turn on MFA, and turn off model training in Data & privacy.",
    "Connect Gmail under Settings → Connectors.",
    "In the prompt box, click + and choose agent mode.",
    "Ask it to analyse receipts from the past 12 months, put them in a table, mark recurring subscriptions and recommend which need attention.",
    "Keep the chat private."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 47.8,
   "sources": [
    {
     "author": "Alicia Lyttle",
     "handle": "@alicialyttle",
     "url": "https://x.com/alicialyttle/status/2106031008239792532",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-router-cheap-model",
   "url": "https://agentsetups.dev/use-case/claude-code-router-cheap-model/",
   "title": "Point Claude Code at a cheaper model with Router v3",
   "summary": "Set up Claude Code Router v3.1.1 to send a side project’s traffic to a cheaper model.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Claude Code Router"
   ],
   "prompt": "Goal: Use a cheaper model for a side project inside Claude Code.\nSetup: agents used in source: Claude; tools/MCPs stated: Claude Code Router.\nSteps:\n1. Install Claude Code Router v3.\n2. Configure the provider and model routing.\n3. Run Claude Code through the router.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Zara Menon — https://dev.to/zaramenon/claude-code-router-v3-what-changed-and-how-i-set-it-up-now-mj7 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install Claude Code Router v3.",
    "Configure the provider and model routing.",
    "Run Claude Code through the router."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 47.7,
   "sources": [
    {
     "author": "Zara Menon",
     "handle": "@zaramenon",
     "url": "https://dev.to/zaramenon/claude-code-router-v3-what-changed-and-how-i-set-it-up-now-mj7",
     "platform": "devto",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-catch-booking-mistakes",
   "url": "https://agentsetups.dev/use-case/dots-catch-booking-mistakes/",
   "title": "Let your Dot catch mistakes in your bookings",
   "summary": "@dkundel’s Dot spotted a missing second train ticket; @CtrlAltDwayne’s flagged a Fiji stay booked for the wrong month.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Have my Dot double-check purchases and bookings against my plans.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Give the Dot access to the inbox where confirmations land.\n2. Let it compare confirmations with what you planned and flag gaps (e.g. one ticket where two were needed, or a stay booked in the wrong month).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: dominik kundel — https://x.com/dkundel/status/2110432654638333987 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give the Dot access to the inbox where confirmations land.",
    "Let it compare confirmations with what you planned and flag gaps (e.g. one ticket where two were needed, or a stay booked in the wrong month)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 47.6,
   "sources": [
    {
     "author": "dominik kundel",
     "handle": "@dkundel",
     "url": "https://x.com/dkundel/status/2110432654638333987",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    },
    {
     "author": "Dwayne",
     "handle": "@CtrlAltDwayne",
     "url": "https://x.com/CtrlAltDwayne/status/2105603794293887167",
     "platform": "x",
     "date": "2026-10-01",
     "primary": false
    }
   ]
  },
  {
   "slug": "context-bar-mod",
   "url": "https://agentsetups.dev/use-case/context-bar-mod/",
   "title": "Build a Claude Code mod without writing code",
   "summary": "One prompt produced an always-visible context-window bar; Claude wrote, validated and hot-reloaded the mod.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Claude Code mods"
   ],
   "prompt": "Goal: Show my context window fill level above the prompt at all times.\nSetup: agents used in source: Claude; tools/MCPs stated: Claude Code mods.\nSteps:\n1. Ask Claude to write a Claude Code mod (a JS/TS module in a plugin) for it.\n2. Have it validate and hot-reload the mod.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Pawel — https://dev.to/pawel_nowak/i-built-my-first-claude-code-mod-without-writing-code-claude-wrote-it-validated-it-and-2mh7",
   "steps": [
    "Ask Claude to write a Claude Code mod (a JS/TS module in a plugin) for it.",
    "Have it validate and hot-reload the mod."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 46.7,
   "sources": [
    {
     "author": "Pawel",
     "handle": "@pawel_nowak",
     "url": "https://dev.to/pawel_nowak/i-built-my-first-claude-code-mod-without-writing-code-claude-wrote-it-validated-it-and-2mh7",
     "platform": "devto",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-shop-recall-marketplace",
   "url": "https://agentsetups.dev/use-case/muse-shop-recall-marketplace/",
   "title": "Let Muse shop, book a recall fix and sell on Marketplace",
   "summary": "@IanAndrewsDC’s Muse bought furniture via Stripe Link, booked a recall appointment and listed items on Facebook Marketplace.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [
    "Stripe Link",
    "Facebook Marketplace"
   ],
   "prompt": "Goal: Hand my Muse real purchases, appointments and selling.\nSetup: agents used in source: Meta Muse; tools/MCPs stated: Stripe Link, Facebook Marketplace.\nSteps:\n1. Furniture: send photos of the room and a description; review its 4 options, give feedback, let it search again, then let it buy (via Stripe Link).\n2. When it proactively flags a recall on your car, ask it to find a dealership and book the appointment.\n3. Marketplace: hand it links to the items and let it list them (expect a Facebook identity check), then monitor and reply to inquiries.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Ian Andrews — https://x.com/IanAndrewsDC/status/2106109552047337870",
   "steps": [
    "Furniture: send photos of the room and a description; review its 4 options, give feedback, let it search again, then let it buy (via Stripe Link).",
    "When it proactively flags a recall on your car, ask it to find a dealership and book the appointment.",
    "Marketplace: hand it links to the items and let it list them (expect a Facebook identity check), then monitor and reply to inquiries."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 45.3,
   "sources": [
    {
     "author": "Ian Andrews",
     "handle": "@IanAndrewsDC",
     "url": "https://x.com/IanAndrewsDC/status/2106109552047337870",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "pi-dot-matrix-dashboard",
   "url": "https://agentsetups.dev/use-case/pi-dot-matrix-dashboard/",
   "title": "Feed a Raspberry Pi dot-matrix display from your agent",
   "summary": "A 90s-pinball style display shows weather, lake fishing conditions, bird reports, local shows, sports and AI news.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Raspberry Pi 5"
   ],
   "prompt": "Goal: Build a small display that my agent keeps updated.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Raspberry Pi 5.\nSteps:\n1. Build the display (Raspberry Pi 5 dot-matrix; or Pi Zero 2 W with a 1.3\" screen).\n2. Have the agent feed it: weather, fishing conditions, a hyperlocal bird report, local shows, sports on TV and AI news.\n3. Variant: show Claude Code weekly quota, 5-hour window and model usage on screens you flip with a joystick.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Zachary Taylor — https://x.com/ztaylor/status/2108289455228616868",
   "steps": [
    "Build the display (Raspberry Pi 5 dot-matrix; or Pi Zero 2 W with a 1.3\" screen).",
    "Have the agent feed it: weather, fishing conditions, a hyperlocal bird report, local shows, sports on TV and AI news.",
    "Variant: show Claude Code weekly quota, 5-hour window and model usage on screens you flip with a joystick."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 45.2,
   "sources": [
    {
     "author": "Zachary Taylor",
     "handle": "@ztaylor",
     "url": "https://x.com/ztaylor/status/2108289455228616868",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "alexa-skill-for-agent",
   "url": "https://agentsetups.dev/use-case/alexa-skill-for-agent/",
   "title": "Talk to your agents through Alexa",
   "summary": "Debbie O’Brien had her agent guide her through building an Alexa skill that talks to Grok Bot.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Alexa"
   ],
   "prompt": "Goal: Build an Alexa skill that talks to my agent.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Alexa.\nSteps:\n1. Clone the alexa-grok-bot-skill repo; add your skill ID and webhook; deploy.\n2. When stuck in a console, ask the agent which box to click.\n3. Design around Alexa’s response-time limits.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Debbie O'Brien — https://dev.to/debs_obrien/talk-to-my-bots-through-alexa-building-an-alexa-skill-for-grok-bot-kak",
   "steps": [
    "Clone the alexa-grok-bot-skill repo; add your skill ID and webhook; deploy.",
    "When stuck in a console, ask the agent which box to click.",
    "Design around Alexa’s response-time limits."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 44.0,
   "sources": [
    {
     "author": "Debbie O'Brien",
     "handle": "@debs_obrien",
     "url": "https://dev.to/debs_obrien/talk-to-my-bots-through-alexa-building-an-alexa-skill-for-grok-bot-kak",
     "platform": "devto",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-close-gaps-with-dots-grok",
   "url": "https://agentsetups.dev/use-case/hermes-close-gaps-with-dots-grok/",
   "title": "Close the gaps between Hermes and Dots or Grok Bot",
   "summary": "A gap analysis for Hermes users: persistent responsibilities, a read-only Scout routine, an autonomy policy file and persistent specialists.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "cron",
    "webhooks",
    "pre_tool_call hooks",
    "Kanban"
   ],
   "prompt": "Goal: Make a self-hosted agent behave more like a proactive personal assistant.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: cron, webhooks, pre_tool_call hooks, Kanban.\nSteps:\n1. Add a small “responsibility” layer (objective, owner, triggers, skill, autonomy level, reporting policy) and let cron/events create durable tasks under it.\n2. Build a read-only Scout routine that checks authorised sources (email, calendar, GitHub, notes, feeds) and the web, then ignores, saves, attaches or notifies.\n3. Write an autonomy policy file enforced by pre_tool_call hooks, e.g. email.read auto, email.send ask, purchase ask, credentials human only.\n4. Use persistent specialist profiles plus temporary subagents under a coordinator.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: The analysis was produced with ChatGPT and depersonalised by the author.\nBased on: /u/MJ_Ali45 — https://www.reddit.com/r/hermesagent/comments/1wumxde/closing_most_gaps_between_hermes_vs_dots_and_grok/",
   "steps": [
    "Add a small “responsibility” layer (objective, owner, triggers, skill, autonomy level, reporting policy) and let cron/events create durable tasks under it.",
    "Build a read-only Scout routine that checks authorised sources (email, calendar, GitHub, notes, feeds) and the web, then ignores, saves, attaches or notifies.",
    "Write an autonomy policy file enforced by pre_tool_call hooks, e.g. email.read auto, email.send ask, purchase ask, credentials human only.",
    "Use persistent specialist profiles plus temporary subagents under a coordinator."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 43.8,
   "sources": [
    {
     "author": "/u/MJ_Ali45",
     "handle": "/u/MJ_Ali45",
     "url": "https://www.reddit.com/r/hermesagent/comments/1wumxde/closing_most_gaps_between_hermes_vs_dots_and_grok/",
     "platform": "reddit",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "parallel-sessions-one-checkout",
   "url": "https://agentsetups.dev/use-case/parallel-sessions-one-checkout/",
   "title": "Run three Claude Code sessions on one checkout",
   "summary": "No worktrees: sessions agree on a split, stage only their own hunks by id, and stop if the hunk count changes.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "git"
   ],
   "prompt": "Goal: Let several agent sessions share one repo safely.\nSetup: agents used in source: Claude; tools/MCPs stated: git.\nSteps:\n1. Have sessions agree on a split by message and list the files each will touch.\n2. For shared files, stage only your own changes hunk by hunk, matched by an id in the changed lines.\n3. Use a small command that lists hunks and stages matching ones; if the hunk count changed between listing and staging, stage nothing and stop.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Rulestack — https://dev.to/rulestack/three-claude-code-sessions-share-one-git-checkout-in-our-repo-with-no-worktrees-how-do-you-keep-5dce",
   "steps": [
    "Have sessions agree on a split by message and list the files each will touch.",
    "For shared files, stage only your own changes hunk by hunk, matched by an id in the changed lines.",
    "Use a small command that lists hunks and stages matching ones; if the hunk count changed between listing and staging, stage nothing and stop."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 43.0,
   "sources": [
    {
     "author": "Rulestack",
     "handle": "@rulestack",
     "url": "https://dev.to/rulestack/three-claude-code-sessions-share-one-git-checkout-in-our-repo-with-no-worktrees-how-do-you-keep-5dce",
     "platform": "devto",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "unreal-engine-game",
   "url": "https://agentsetups.dev/use-case/unreal-engine-game/",
   "title": "Build an Unreal Engine game mission with Claude Code",
   "summary": "Loadout menus, shooting mechanics, bullet effects and ragdoll physics built in Unreal with Claude Code.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude",
    "Antigravity"
   ],
   "models": [],
   "tools": [
    "Unreal Engine"
   ],
   "prompt": "Goal: Build a playable mission in a real game engine.\nSetup: agents used in source: Claude, Antigravity; tools/MCPs stated: Unreal Engine.\nSteps:\n1. Set up the engine project.\n2. Have the agent build loadout menus, shooting, effects and physics.\n3. Play the mission and iterate.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Brendan Jowett — https://x.com/jowettbrendan/status/2109538818210799979 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Set up the engine project.",
    "Have the agent build loadout menus, shooting, effects and physics.",
    "Play the mission and iterate."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 42.9,
   "sources": [
    {
     "author": "Brendan Jowett",
     "handle": "@jowettbrendan",
     "url": "https://x.com/jowettbrendan/status/2109538818210799979",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    },
    {
     "author": "Chouaieb Nemri",
     "handle": "@c_nemri",
     "url": "https://x.com/c_nemri/status/2104472843815735362",
     "platform": "x",
     "date": "2026-09-28",
     "primary": false
    }
   ]
  },
  {
   "slug": "obsidian-claude-shared-memory",
   "url": "https://agentsetups.dev/use-case/obsidian-claude-shared-memory/",
   "title": "Use Obsidian folders as Claude Code’s shared memory",
   "summary": "Inbox, projects (each with CLAUDE.md), a memory tree for people/decisions/bugs, and docs Claude reads.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Obsidian"
   ],
   "prompt": "Goal: Organise my vault so Claude Code uses it as memory.\nSetup: agents used in source: Claude; tools/MCPs stated: Obsidian.\nSteps:\n1. Create /00-inbox, /01-projects (each with its own CLAUDE.md), /02-memory and /03-docs.\n2. Keep people, decisions and bugs in the memory tree.\n3. Put stack and rules in each project’s CLAUDE.md.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: v. Splicer — https://dev.to/numbpill3d/obsidian-claude-code-the-shared-memory-stack-i-actually-use-8m",
   "steps": [
    "Create /00-inbox, /01-projects (each with its own CLAUDE.md), /02-memory and /03-docs.",
    "Keep people, decisions and bugs in the memory tree.",
    "Put stack and rules in each project’s CLAUDE.md."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 41.5,
   "sources": [
    {
     "author": "v. Splicer",
     "handle": "@numbpill3d",
     "url": "https://dev.to/numbpill3d/obsidian-claude-code-the-shared-memory-stack-i-actually-use-8m",
     "platform": "devto",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "pwa-game-in-a-day",
   "url": "https://agentsetups.dev/use-case/pwa-game-in-a-day/",
   "title": "Ship a PWA game in a day from a three-sentence idea",
   "summary": "Opus 5.5 in Claude Code shipped a browser game using about half a daily allotment; the harness mattered.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [],
   "prompt": "Goal: Turn a short idea into a shipped browser game in a day.\nSetup: agents used in source: Claude.\nSteps:\n1. Start from a short idea, but set up the harness: structure, checks and a playable loop.\n2. Iterate with the agent and deploy as a PWA.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tiago Vilas Boas (Montanha) — https://dev.to/tiagovilasboas/i-built-a-full-pwa-game-in-one-day-with-claude-opus-55-and-claude-code-here-is-the-real-token-41p7 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Start from a short idea, but set up the harness: structure, checks and a playable loop.",
    "Iterate with the agent and deploy as a PWA."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 40.9,
   "sources": [
    {
     "author": "Tiago Vilas Boas (Montanha)",
     "handle": "@tiagovilasboas",
     "url": "https://dev.to/tiagovilasboas/i-built-a-full-pwa-game-in-one-day-with-claude-opus-55-and-claude-code-here-is-the-real-token-41p7",
     "platform": "devto",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-price-drop-watch",
   "url": "https://agentsetups.dev/use-case/muse-price-drop-watch/",
   "title": "Ask Muse for the best product and get price-drop alerts",
   "summary": "@chrissev asked Muse for the best walking pad; two weeks later it told him, unprompted, it was on sale for $93.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Research a purchase and get told when the price drops.\nSetup: agents used in source: Meta Muse.\nSteps:\n1. Ask Muse for the best option in a category.\n2. Let it keep the request in memory; it may alert you to a sale without being asked.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Chris Sev — https://x.com/chrissev/status/2107917341455729040 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask Muse for the best option in a category.",
    "Let it keep the request in memory; it may alert you to a sale without being asked."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 38.8,
   "sources": [
    {
     "author": "Chris Sev",
     "handle": "@chrissev",
     "url": "https://x.com/chrissev/status/2107917341455729040",
     "platform": "x",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-track-launch-feedback-x",
   "url": "https://agentsetups.dev/use-case/grokbot-track-launch-feedback-x/",
   "title": "Have Grok Bot track feedback on your launches",
   "summary": "Grok Bot found five of a builder’s launched projects, analysed replies, quotes and mentions, then set a daily check.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "X"
   ],
   "prompt": "Goal: Never miss product feedback people leave on X.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Ask Grok Bot to find the products you launched on X and analyse replies, quotes and mentions for feedback you missed.\n2. Have it set up a daily routine to check for new feedback, spot new launches and alert you when something needs attention.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Karata — https://x.com/karatademada/status/2108094746392494217",
   "steps": [
    "Ask Grok Bot to find the products you launched on X and analyse replies, quotes and mentions for feedback you missed.",
    "Have it set up a daily routine to check for new feedback, spot new launches and alert you when something needs attention."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 38.6,
   "sources": [
    {
     "author": "Karata",
     "handle": "@karatademada",
     "url": "https://x.com/karatademada/status/2108094746392494217",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "amp-debug-token-migrate-node",
   "url": "https://agentsetups.dev/use-case/amp-debug-token-migrate-node/",
   "title": "Let Amp find a deploy bug and upgrade Node",
   "summary": "Amp traced a bad API token from headers alone, reproduced it, migrated deps and code to Node.js v24; first PR all green.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [
    "Node.js"
   ],
   "prompt": "Goal: Get a broken project re-deployable.\nSetup: agents used in source: Amp; tools/MCPs stated: Node.js.\nSteps:\n1. Give Amp the failing project and symptoms.\n2. Let it diagnose from the request headers and reproduce the issue.\n3. Have it migrate dependencies and code to Node.js v24.\n4. Review the PR once checks are green.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Liran Tal — https://x.com/liran_tal/status/2109636209374904758",
   "steps": [
    "Give Amp the failing project and symptoms.",
    "Let it diagnose from the request headers and reproduce the issue.",
    "Have it migrate dependencies and code to Node.js v24.",
    "Review the PR once checks are green."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 38.0,
   "sources": [
    {
     "author": "Liran Tal",
     "handle": "@liran_tal",
     "url": "https://x.com/liran_tal/status/2109636209374904758",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "warcraft3-map-sim-from-phone",
   "url": "https://agentsetups.dev/use-case/warcraft3-map-sim-from-phone/",
   "title": "Build a big project mostly from your phone with Amp",
   "summary": "A TypeScript simulator that runs any Warcraft 3 custom map in the browser with multiplayer, 95% prompted from a phone.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [
    "TypeScript"
   ],
   "prompt": "Goal: Drive a large coding project from my phone.\nSetup: agents used in source: Amp; tools/MCPs stated: TypeScript.\nSteps:\n1. Run the project in Amp and prompt it from your phone.\n2. Iterate on bugs and performance as they come up.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Richard Artoul — https://x.com/richardartoul/status/2105821616899015035 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Run the project in Amp and prompt it from your phone.",
    "Iterate on bugs and performance as they come up."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 37.7,
   "sources": [
    {
     "author": "Richard Artoul",
     "handle": "@richardartoul",
     "url": "https://x.com/richardartoul/status/2105821616899015035",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "meta-ads-dashboard",
   "url": "https://agentsetups.dev/use-case/meta-ads-dashboard/",
   "title": "Build your own Meta Ads dashboard with Claude Code",
   "summary": "A System User token with ads_read lets Claude Code pull the Marketing API into a custom dashboard.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Meta Marketing API"
   ],
   "prompt": "Goal: Build a dashboard of the Meta Ads numbers I actually care about.\nSetup: agents used in source: Claude; tools/MCPs stated: Meta Marketing API.\nSteps:\n1. In Meta Business Settings, create a System User.\n2. Give it access to your ad account and generate a token with ads_read permission.\n3. Hand the token to Claude Code and tell it what you want to track (leading indicators, per-campaign and creative performance).\n4. It pulls data from the Meta Marketing API and builds the dashboard around your numbers.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: @dukedoesai reports £35.8k spend → £129.6k revenue, run from Claude Code (own claim).\nBased on: Chris Panteli (Co-Founder) — https://x.com/Linkifi_/status/2105935542315528437",
   "steps": [
    "In Meta Business Settings, create a System User.",
    "Give it access to your ad account and generate a token with ads_read permission.",
    "Hand the token to Claude Code and tell it what you want to track (leading indicators, per-campaign and creative performance).",
    "It pulls data from the Meta Marketing API and builds the dashboard around your numbers."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 37.5,
   "sources": [
    {
     "author": "Chris Panteli (Co-Founder)",
     "handle": "@Linkifi_",
     "url": "https://x.com/Linkifi_/status/2105935542315528437",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "kiro-unattended-s3-lambda-loop",
   "url": "https://agentsetups.dev/use-case/kiro-unattended-s3-lambda-loop/",
   "title": "Check event triggers before leaving Kiro unattended",
   "summary": "Kiro’s thumbnail feature wrote back into the bucket that triggered it; AWS caught the recursive Lambda loop. Use separate buckets.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Kiro"
   ],
   "models": [],
   "tools": [
    "AWS Lambda",
    "S3",
    "Terraform",
    "Go"
   ],
   "prompt": "Goal: Let an agent build serverless features without creating runaway loops.\nSetup: agents used in source: Kiro; tools/MCPs stated: AWS Lambda, S3, Terraform, Go.\nSteps:\n1. Before walking away, review what triggers each function and where its outputs land.\n2. Break write-back loops: separate buckets for originals and derivatives, or filter the trigger by prefix.\n3. “It deployed and the happy path worked” isn’t “safe to walk away”; test the side effects.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: pmalmirae — https://dev.to/aws-builders/dont-try-this-at-home-what-happened-when-i-sent-kiro-to-work-and-went-gardening-131c",
   "steps": [
    "Before walking away, review what triggers each function and where its outputs land.",
    "Break write-back loops: separate buckets for originals and derivatives, or filter the trigger by prefix.",
    "“It deployed and the happy path worked” isn’t “safe to walk away”; test the side effects."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 37.4,
   "sources": [
    {
     "author": "pmalmirae",
     "handle": "@pmalmirae",
     "url": "https://dev.to/aws-builders/dont-try-this-at-home-what-happened-when-i-sent-kiro-to-work-and-went-gardening-131c",
     "platform": "devto",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "local-model-judges-shell-commands",
   "url": "https://agentsetups.dev/use-case/local-model-judges-shell-commands/",
   "title": "Have a small local model vet agent shell commands",
   "summary": "A hook sends every command to a 322M local model that returns allow, review or block; tuned against false blocks and chained commands.",
   "category": "security",
   "category_label": "Security",
   "agents": [
    "Claude",
    "Cursor"
   ],
   "models": [],
   "tools": [
    "laya-guard"
   ],
   "prompt": "Goal: Catch dangerous commands from my coding agent locally, without cloud calls.\nSetup: agents used in source: Claude, Cursor; tools/MCPs stated: laya-guard.\nSteps:\n1. Run a small local server that classifies each tool call as allow, review or block; the agent’s hook calls it before execution.\n2. Test on everyday commands: the first version blocked ls -la and npm run build, so add a careful allowlist.\n3. Don’t allowlist by command name alone (git log --output can write files); split command chains (&&, |) and check every part.\n4. Know the trade-off: it fails open if the server is down.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Changsu Seong — https://dev.to/scs0209/i-let-a-322m-local-model-judge-every-shell-command-my-coding-agent-runs-2hf6",
   "steps": [
    "Run a small local server that classifies each tool call as allow, review or block; the agent’s hook calls it before execution.",
    "Test on everyday commands: the first version blocked ls -la and npm run build, so add a careful allowlist.",
    "Don’t allowlist by command name alone (git log --output can write files); split command chains (&&, |) and check every part.",
    "Know the trade-off: it fails open if the server is down."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 37.0,
   "sources": [
    {
     "author": "Changsu Seong",
     "handle": "@scs0209",
     "url": "https://dev.to/scs0209/i-let-a-322m-local-model-judge-every-shell-command-my-coding-agent-runs-2hf6",
     "platform": "devto",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-cancel-unused-subscriptions",
   "url": "https://agentsetups.dev/use-case/grokbot-cancel-unused-subscriptions/",
   "title": "Cancel unused subscriptions with Grok Bot",
   "summary": "Grok Bot read email and bank data, found every subscription and cancelled unused ones (Audible, Uber One, SiriusXM): ~$1,700/yr.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "email",
    "bank"
   ],
   "prompt": "Goal: Stop paying for subscriptions I don’t use.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: email, bank.\nSteps:\n1. Give Grok Bot access to your email and bank.\n2. Have it list every subscription you pay for.\n3. Have it cancel the unused ones, emailing providers where needed (it cited BC consumer rules to SiriusXM).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Devin Olsen — https://x.com/DevinOlsenn/status/2110595533891067938 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give Grok Bot access to your email and bank.",
    "Have it list every subscription you pay for.",
    "Have it cancel the unused ones, emailing providers where needed (it cited BC consumer rules to SiriusXM)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 36.2,
   "sources": [
    {
     "author": "Devin Olsen",
     "handle": "@DevinOlsenn",
     "url": "https://x.com/DevinOlsenn/status/2110595533891067938",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-fix-mac-going-offline",
   "url": "https://agentsetups.dev/use-case/grokbot-fix-mac-going-offline/",
   "title": "Ask Grok Bot why your Mac keeps going offline",
   "summary": "@Kevin_Logan’s Grok Bot found why his Mac kept sleeping and breaking automations, wrote the fix and installed it.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Keep the machine my automations run on awake and online.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Ask your bot why the Mac keeps going offline.\n2. Let it find the cause, write the fix and install it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kevin Logan — https://x.com/Kevin_Logan/status/2109084141417300385 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask your bot why the Mac keeps going offline.",
    "Let it find the cause, write the fix and install it."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 36.1,
   "sources": [
    {
     "author": "Kevin Logan",
     "handle": "@Kevin_Logan",
     "url": "https://x.com/Kevin_Logan/status/2109084141417300385",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "multi-agent-vps-solana-mvp",
   "url": "https://agentsetups.dev/use-case/multi-agent-vps-solana-mvp/",
   "title": "Run a multi-agent dev system on a cheap VPS",
   "summary": "Hermes, Orca, Engram/MCP, Claude Code and Codex with git worktrees, tmux and a human gate shipped a Solana escrow MVP.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex",
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Oracle Cloud",
    "Orca",
    "Engram",
    "git worktrees",
    "tmux"
   ],
   "prompt": "Goal: Build an MVP with several agents outside the IDE.\nSetup: agents used in source: Claude, Codex, Hermes Agent; tools/MCPs stated: Oracle Cloud, Orca, Engram, git worktrees, tmux.\nSteps:\n1. Set up a VPS (here Oracle Cloud).\n2. Run Hermes, Orca, Engram/MCP, Claude Code and Codex there.\n3. Isolate work in git worktrees and tmux sessions.\n4. Keep a human gate before merges.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Yhona e/acc — https://x.com/thisnotmeeme/status/2106946532880589115",
   "steps": [
    "Set up a VPS (here Oracle Cloud).",
    "Run Hermes, Orca, Engram/MCP, Claude Code and Codex there.",
    "Isolate work in git worktrees and tmux sessions.",
    "Keep a human gate before merges."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 35.6,
   "sources": [
    {
     "author": "Yhona e/acc",
     "handle": "@thisnotmeeme",
     "url": "https://x.com/thisnotmeeme/status/2106946532880589115",
     "platform": "x",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-investigate-phishing-email",
   "url": "https://agentsetups.dev/use-case/grokbot-investigate-phishing-email/",
   "title": "Have Grok Bot investigate a suspicious email",
   "summary": "An email passed SPF, DKIM and DMARC, but Grok Bot found the hidden phishing link and explained why the checks passed.",
   "category": "security",
   "category_label": "Security",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "email"
   ],
   "prompt": "Goal: Check a suspicious email before clicking anything in it.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: email.\nSteps:\n1. Ask your bot to investigate the email.\n2. Have it look for hidden links and explain why authentication checks (SPF, DKIM, DMARC) passed anyway.\n3. Have it suggest a fix or prepare a report.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: A single shared example; it says nothing about how reliably it catches scams.\nBased on: Alex — https://x.com/alexmichaelio/status/2110574355256394089",
   "steps": [
    "Ask your bot to investigate the email.",
    "Have it look for hidden links and explain why authentication checks (SPF, DKIM, DMARC) passed anyway.",
    "Have it suggest a fix or prepare a report."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 34.9,
   "sources": [
    {
     "author": "Alex",
     "handle": "@alexmichaelio",
     "url": "https://x.com/alexmichaelio/status/2110574355256394089",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    },
    {
     "author": "Winter",
     "handle": "@ghosttrends",
     "url": "https://x.com/ghosttrends/status/2110544969262084330",
     "platform": "x",
     "date": "2026-10-15",
     "primary": false
    }
   ]
  },
  {
   "slug": "coding-agent-inside-android-app",
   "url": "https://agentsetups.dev/use-case/coding-agent-inside-android-app/",
   "title": "Run a coding agent inside an Android app",
   "summary": "AndroPI wraps the open-source pi agent in Flutter, with a rootless Debian userland, DNS-over-HTTPS and a live HTML preview.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Pi"
   ],
   "models": [],
   "tools": [
    "Flutter",
    "Node.js",
    "Debian userland"
   ],
   "prompt": "Goal: Use a real coding agent on an Android phone.\nSetup: agents used in source: Pi; tools/MCPs stated: Flutter, Node.js, Debian userland.\nSteps:\n1. Wrap the pi agent in a Flutter UI.\n2. Android won’t execute binaries from app storage, so run a Debian or Alpine userland without root so the agent can apt, pip and npm.\n3. Add DNS-over-HTTPS if your ISP tampers with lookups.\n4. Expect Play Store pushback on all-files access; keep a live HTML preview for web work.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Taqin — https://dev.to/abdulm/i-put-an-ai-coding-agent-inside-an-android-app-heres-everything-that-fought-back-lpk",
   "steps": [
    "Wrap the pi agent in a Flutter UI.",
    "Android won’t execute binaries from app storage, so run a Debian or Alpine userland without root so the agent can apt, pip and npm.",
    "Add DNS-over-HTTPS if your ISP tampers with lookups.",
    "Expect Play Store pushback on all-files access; keep a live HTML preview for web work."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 34.8,
   "sources": [
    {
     "author": "Taqin",
     "handle": "@abdulm",
     "url": "https://dev.to/abdulm/i-put-an-ai-coding-agent-inside-an-android-app-heres-everything-that-fought-back-lpk",
     "platform": "devto",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-freelancer-invoices-poland",
   "url": "https://agentsetups.dev/use-case/grokbot-freelancer-invoices-poland/",
   "title": "Move a one-person business’s paperwork to Grok Bot",
   "summary": "16 agents handle invoices, deals, contracts and X content; the move used ~5% of a weekly limit. National e-invoicing is the hard part.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "KSeF"
   ],
   "prompt": "Goal: Run invoicing, contracts and content for my sole proprietorship with agents.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: KSeF.\nSteps:\n1. Set up agents for invoices, deals, creator contracts, approvals and X content.\n2. Expect friction where systems are built for paper: national e-invoicing (KSeF) needs certificates and a clunky API; accountants may only take PDFs.\n3. Let the agent draft invoices, then carry them through those systems yourself.\n4. Save repeatable jobs as skills (his reads invoices, converts currency, checks screenshots for leaks and writes the post).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: ＺＥＦＩ — https://x.com/zefirium/status/2108547389120221411",
   "steps": [
    "Set up agents for invoices, deals, creator contracts, approvals and X content.",
    "Expect friction where systems are built for paper: national e-invoicing (KSeF) needs certificates and a clunky API; accountants may only take PDFs.",
    "Let the agent draft invoices, then carry them through those systems yourself.",
    "Save repeatable jobs as skills (his reads invoices, converts currency, checks screenshots for leaks and writes the post)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 34.6,
   "sources": [
    {
     "author": "ＺＥＦＩ",
     "handle": "@zefirium",
     "url": "https://x.com/zefirium/status/2108547389120221411",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "woocommerce-mcp-with-approvals",
   "url": "https://agentsetups.dev/use-case/woocommerce-mcp-with-approvals/",
   "title": "Let an agent manage a WooCommerce store with approvals",
   "summary": "A WordPress plugin turns the store into an MCP server with OAuth 2.1; Muse Spark proposes a product and you approve it.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "Muse Code"
   ],
   "models": [
    "Muse Spark"
   ],
   "tools": [
    "WordPress",
    "WooCommerce",
    "MCP",
    "OAuth 2.1"
   ],
   "prompt": "Goal: Give an AI agent controlled access to my online store.\nSetup: agents used in source: Muse Code; tools/MCPs stated: WordPress, WooCommerce, MCP, OAuth 2.1.\nSteps:\n1. Install an MCP bridge plugin (the author’s MuseSpark MCP Bridge) to expose selected WordPress/WooCommerce tools.\n2. Authorise the agent via the plugin’s OAuth 2.1 server.\n3. Have the agent propose actions (e.g. create a product with price, stock, SKU, categories and SEO).\n4. Review and approve each action in the admin dashboard before it runs.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Joni Ilman Pahmi — https://dev.to/joni_ilman12/i-turned-my-wordpress-store-into-an-mcp-server-now-an-ai-agent-runs-my-business-with-my-1i3c",
   "steps": [
    "Install an MCP bridge plugin (the author’s MuseSpark MCP Bridge) to expose selected WordPress/WooCommerce tools.",
    "Authorise the agent via the plugin’s OAuth 2.1 server.",
    "Have the agent propose actions (e.g. create a product with price, stock, SKU, categories and SEO).",
    "Review and approve each action in the admin dashboard before it runs."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 34.4,
   "sources": [
    {
     "author": "Joni Ilman Pahmi",
     "handle": "@joni_ilman12",
     "url": "https://dev.to/joni_ilman12/i-turned-my-wordpress-store-into-an-mcp-server-now-an-ai-agent-runs-my-business-with-my-1i3c",
     "platform": "devto",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "three-layer-claude-code-safety",
   "url": "https://agentsetups.dev/use-case/three-layer-claude-code-safety/",
   "title": "Protect files with sandbox, hooks and checkpoints",
   "summary": "Turn on /sandbox, block destructive commands with hooks, and keep git checkpoints so one bad command is a one-step rollback.",
   "category": "security",
   "category_label": "Security",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Seatbelt",
    "bubblewrap",
    "git"
   ],
   "prompt": "Goal: Let Claude Code run real commands without risking my files.\nSetup: agents used in source: Claude; tools/MCPs stated: Seatbelt, bubblewrap, git.\nSteps:\n1. Layer 1: run /sandbox in a session; writes are confined to the project at OS level (Seatbelt on macOS, bubblewrap on Linux/WSL2). Not on native Windows.\n2. Layer 2: add hooks that stop destructive commands (force-push to main, DROP TABLE, reset --hard) or make Claude ask first.\n3. Layer 3: keep git checkpoints so you can roll back in one command if something slips through.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: anassBld — https://dev.to/anasbuilds997/claude-code-can-delete-your-files-the-3-layer-setup-i-run-sandbox-hooks-git-checkpoints-188h",
   "steps": [
    "Layer 1: run /sandbox in a session; writes are confined to the project at OS level (Seatbelt on macOS, bubblewrap on Linux/WSL2). Not on native Windows.",
    "Layer 2: add hooks that stop destructive commands (force-push to main, DROP TABLE, reset --hard) or make Claude ask first.",
    "Layer 3: keep git checkpoints so you can roll back in one command if something slips through."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 34.2,
   "sources": [
    {
     "author": "anassBld",
     "handle": "@anasbuilds997",
     "url": "https://dev.to/anasbuilds997/claude-code-can-delete-your-files-the-3-layer-setup-i-run-sandbox-hooks-git-checkpoints-188h",
     "platform": "devto",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-find-emails-that-slipped",
   "url": "https://agentsetups.dev/use-case/dots-find-emails-that-slipped/",
   "title": "Ask your Dot for emails that fell through the cracks",
   "summary": "@arpans’ Dot found a document he owed his CPA plus vendor and appointment follow-ups; another user’s Dot nudges each new email.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Find what I forgot to act on in my personal inbox.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Connect your personal inbox.\n2. Ask: find emails that fell through the cracks.\n3. Review what it surfaces: documents to forward (e.g. to your accountant), appointment and vendor follow-ups.\n4. Optionally let it nudge you on each new email and ask it to send emails or update sheets and docs for you.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Arpan Shah — https://x.com/arpans/status/2109885241989218560",
   "steps": [
    "Connect your personal inbox.",
    "Ask: find emails that fell through the cracks.",
    "Review what it surfaces: documents to forward (e.g. to your accountant), appointment and vendor follow-ups.",
    "Optionally let it nudge you on each new email and ask it to send emails or update sheets and docs for you."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 33.5,
   "sources": [
    {
     "author": "Arpan Shah",
     "handle": "@arpans",
     "url": "https://x.com/arpans/status/2109885241989218560",
     "platform": "x",
     "date": "2026-10-13",
     "primary": true
    },
    {
     "author": "Ali",
     "handle": "@somehowali",
     "url": "https://x.com/somehowali/status/2107195622562373662",
     "platform": "x",
     "date": "2026-10-05",
     "primary": false
    }
   ]
  },
  {
   "slug": "find-wasted-disk-space",
   "url": "https://agentsetups.dev/use-case/find-wasted-disk-space/",
   "title": "Find 112 GB of wasted disk space without deleting anything",
   "summary": "A pasteable prompt sorts repos, build outputs, node_modules, caches, Xcode and old worktrees into tables before any deletion.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Find what is eating my disk.\nSetup: agents used in source: Claude.\nSteps:\n1. Check repos, gitignored build outputs, node_modules, caches, Xcode, simulators and old worktrees.\n2. Don’t delete anything yet.\n3. Give me tables, starting with “safe to delete” and “rebuildable”, so I can choose.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dante — https://x.com/dantegaleazzi/status/2109587379266990278",
   "steps": [
    "Check repos, gitignored build outputs, node_modules, caches, Xcode, simulators and old worktrees.",
    "Don’t delete anything yet.",
    "Give me tables, starting with “safe to delete” and “rebuildable”, so I can choose."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 33.1,
   "sources": [
    {
     "author": "Dante",
     "handle": "@dantegaleazzi",
     "url": "https://x.com/dantegaleazzi/status/2109587379266990278",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "three-js-game-zero-assets",
   "url": "https://agentsetups.dev/use-case/three-js-game-zero-assets/",
   "title": "Build a cozy three.js game with zero imported assets",
   "summary": "Every cat, bowl, pond and tree made in code with Claude Code; the trick is the agent never guesses — it’s all written down first.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "three.js"
   ],
   "prompt": "Goal: Make a cute 3D restaurant game without any asset packs.\nSetup: agents used in source: Claude; tools/MCPs stated: three.js.\nSteps:\n1. Write one brief before building.\n2. Write down everything the agent needs so it never guesses.\n3. Have Claude Code build every model procedurally in three.js.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: anul agarwal — https://x.com/anulagarwal/status/2110599427656429939 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Write one brief before building.",
    "Write down everything the agent needs so it never guesses.",
    "Have Claude Code build every model procedurally in three.js."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 32.5,
   "sources": [
    {
     "author": "anul agarwal",
     "handle": "@anulagarwal",
     "url": "https://x.com/anulagarwal/status/2110599427656429939",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "family-business-erp-claude-code",
   "url": "https://agentsetups.dev/use-case/family-business-erp-claude-code/",
   "title": "Build your family business’s own ERP with Claude Code",
   "summary": "A car-wash service firm replaced its ERP and runs agents; humans approve anything with money, from a phone.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "SQL"
   ],
   "prompt": "Goal: Replace commercial business software with our own, built with AI.\nSetup: agents used in source: Claude; tools/MCPs stated: SQL.\nSteps:\n1. Write procedures down; every incident becomes a dated rule the agents read.\n2. Use an approval loop: review the day’s decisions from your phone; nothing with money moves without a human click.\n3. Keep production and testing in separate copies with separate databases.\n4. Test the money logic: invoice numbering per series, VAT, rounding, against real SQL on many random documents.\n5. Use one session per topic with a short hand-over note; long sessions waste tokens. Keep local models to small mechanical jobs.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jorge Garzón — https://dev.to/satgarzon/two-years-in-a-family-car-wash-service-company-running-its-own-erp-and-ai-agents-built-with-claude-89a",
   "steps": [
    "Write procedures down; every incident becomes a dated rule the agents read.",
    "Use an approval loop: review the day’s decisions from your phone; nothing with money moves without a human click.",
    "Keep production and testing in separate copies with separate databases.",
    "Test the money logic: invoice numbering per series, VAT, rounding, against real SQL on many random documents.",
    "Use one session per topic with a short hand-over note; long sessions waste tokens. Keep local models to small mechanical jobs."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 31.8,
   "sources": [
    {
     "author": "Jorge Garzón",
     "handle": "@satgarzon",
     "url": "https://dev.to/satgarzon/two-years-in-a-family-car-wash-service-company-running-its-own-erp-and-ai-agents-built-with-claude-89a",
     "platform": "devto",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "esp32-wake-time-skill",
   "url": "https://agentsetups.dev/use-case/esp32-wake-time-skill/",
   "title": "Cut an ESP32 display’s wake time from 7s to 0.9s",
   "summary": "Applying Anthropic’s “how we made it faster” method; battery life goes from ~1 month to ~10. Packaged as a Claude Code skill.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "ESP32"
   ],
   "prompt": "Goal: Make a slow device or program start faster.\nSetup: agents used in source: Claude; tools/MCPs stated: ESP32.\nSteps:\n1. Apply Anthropic’s published speed-up method to your software (here a battery-powered ESP32 display).\n2. Measure wake time and battery impact before and after.\n3. Turn the method into a Claude Code skill to reuse on any software.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Steve Dakh — https://x.com/stevedakh/status/2109702526845014040 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Apply Anthropic’s published speed-up method to your software (here a battery-powered ESP32 display).",
    "Measure wake time and battery impact before and after.",
    "Turn the method into a Claude Code skill to reuse on any software."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 31.2,
   "sources": [
    {
     "author": "Steve Dakh",
     "handle": "@stevedakh",
     "url": "https://x.com/stevedakh/status/2109702526845014040",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "supply-chain-ops-agent",
   "url": "https://agentsetups.dev/use-case/supply-chain-ops-agent/",
   "title": "Run supply-chain paperwork with an ops agent team",
   "summary": "Officer Can handles co-packer paperwork, vendor forms, COAs, POs and chasing docs for a beverage brand.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Build an operations team that does my supply-chain busywork.\nSetup: agents used in source: Claude, Codex.\nSteps:\n1. Hand the Officer Can playbook to Claude Code or Codex to build the system for your business.\n2. Roles: Inbox Clerk (sorts email), Form Filler (remembers your answers), Negotiator (replies from the facts), File Clerk (files attachments, watches expiry dates).\n3. Focus your time on relationships while it does the papers.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Matt Cauble — https://x.com/thecauble/status/2105674557407281490",
   "steps": [
    "Hand the Officer Can playbook to Claude Code or Codex to build the system for your business.",
    "Roles: Inbox Clerk (sorts email), Form Filler (remembers your answers), Negotiator (replies from the facts), File Clerk (files attachments, watches expiry dates).",
    "Focus your time on relationships while it does the papers."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 31.2,
   "sources": [
    {
     "author": "Matt Cauble",
     "handle": "@thecauble",
     "url": "https://x.com/thecauble/status/2105674557407281490",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "cheap-models-as-claude-subagents",
   "url": "https://agentsetups.dev/use-case/cheap-models-as-claude-subagents/",
   "title": "Use cheap models as subagents inside Claude Code",
   "summary": "Many cheap models speak the Anthropic API, so a small tool (cameo) lets Opus delegate to them as subagents.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5",
    "Fable 5.1"
   ],
   "tools": [
    "cameo",
    "herdr"
   ],
   "prompt": "Goal: Use spare quotas on cheaper models without leaving Claude Code.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: cameo, herdr.\nSteps:\n1. Note that many cheap models expose Anthropic-compatible endpoints.\n2. Wrap each one so Claude Code can launch it as a subagent (the author’s cameo, built by Opus in one shot from a short prompt).\n3. Keep your main session on Claude; delegate grunt work to the cheaper subagents.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Maple — https://dev.to/maple/using-third-party-models-as-subagents-alongside-claude-in-claude-code-4i38 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Note that many cheap models expose Anthropic-compatible endpoints.",
    "Wrap each one so Claude Code can launch it as a subagent (the author’s cameo, built by Opus in one shot from a short prompt).",
    "Keep your main session on Claude; delegate grunt work to the cheaper subagents."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 30.4,
   "sources": [
    {
     "author": "Maple",
     "handle": "@maple",
     "url": "https://dev.to/maple/using-third-party-models-as-subagents-alongside-claude-in-claude-code-4i38",
     "platform": "devto",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "agent-fleet-rate-limit-resilience",
   "url": "https://agentsetups.dev/use-case/agent-fleet-rate-limit-resilience/",
   "title": "Keep an agent fleet alive through rate limits",
   "summary": "Classify errors, use jittered backoff with a retry budget, one shared circuit breaker, and checkpoint-and-park instead of crash.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Python"
   ],
   "prompt": "Goal: Stop API rate limits and outages from killing my 24/7 coding agents.\nSetup: agents used in source: Claude; tools/MCPs stated: Python.\nSteps:\n1. Classify errors before retrying (rate limit vs. overload vs. real failure).\n2. Use exponential backoff with full jitter and a retry budget; honour retry-after.\n3. Share one circuit breaker across the fleet so agents don’t all probe a struggling provider.\n4. When a task runs out of budget, write a checkpoint and park it instead of failing.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: yureki_lab — https://dev.to/yureki_lab/how-i-made-my-autonomous-coding-agent-survive-api-rate-limits-and-outages-3912",
   "steps": [
    "Classify errors before retrying (rate limit vs. overload vs. real failure).",
    "Use exponential backoff with full jitter and a retry budget; honour retry-after.",
    "Share one circuit breaker across the fleet so agents don’t all probe a struggling provider.",
    "When a task runs out of budget, write a checkpoint and park it instead of failing."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 29.6,
   "sources": [
    {
     "author": "yureki_lab",
     "handle": "@yureki_lab",
     "url": "https://dev.to/yureki_lab/how-i-made-my-autonomous-coding-agent-survive-api-rate-limits-and-outages-3912",
     "platform": "devto",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "do-once-then-script-then-cron",
   "url": "https://agentsetups.dev/use-case/do-once-then-script-then-cron/",
   "title": "Turn tasks into cron scripts after doing them once",
   "summary": "Do a task once with Claude Code next to you, argue until it’s right, then say “turn what we just did into a script” and cron it.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "cron"
   ],
   "prompt": "Goal: Build an AI stack of automations without planning one.\nSetup: agents used in source: Claude; tools/MCPs stated: cron.\nSteps:\n1. Do the task once with Claude Code, arguing until the output is right.\n2. At the end say: “turn what we just did into a script.”\n3. Put the script on a cron: daily, weekly, whatever the task needs.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: andrew jennings — https://x.com/andrew_jennings/status/2107594359579537634 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Do the task once with Claude Code, arguing until the output is right.",
    "At the end say: “turn what we just did into a script.”",
    "Put the script on a cron: daily, weekly, whatever the task needs."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 29.6,
   "sources": [
    {
     "author": "andrew jennings",
     "handle": "@andrew_jennings",
     "url": "https://x.com/andrew_jennings/status/2107594359579537634",
     "platform": "x",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "codex-revive-old-ios-game",
   "url": "https://agentsetups.dev/use-case/codex-revive-old-ios-game/",
   "title": "Revive an old iOS game on web, Watch and Vision Pro",
   "summary": "A dev brought back a 12-year-old iOS game with Codex and shipped it to the browser, Apple Watch and Vision Pro.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "Apple Watch",
    "Vision Pro"
   ],
   "prompt": "Goal: Bring my old game back on new platforms.\nSetup: agents used in source: Codex; tools/MCPs stated: Apple Watch, Vision Pro.\nSteps:\n1. Point Codex at the old iOS game.\n2. Port it to the browser, Apple Watch and Vision Pro.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: 大西瓜焚岚 — https://x.com/deadseafu/status/2108028084641558916 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Point Codex at the old iOS game.",
    "Port it to the browser, Apple Watch and Vision Pro."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 29.5,
   "sources": [
    {
     "author": "大西瓜焚岚",
     "handle": "@deadseafu",
     "url": "https://x.com/deadseafu/status/2108028084641558916",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "diff-budget-scope-creep",
   "url": "https://agentsetups.dev/use-case/diff-budget-scope-creep/",
   "title": "Cap scope creep with a per-task diff budget",
   "summary": "Each task declares allowed paths and a size budget; a pre-edit hook blocks out-of-scope writes and a parking lot keeps ideas.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Keep small agent tasks small.\nSetup: agents used in source: Claude.\nSteps:\n1. Every task spec declares a scope block: allowed paths and a diff size budget.\n2. A Claude Code PreToolUse hook blocks edits outside the allowed paths before they land.\n3. A post-run check enforces the size budget inside the allowed directory.\n4. Give the agent a parking lot file to note out-of-scope problems instead of fixing them.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: yureki_lab — https://dev.to/yureki_lab/how-i-stopped-my-ai-coding-agents-scope-creep-with-a-diff-budget-47lj",
   "steps": [
    "Every task spec declares a scope block: allowed paths and a diff size budget.",
    "A Claude Code PreToolUse hook blocks edits outside the allowed paths before they land.",
    "A post-run check enforces the size budget inside the allowed directory.",
    "Give the agent a parking lot file to note out-of-scope problems instead of fixing them."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 28.9,
   "sources": [
    {
     "author": "yureki_lab",
     "handle": "@yureki_lab",
     "url": "https://dev.to/yureki_lab/how-i-stopped-my-ai-coding-agents-scope-creep-with-a-diff-budget-47lj",
     "platform": "devto",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "replace-paid-push-service",
   "url": "https://agentsetups.dev/use-case/replace-paid-push-service/",
   "title": "Replace a newly paid SaaS with your own build",
   "summary": "When OneSignal’s pricing went to ~$100/month for him, a builder and Codex built their own push-notification service.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Stop paying for a service whose free tier disappeared.\nSetup: agents used in source: Codex.\nSteps:\n1. Ask Codex to assess what you actually use from the service.\n2. Build your own replacement for that subset.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Runemir — https://x.com/RunemirQi/status/2106626111182426602 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask Codex to assess what you actually use from the service.",
    "Build your own replacement for that subset."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 28.2,
   "sources": [
    {
     "author": "Runemir",
     "handle": "@RunemirQi",
     "url": "https://x.com/RunemirQi/status/2106626111182426602",
     "platform": "x",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "ralph-loop-network-sandbox",
   "url": "https://agentsetups.dev/use-case/ralph-loop-network-sandbox/",
   "title": "Sandbox an unattended Claude Code loop",
   "summary": "ralph-sandbox: internal Docker network with an allowlist proxy, no Docker socket, host-side snapshots, read-only QA agent.",
   "category": "security",
   "category_label": "Security",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [],
   "tools": [
    "Docker",
    "git bundle"
   ],
   "prompt": "Goal: Run a coding agent with skipped permissions without risking my machine.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: Docker, git bundle.\nSteps:\n1. Put the agent in a container on a Docker --internal network; the only way out is an allowlist proxy that tunnels TLS on 443.\n2. Never mount the Docker socket; run as an unprivileged user; keep webhook URLs out and post notifications from the host.\n3. Before each run, snapshot the repo to a hidden git ref plus a git bundle outside the mount.\n4. Run the Ralph loop: same prompt, fresh session, one task per iteration until the PRD is done.\n5. Give the QA agent no edit tools; if Claude hits a usage limit, let Codex take over with its own three attempts.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jean Manzo — https://x.com/jdevmanzo/status/2107865498230706527",
   "steps": [
    "Put the agent in a container on a Docker --internal network; the only way out is an allowlist proxy that tunnels TLS on 443.",
    "Never mount the Docker socket; run as an unprivileged user; keep webhook URLs out and post notifications from the host.",
    "Before each run, snapshot the repo to a hidden git ref plus a git bundle outside the mount.",
    "Run the Ralph loop: same prompt, fresh session, one task per iteration until the PRD is done.",
    "Give the QA agent no edit tools; if Claude hits a usage limit, let Codex take over with its own three attempts."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 27.3,
   "sources": [
    {
     "author": "Jean Manzo",
     "handle": "@jdevmanzo",
     "url": "https://x.com/jdevmanzo/status/2107865498230706527",
     "platform": "x",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "backup-claude-code-setup",
   "url": "https://agentsetups.dev/use-case/backup-claude-code-setup/",
   "title": "Back up your whole Claude Code setup to GitHub",
   "summary": "CLAUDE.md files, skills, hooks, settings and memory go into a private repo, with one install script to restore on a new Mac.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "GitHub"
   ],
   "prompt": "Goal: Never lose my agent configuration.\nSetup: agents used in source: Claude; tools/MCPs stated: GitHub.\nSteps:\n1. Collect CLAUDE.md files, skills, hooks, settings and memory into one private GitHub repo.\n2. Write one install script that puts everything back on a new machine.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tejas Kalpande — https://x.com/tejaskalpande/status/2108568392173318432",
   "steps": [
    "Collect CLAUDE.md files, skills, hooks, settings and memory into one private GitHub repo.",
    "Write one install script that puts everything back on a new machine."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 27.0,
   "sources": [
    {
     "author": "Tejas Kalpande",
     "handle": "@tejaskalpande",
     "url": "https://x.com/tejaskalpande/status/2108568392173318432",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "extract-memories-across-harnesses",
   "url": "https://agentsetups.dev/use-case/extract-memories-across-harnesses/",
   "title": "Extract your memories from thousands of chats",
   "summary": "Instead of an agent run, a builder had Opus 5.5 extract memories across Claude, Cursor and Codex chats to stay portable.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "Claude",
    "Codex",
    "Cursor"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [],
   "prompt": "Goal: Keep my memory portable when I switch harnesses often.\nSetup: agents used in source: Claude, Codex, Cursor.\nSteps:\n1. Export chats from Claude, Cursor and Codex.\n2. Have Opus 5.5 extract memories across them (cheaper than an agent loop).\n3. Load the result into whichever harness you use next.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: shawn — https://x.com/shawnbuilds/status/2107473164641210720 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Export chats from Claude, Cursor and Codex.",
    "Have Opus 5.5 extract memories across them (cheaper than an agent loop).",
    "Load the result into whichever harness you use next."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 26.7,
   "sources": [
    {
     "author": "shawn",
     "handle": "@shawnbuilds",
     "url": "https://x.com/shawnbuilds/status/2107473164641210720",
     "platform": "x",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "game-while-claude-works",
   "url": "https://agentsetups.dev/use-case/game-while-claude-works/",
   "title": "Build a multiplayer mini-game to play while Claude works",
   "summary": "With Claude Code mods, a builder made an FPS that launches while you wait; other players are people waiting on Claude too.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Use agent wait time for something fun.\nSetup: agents used in source: Claude.\nSteps:\n1. Use Claude Code’s mods to launch a game while the agent works.\n2. Make it multiplayer so other waiting users join; works on Windows too.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: XHabib — https://x.com/XHabib/status/2106440637004300297 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Use Claude Code’s mods to launch a game while the agent works.",
    "Make it multiplayer so other waiting users join; works on Windows too."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 26.7,
   "sources": [
    {
     "author": "XHabib",
     "handle": "@XHabib",
     "url": "https://x.com/XHabib/status/2106440637004300297",
     "platform": "x",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-kids-halloween-game",
   "url": "https://agentsetups.dev/use-case/grokbot-kids-halloween-game/",
   "title": "Make a Halloween browser game from one sentence",
   "summary": "@Frank_AI_Lab gave Grok Bot one sentence; it built a swipe-and-smash game with combos, ghosts, a skull bomb and a pumpkin boss.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Make a quick browser game for my kids.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Describe the game in one sentence.\n2. Let Grok Bot build it and play it in the browser.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Frank — https://x.com/Frank_AI_Lab/status/2108787379276222702 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Describe the game in one sentence.",
    "Let Grok Bot build it and play it in the browser."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 24.7,
   "sources": [
    {
     "author": "Frank",
     "handle": "@Frank_AI_Lab",
     "url": "https://x.com/Frank_AI_Lab/status/2108787379276222702",
     "platform": "x",
     "date": "2026-10-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-in-chrome-woocommerce-redesign",
   "url": "https://agentsetups.dev/use-case/claude-in-chrome-woocommerce-redesign/",
   "title": "Redesign a WooCommerce store via Claude in Chrome",
   "summary": "Claude Code drove Claude in Chrome on a live store: audit, new logo and images, page redesigns, CRO fixes, 1-click checkout.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "WordPress",
    "WooCommerce"
   ],
   "prompt": "Goal: Redesign and fix an old WordPress + WooCommerce store.\nSetup: agents used in source: Claude; tools/MCPs stated: WordPress, WooCommerce.\nSteps:\n1. Run Claude Code in the terminal and let it call the Claude in Chrome extension on your site (the author worked on live, with no staging; use staging if you can).\n2. Audit: broken images and links, missing SEO tags, slow pages, broken design.\n3. Create and apply a new logo; redesign pages; recreate and replace store images.\n4. CRO: sorting order, bundled products, filters, 1-click checkout instead of 3.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: HeyNikhila — https://x.com/HeyNikhila/status/2110375208414855526",
   "steps": [
    "Run Claude Code in the terminal and let it call the Claude in Chrome extension on your site (the author worked on live, with no staging; use staging if you can).",
    "Audit: broken images and links, missing SEO tags, slow pages, broken design.",
    "Create and apply a new logo; redesign pages; recreate and replace store images.",
    "CRO: sorting order, bundled products, filters, 1-click checkout instead of 3."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 24.5,
   "sources": [
    {
     "author": "HeyNikhila",
     "handle": "@HeyNikhila",
     "url": "https://x.com/HeyNikhila/status/2110375208414855526",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "homelab-kvm-dashboard",
   "url": "https://agentsetups.dev/use-case/homelab-kvm-dashboard/",
   "title": "Build one dashboard for all your homelab KVMs",
   "summary": "Claude Code built a simple dashboard giving quick access to every GL.iNet Comet KVM connected to the lab systems.",
   "category": "devops",
   "category_label": "DevOps",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "GL.iNet Comet KVM"
   ],
   "prompt": "Goal: Manage remote homelab machines from one place.\nSetup: agents used in source: Claude; tools/MCPs stated: GL.iNet Comet KVM.\nSteps:\n1. List the KVM devices and their addresses.\n2. Ask Claude Code to build a simple dashboard linking to each.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dale Hassinger — https://x.com/dalehassinger/status/2109758509969711123 (summarised from source; the source has no explicit step list)",
   "steps": [
    "List the KVM devices and their addresses.",
    "Ask Claude Code to build a simple dashboard linking to each."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 24.1,
   "sources": [
    {
     "author": "Dale Hassinger",
     "handle": "@dalehassinger",
     "url": "https://x.com/dalehassinger/status/2109758509969711123",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "amp-legacy-stack-weekend-features",
   "url": "https://agentsetups.dev/use-case/amp-legacy-stack-weekend-features/",
   "title": "Ship features across legacy and mobile stacks with Amp",
   "summary": "Local runners on a legacy WebForms site, Orbs on a .NET API and React Native app with staging deploys and Expo previews: 12+ features.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [
    "WebForms",
    ".NET",
    "React Native",
    "Expo"
   ],
   "prompt": "Goal: Ship a backlog across three codebases in one weekend.\nSetup: agents used in source: Amp; tools/MCPs stated: WebForms, .NET, React Native, Expo.\nSteps:\n1. Use Amp locally for the legacy WebForms site.\n2. Use Orbs for the .NET API and React Native app features.\n3. Have the Orbs deploy to staging and send Expo previews to your phone.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Alex Heffernan — https://x.com/AlexH2035/status/2106867233825898634",
   "steps": [
    "Use Amp locally for the legacy WebForms site.",
    "Use Orbs for the .NET API and React Native app features.",
    "Have the Orbs deploy to staging and send Expo previews to your phone."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 23.8,
   "sources": [
    {
     "author": "Alex Heffernan",
     "handle": "@AlexH2035",
     "url": "https://x.com/AlexH2035/status/2106867233825898634",
     "platform": "x",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-support-ads-refunds-team",
   "url": "https://agentsetups.dev/use-case/grokbot-support-ads-refunds-team/",
   "title": "Have a Grok Bot team handle support and refunds",
   "summary": "@johnmccoyx’s bots handle support tickets, account fixes, the morning ads report, refund/dispute paperwork and content drafts.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Hand day-to-day operations to bots and keep decisions for myself.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Bots: customer support tickets, account fixes and access issues, an ads report every morning, refund and dispute paperwork, content ideas and drafts.\n2. You: decisions and building.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: John McCoy — https://x.com/johnmccoyx/status/2108012315602034988",
   "steps": [
    "Bots: customer support tickets, account fixes and access issues, an ads report every morning, refund and dispute paperwork, content ideas and drafts.",
    "You: decisions and building."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 23.7,
   "sources": [
    {
     "author": "John McCoy",
     "handle": "@johnmccoyx",
     "url": "https://x.com/johnmccoyx/status/2108012315602034988",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "content-waterfall-from-one-video",
   "url": "https://agentsetups.dev/use-case/content-waterfall-from-one-video/",
   "title": "Turn one weekly video into 20+ posts",
   "summary": "Claude Code turns one recorded video into LinkedIn/X posts, a newsletter, an X Article and graphics: 300k+ impressions, 109 signups.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "LinkedIn",
    "X"
   ],
   "prompt": "Goal: Keep up B2B distribution without spending the week on content.\nSetup: agents used in source: Claude; tools/MCPs stated: LinkedIn, X.\nSteps:\n1. Record one video a week.\n2. Have Claude Code turn it into several LinkedIn and X posts, one newsletter, an X Article, and graphics and carousels.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Tim Scheuer — https://x.com/timscheuer/status/2108543008505319500",
   "steps": [
    "Record one video a week.",
    "Have Claude Code turn it into several LinkedIn and X posts, one newsletter, an X Article, and graphics and carousels."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 23.4,
   "sources": [
    {
     "author": "Tim Scheuer",
     "handle": "@timscheuer",
     "url": "https://x.com/timscheuer/status/2108543008505319500",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "perplexity-computer-stock-terminal",
   "url": "https://agentsetups.dev/use-case/perplexity-computer-stock-terminal/",
   "title": "Build a stock analysis terminal with Perplexity Computer",
   "summary": "One instruction: a terminal for analysing $NVDA with real-time data from Perplexity Finance; no code written by hand.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [],
   "tools": [
    "Perplexity Finance"
   ],
   "prompt": "Goal: Get a custom analysis dashboard for one stock.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Perplexity Finance.\nSteps:\n1. Give Computer one instruction: build a terminal to analyse a ticker using real-time Perplexity Finance data.\n2. Review what it builds.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Quant Science — https://x.com/quantscience_/status/2110038128400404559 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give Computer one instruction: build a terminal to analyse a ticker using real-time Perplexity Finance data.",
    "Review what it builds."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 23.4,
   "sources": [
    {
     "author": "Quant Science",
     "handle": "@quantscience_",
     "url": "https://x.com/quantscience_/status/2110038128400404559",
     "platform": "x",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "perplexity-computer-weekly-changes",
   "url": "https://agentsetups.dev/use-case/perplexity-computer-weekly-changes/",
   "title": "Get a weekly what-changed report with Perplexity Computer",
   "summary": "@JulianGoldieSEO sets Computer Automations to track a topic weekly and report only what changed, and charts raw numbers.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [],
   "tools": [
    "Perplexity Computer Automations"
   ],
   "prompt": "Goal: Track a topic every week and only see what’s new.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: Perplexity Computer Automations.\nSteps:\n1. Choose something worth tracking (creator topics, community questions).\n2. Set the weekly schedule.\n3. Define the sources it should check.\n4. For metrics, give Computer the spreadsheet, have it chart visits and signups and what changed, then ask for five things to test next.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Julian Goldie SEO — https://x.com/JulianGoldieSEO/status/2106773183970095379 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Choose something worth tracking (creator topics, community questions).",
    "Set the weekly schedule.",
    "Define the sources it should check.",
    "For metrics, give Computer the spreadsheet, have it chart visits and signups and what changed, then ask for five things to test next."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 22.2,
   "sources": [
    {
     "author": "Julian Goldie SEO",
     "handle": "@JulianGoldieSEO",
     "url": "https://x.com/JulianGoldieSEO/status/2106773183970095379",
     "platform": "x",
     "date": "2026-10-04",
     "primary": true
    },
    {
     "author": "Julian Goldie SEO",
     "handle": "@JulianGoldieSEO",
     "url": "https://x.com/JulianGoldieSEO/status/2107705558241558775",
     "platform": "x",
     "date": "2026-10-07",
     "primary": false
    }
   ]
  },
  {
   "slug": "lovable-frontend-claude-code-backend",
   "url": "https://agentsetups.dev/use-case/lovable-frontend-claude-code-backend/",
   "title": "Pair Lovable for v1 UI with Claude Code for the backend",
   "summary": "A kids’ book app: frontend on Lovable in ~2 weeks, backend almost entirely with Claude Code, so he owns the code afterwards.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Lovable"
   ],
   "prompt": "Goal: Ship an app fast without losing ownership of the code.\nSetup: agents used in source: Claude; tools/MCPs stated: Lovable.\nSteps:\n1. Use Lovable to get v1 of the frontend on screen fast.\n2. Build the backend with Claude Code.\n3. Own and maintain the code yourself afterwards.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Shirochenko Dmitriy — https://x.com/dmshirochenko/status/2107024678560616854",
   "steps": [
    "Use Lovable to get v1 of the frontend on screen fast.",
    "Build the backend with Claude Code.",
    "Own and maintain the code yourself afterwards."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 21.5,
   "sources": [
    {
     "author": "Shirochenko Dmitriy",
     "handle": "@dmshirochenko",
     "url": "https://x.com/dmshirochenko/status/2107024678560616854",
     "platform": "x",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "phone-app-for-all-agent-sessions",
   "url": "https://agentsetups.dev/use-case/phone-app-for-all-agent-sessions/",
   "title": "Build your own phone remote for agent sessions",
   "summary": "Opus 5.5 one-shot an iPhone app connecting to every Claude Code and Codex session on a Mac Studio, across 3 subscriptions.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Claude",
    "Codex"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "iPhone"
   ],
   "prompt": "Goal: Control all my desktop agent sessions from my phone.\nSetup: agents used in source: Claude, Codex; tools/MCPs stated: iPhone.\nSteps:\n1. Ask the agent to build an iPhone app that connects to every Claude Code and Codex CLI session on your desktop.\n2. Make sessions started from the phone appear back on the desktop.\n3. Organise chats by project (client work, YouTube, newsletter).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Pat Simmons — https://x.com/per_simmons_/status/2107570106549071876",
   "steps": [
    "Ask the agent to build an iPhone app that connects to every Claude Code and Codex CLI session on your desktop.",
    "Make sessions started from the phone appear back on the desktop.",
    "Organise chats by project (client work, YouTube, newsletter)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-06",
   "trend_score": 21.1,
   "sources": [
    {
     "author": "Pat Simmons",
     "handle": "@per_simmons_",
     "url": "https://x.com/per_simmons_/status/2107570106549071876",
     "platform": "x",
     "date": "2026-10-06",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-personal-tidy-ups",
   "url": "https://agentsetups.dev/use-case/cowork-personal-tidy-ups/",
   "title": "Hand Claude Cowork your small personal tidy-ups",
   "summary": "@JustinTimeJLew uses Cowork to organise bookmarks and files, make mind maps for his blogs and build grocery lists.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Get time back from small organising chores.\nSetup: agents used in source: Claude.\nSteps:\n1. Ask Cowork to organise your bookmarks.\n2. Have it create a mind map for a blog.\n3. Ask for a grocery list.\n4. Have it organise your files.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: J Lew the Don 🚀 — https://x.com/JustinTimeJLew/status/2109319425069326723",
   "steps": [
    "Ask Cowork to organise your bookmarks.",
    "Have it create a mind map for a blog.",
    "Ask for a grocery list.",
    "Have it organise your files."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 20.1,
   "sources": [
    {
     "author": "J Lew the Don 🚀",
     "handle": "@JustinTimeJLew",
     "url": "https://x.com/JustinTimeJLew/status/2109319425069326723",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-cheaper-utility-plan",
   "url": "https://agentsetups.dev/use-case/dots-cheaper-utility-plan/",
   "title": "Have your Dot find a cheaper electricity plan",
   "summary": "When a renewal email arrived, a Dot suggested other plans based on actual usage, saving $20–40 a month.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Stop auto-renewing utility plans without checking alternatives.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Let the Dot watch your inbox for renewal emails.\n2. When one arrives, have it compare other plans against your actual usage history.\n3. Review and switch if it saves money.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Chill Waterson — https://x.com/ChillWaterson/status/2109322448214667530 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Let the Dot watch your inbox for renewal emails.",
    "When one arrives, have it compare other plans against your actual usage history.",
    "Review and switch if it saves money."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 20.1,
   "sources": [
    {
     "author": "Chill Waterson",
     "handle": "@ChillWaterson",
     "url": "https://x.com/ChillWaterson/status/2109322448214667530",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-cad-part-subscriptions-quotes",
   "url": "https://agentsetups.dev/use-case/grokbot-cad-part-subscriptions-quotes/",
   "title": "Let Grok Bot order a part, cut subs and shop insurance",
   "summary": "In 24h a Grok Bot used Claude Code to design and order a truck bracket, cut $180 of subscriptions and requested 10 quotes.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Claude",
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "STEP files"
   ],
   "prompt": "Goal: Offload a mix of making, money and admin tasks to my bot.\nSetup: agents used in source: Claude, Grok Bot; tools/MCPs stated: STEP files.\nSteps:\n1. Give it a sketch; have it drive Claude Code on your Mac to design the part, build the STEP file, then quote and order it through Xometry.\n2. Have it find and cancel unused subscriptions, and review charges periodically.\n3. Have it request home and auto insurance renewal quotes from ~10 agents by email, every year.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jubbs — https://x.com/JUBBAMAYNE/status/2108036870257144089",
   "steps": [
    "Give it a sketch; have it drive Claude Code on your Mac to design the part, build the STEP file, then quote and order it through Xometry.",
    "Have it find and cancel unused subscriptions, and review charges periodically.",
    "Have it request home and auto insurance renewal quotes from ~10 agents by email, every year."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 19.5,
   "sources": [
    {
     "author": "Jubbs",
     "handle": "@JUBBAMAYNE",
     "url": "https://x.com/JUBBAMAYNE/status/2108036870257144089",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-cold-email-two-bots",
   "url": "https://agentsetups.dev/use-case/grokbot-cold-email-two-bots/",
   "title": "Set up cold email with two Grok Bots and Instantly",
   "summary": "Bot 1 set up domain, Workspace and email auth; bot 2 researched Toronto businesses with weak sites; 23 leads ready.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Google Workspace",
    "Instantly"
   ],
   "prompt": "Goal: Land one new client a month with researched, personalised cold email.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Google Workspace, Instantly.\nSteps:\n1. Bot 1: buy a separate outreach domain, set up Google Workspace, configure email authentication and connect Instantly.\n2. Bot 2: research local small businesses with outdated sites, weak stores or no site; find contact emails and improvement opportunities; log it all in a spreadsheet.\n3. Bot 1 drafts personalised emails from that research.\n4. You review and approve; Instantly sends and follows up. Warm the inbox before sending 20–30 a day.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dre Voudouris — https://x.com/drevoudouriss/status/2110418743272603919",
   "steps": [
    "Bot 1: buy a separate outreach domain, set up Google Workspace, configure email authentication and connect Instantly.",
    "Bot 2: research local small businesses with outdated sites, weak stores or no site; find contact emails and improvement opportunities; log it all in a spreadsheet.",
    "Bot 1 drafts personalised emails from that research.",
    "You review and approve; Instantly sends and follows up. Warm the inbox before sending 20–30 a day."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 19.1,
   "sources": [
    {
     "author": "Dre Voudouris",
     "handle": "@drevoudouriss",
     "url": "https://x.com/drevoudouriss/status/2110418743272603919",
     "platform": "x",
     "date": "2026-10-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-physics-game-for-kids",
   "url": "https://agentsetups.dev/use-case/grokbot-physics-game-for-kids/",
   "title": "Explain a science question with a Grok Bot game",
   "summary": "Asked why a straw looks bent in water, Grok Bot built a 3D archerfish game in one HTML file that learns Snell’s law.",
   "category": "education",
   "category_label": "Education",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "HTML"
   ],
   "prompt": "Goal: Help my kids understand refraction.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: HTML.\nSteps:\n1. Ask Grok Bot the kids’ question.\n2. Ask for a playable explanation; it built a single-file 3D game where an archerfish misses, learns that water bends light (n = 1.33), aims 7.2° lower and hits.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Frank — https://x.com/Frank_AI_Lab/status/2105898453893009485",
   "steps": [
    "Ask Grok Bot the kids’ question.",
    "Ask for a playable explanation; it built a single-file 3D game where an archerfish misses, learns that water bends light (n = 1.33), aims 7.2° lower and hits."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 18.2,
   "sources": [
    {
     "author": "Frank",
     "handle": "@Frank_AI_Lab",
     "url": "https://x.com/Frank_AI_Lab/status/2105898453893009485",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "instinct-weekly-small-business-help",
   "url": "https://agentsetups.dev/use-case/instinct-weekly-small-business-help/",
   "title": "Text Instinct your weekly small-business chores",
   "summary": "One user’s Instinct scheduled X posts overnight, audited her website, drafted Reddit posts and found homeschool field trips.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Instinct"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Hand off a week of small chores by text.\nSetup: agents used in source: Instinct.\nSteps:\n1. Text the agent the chores.\n2. Examples: schedule social posts overnight, audit your website, draft Reddit posts, find homeschool field trips.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Home Sweet Alabama — https://x.com/ourhomeswtbama/status/2105823076172849520",
   "steps": [
    "Text the agent the chores.",
    "Examples: schedule social posts overnight, audit your website, draft Reddit posts, find homeschool field trips."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 18.2,
   "sources": [
    {
     "author": "Home Sweet Alabama",
     "handle": "@ourhomeswtbama",
     "url": "https://x.com/ourhomeswtbama/status/2105823076172849520",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-overnight-surprise-me",
   "url": "https://agentsetups.dev/use-case/dots-overnight-surprise-me/",
   "title": "Give your Dot an overnight brief with spending rules",
   "summary": "“Surprise me by morning,” no spending, don’t touch existing projects: 3 GitHub projects, an audited draft PR, 193 tests passed.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "GitHub",
    "Blender"
   ],
   "prompt": "Goal: See what my Dot can do unsupervised overnight.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: GitHub, Blender.\nSteps:\n1. Set the rules: spend nothing, leave existing projects alone, work all night.\n2. Say “Surprise me by morning.”\n3. Handle sign-in and permission approvals when it asks.\n4. In the morning, review the work (here 3 new GitHub projects, an independently audited draft PR, 193 targeted tests passed, 3 DevRel applications).\n5. Optional: have it visualise the night’s work (he got a Blender city).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Himanshu Jha — https://x.com/jhahimanshu653/status/2105521799178137706",
   "steps": [
    "Set the rules: spend nothing, leave existing projects alone, work all night.",
    "Say “Surprise me by morning.”",
    "Handle sign-in and permission approvals when it asks.",
    "In the morning, review the work (here 3 new GitHub projects, an independently audited draft PR, 193 targeted tests passed, 3 DevRel applications).",
    "Optional: have it visualise the night’s work (he got a Blender city)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 18.0,
   "sources": [
    {
     "author": "Himanshu Jha",
     "handle": "@jhahimanshu653",
     "url": "https://x.com/jhahimanshu653/status/2105521799178137706",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-deconflict-meetings",
   "url": "https://agentsetups.dev/use-case/grokbot-deconflict-meetings/",
   "title": "Let Grok Bot spot and fix double-booked meetings",
   "summary": "@abbyfinan’s Grok Bot flagged two conflicting customer meetings with a rundown of each, then rescheduled one.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Catch calendar conflicts before they bite.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Connect your calendar.\n2. When it flags a conflict, read its rundown (what each meeting is, who it’s with).\n3. Ask it to deconflict; it reschedules one.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: abby finan — https://x.com/abbyfinan/status/2105772495823577359",
   "steps": [
    "Connect your calendar.",
    "When it flags a conflict, read its rundown (what each meeting is, who it’s with).",
    "Ask it to deconflict; it reschedules one."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 18.0,
   "sources": [
    {
     "author": "abby finan",
     "handle": "@abbyfinan",
     "url": "https://x.com/abbyfinan/status/2105772495823577359",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "perplexity-computer-light-effort-builds",
   "url": "https://agentsetups.dev/use-case/perplexity-computer-light-effort-builds/",
   "title": "Build the rough version on Light effort to save credits",
   "summary": "Perplexity Computer built a playable flight simulator for 97 credits on Light; scale effort up only once the idea works.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Prototype with Perplexity Computer without burning credits.\nSetup: agents used in source: Perplexity Computer.\nSteps:\n1. Use the effort slider: start on Light (smaller models, much cheaper).\n2. Build the rough version first; turn effort up only once the idea works.\n3. Use Mac app tabs to research in one tab while another builds.\n4. Ask for single-file HTML outputs (e.g. an SEO calculator, a landing page) and open them in the browser.\n5. Read your prompt twice; credits don’t come back.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Julian Goldie SEO — https://x.com/JulianGoldieSEO/status/2108176289886773738",
   "steps": [
    "Use the effort slider: start on Light (smaller models, much cheaper).",
    "Build the rough version first; turn effort up only once the idea works.",
    "Use Mac app tabs to research in one tab while another builds.",
    "Ask for single-file HTML outputs (e.g. an SEO calculator, a landing page) and open them in the browser.",
    "Read your prompt twice; credits don’t come back."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 17.8,
   "sources": [
    {
     "author": "Julian Goldie SEO",
     "handle": "@JulianGoldieSEO",
     "url": "https://x.com/JulianGoldieSEO/status/2108176289886773738",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-mcp-events-notify",
   "url": "https://agentsetups.dev/use-case/dots-mcp-events-notify/",
   "title": "Notify your Dot when your app’s data changes",
   "summary": "@itsJaimeMedina added MCP Events to his app’s MCP server; the Dot watched a contact and pinged him when it changed.",
   "category": "automation-integrations",
   "category_label": "Automation & integrations",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "MCP",
    "Docker"
   ],
   "prompt": "Goal: Let my Dot react to events in my own app instead of polling.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: MCP, Docker.\nSteps:\n1. Add events to your app’s MCP server.\n2. Run a sender (here in Docker) that delivers events to ChatGPT.\n3. Ask your Dot to watch something (e.g. a contact’s company name), change it in the app and confirm you get a notification.\n4. Extend it: a failed job triggers a log review, a finished build triggers a check and summary.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Jaime Medina — https://x.com/itsJaimeMedina/status/2110073711684632616",
   "steps": [
    "Add events to your app’s MCP server.",
    "Run a sender (here in Docker) that delivers events to ChatGPT.",
    "Ask your Dot to watch something (e.g. a contact’s company name), change it in the app and confirm you get a notification.",
    "Extend it: a failed job triggers a log review, a finished build triggers a check and summary."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 16.9,
   "sources": [
    {
     "author": "Jaime Medina",
     "handle": "@itsJaimeMedina",
     "url": "https://x.com/itsJaimeMedina/status/2110073711684632616",
     "platform": "x",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-hourly-email-weekly-billing",
   "url": "https://agentsetups.dev/use-case/dots-hourly-email-weekly-billing/",
   "title": "Schedule your Dot to check email and billing claims",
   "summary": "A setup video: the Dot checks email every hour and reviews billing claims every Friday, reporting back in one chat.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Put my Dot on a recurring schedule for inbox and billing checks.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Set an hourly schedule for the Dot to check email.\n2. Set a weekly (Friday) task to review billing claims.\n3. Have both report back in a single chat.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dylan Normandin — https://x.com/DNormandin1234/status/2109373745081077971 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Set an hourly schedule for the Dot to check email.",
    "Set a weekly (Friday) task to review billing claims.",
    "Have both report back in a single chat."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 16.5,
   "sources": [
    {
     "author": "Dylan Normandin",
     "handle": "@DNormandin1234",
     "url": "https://x.com/DNormandin1234/status/2109373745081077971",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-stealable-routines",
   "url": "https://agentsetups.dev/use-case/grokbot-stealable-routines/",
   "title": "Run four Grok Bot routines, including a bot that checks bots",
   "summary": "Midnight: one bot checks the others and suggests fixes; 8am weekdays inbox triage (advice only); daily LinkedIn post; Monday review.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "LinkedIn"
   ],
   "prompt": "Goal: Set up a small routine system with Grok Bot.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: LinkedIn.\nSteps:\n1. Midnight: one bot checks your other bots and suggests fixes.\n2. 08:00 weekdays: inbox triage, advice only.\n3. Every morning: your LinkedIn post goes out.\n4. Mondays: weekly review of last week’s posts.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Eyad Kelleh — https://x.com/KellehEyad/status/2108505265880371670",
   "steps": [
    "Midnight: one bot checks your other bots and suggests fixes.",
    "08:00 weekdays: inbox triage, advice only.",
    "Every morning: your LinkedIn post goes out.",
    "Mondays: weekly review of last week’s posts."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 16.1,
   "sources": [
    {
     "author": "Eyad Kelleh",
     "handle": "@KellehEyad",
     "url": "https://x.com/KellehEyad/status/2108505265880371670",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-runs-fantasy-football",
   "url": "https://agentsetups.dev/use-case/grokbot-runs-fantasy-football/",
   "title": "Hand your fantasy football team to Grok Bot",
   "summary": "It drafted live, sets the lineup each morning, files waivers, swaps injured players before kickoff and only messages on changes.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Manage my fantasy team without opening the app.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Have Grok Bot draft live for you.\n2. Each morning it sets the lineup and files waivers.\n3. Before kickoff it swaps out injured players.\n4. It only messages you when something changes.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Dean Young — https://x.com/Dean_Y0ung/status/2108036174417965538",
   "steps": [
    "Have Grok Bot draft live for you.",
    "Each morning it sets the lineup and files waivers.",
    "Before kickoff it swaps out injured players.",
    "It only messages you when something changes."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 15.9,
   "sources": [
    {
     "author": "Dean Young",
     "handle": "@Dean_Y0ung",
     "url": "https://x.com/Dean_Y0ung/status/2108036174417965538",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-landlord-lease-signing",
   "url": "https://agentsetups.dev/use-case/grokbot-landlord-lease-signing/",
   "title": "Have Grok Bot draft and send a lease for signing",
   "summary": "Grok Bot logged into a rental-management site, drafted a lease with the requested terms, and both tenants signed it overnight.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "rental management website",
    "email"
   ],
   "prompt": "Goal: Handle a rental lease without a property manager.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: rental management website, email.\nSteps:\n1. Give Grok Bot the lease terms in a prompt.\n2. Let it log into your rental-management website and generate the agreement with signature boxes.\n3. Have it email it to the tenants with a friendly message (it can schedule the send).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Joseph R. Nosef — https://x.com/jrnosef/status/2110567718734709023",
   "steps": [
    "Give Grok Bot the lease terms in a prompt.",
    "Let it log into your rental-management website and generate the agreement with signature boxes.",
    "Have it email it to the tenants with a friendly message (it can schedule the send)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 14.9,
   "sources": [
    {
     "author": "Joseph R. Nosef",
     "handle": "@jrnosef",
     "url": "https://x.com/jrnosef/status/2110567718734709023",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-review-seller-disclosures",
   "url": "https://agentsetups.dev/use-case/grokbot-review-seller-disclosures/",
   "title": "Give Grok Bot the seller disclosures first",
   "summary": "A Bay Area house hunter gives Grok Bot each seller-disclosure packet first; he says it finds more than his agent and lawyer.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Catch issues in a home’s disclosure documents early.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Upload the seller disclosures to your bot before anything else.\n2. Ask it to flag issues, then take its findings to your agent or lawyer.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: nick — https://x.com/thecsguy/status/2110586525427876259 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Upload the seller disclosures to your bot before anything else.",
    "Ask it to flag issues, then take its findings to your agent or lawyer."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 14.9,
   "sources": [
    {
     "author": "nick",
     "handle": "@thecsguy",
     "url": "https://x.com/thecsguy/status/2110586525427876259",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-research-with-folder-and-chrome",
   "url": "https://agentsetups.dev/use-case/cowork-research-with-folder-and-chrome/",
   "title": "Do research with Claude Cowork driving data portals",
   "summary": "Link a real folder, let Cowork drive Chrome to pull MAST and ExoFOP data, and give it computer access to run the analysis.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Chrome",
    "MAST",
    "ExoFOP"
   ],
   "prompt": "Goal: Run an astronomy research project with Claude Cowork.\nSetup: agents used in source: Claude; tools/MCPs stated: Chrome, MAST, ExoFOP.\nSteps:\n1. Link a real project folder on your PC to Cowork.\n2. Let it drive Chrome to fetch data from archives (MAST, ExoFOP).\n3. Give it computer access to run the analysis code.\n4. Talk to it like a coworker, or hand it a /goal.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: samsonfraser — https://x.com/samsonfraser_/status/2108580741873561993 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Link a real project folder on your PC to Cowork.",
    "Let it drive Chrome to fetch data from archives (MAST, ExoFOP).",
    "Give it computer access to run the analysis code.",
    "Talk to it like a coworker, or hand it a /goal."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 13.8,
   "sources": [
    {
     "author": "samsonfraser",
     "handle": "@samsonfraser_",
     "url": "https://x.com/samsonfraser_/status/2108580741873561993",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "opencode-reviews-dictated-daily-note",
   "url": "https://agentsetups.dev/use-case/opencode-reviews-dictated-daily-note/",
   "title": "Ramble into a daily note, let OpenCode make sense of it",
   "summary": "Dictate unfiltered thoughts into an Obsidian daily note all day; each evening OpenCode extracts tasks, summarises and sets goals.",
   "category": "knowledge-memory",
   "category_label": "Knowledge & memory",
   "agents": [
    "OpenCode"
   ],
   "models": [],
   "tools": [
    "Obsidian"
   ],
   "prompt": "Goal: Get the benefit of time tracking without the tracking.\nSetup: agents used in source: OpenCode; tools/MCPs stated: Obsidian.\nSteps:\n1. Through the day, dictate whatever you are doing or thinking into your Obsidian daily note.\n2. At the end of each day, have OpenCode read the daily note from the vault.\n3. Have it extract tasks, summarise your thoughts and set goals for tomorrow.\n4. Over weeks, use the notes to build a personal charter or a tag-based heatmap of your time.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Billy-Fong-2007 — https://www.reddit.com/r/ObsidianMD/comments/1x5k75t/rambling_into_obsidian_daily_note_is_the_best/",
   "steps": [
    "Through the day, dictate whatever you are doing or thinking into your Obsidian daily note.",
    "At the end of each day, have OpenCode read the daily note from the vault.",
    "Have it extract tasks, summarise your thoughts and set goals for tomorrow.",
    "Over weeks, use the notes to build a personal charter or a tag-based heatmap of your time."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-14",
   "trend_score": 13.6,
   "sources": [
    {
     "author": "/u/Billy-Fong-2007",
     "handle": "/u/Billy-Fong-2007",
     "url": "https://www.reddit.com/r/ObsidianMD/comments/1x5k75t/rambling_into_obsidian_daily_note_is_the_best/",
     "platform": "reddit",
     "date": "2026-10-14",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-patches-1991-dos-game",
   "url": "https://agentsetups.dev/use-case/claude-patches-1991-dos-game/",
   "title": "Have Claude patch an old game that won’t run",
   "summary": "Given the 1991 game’s binaries and the symptoms, Claude disassembled it, found a sound-card handshake that hangs, and wrote a 3-byte patch.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "FreeDOS"
   ],
   "prompt": "Goal: Get a retro game running on real old hardware.\nSetup: agents used in source: Claude; tools/MCPs stated: FreeDOS.\nSteps:\n1. Give Claude the original binaries and a description of the problem.\n2. Let it disassemble the executable, trace execution and identify the likely root cause.\n3. Have it apply the patch to a new copy (keep the original) and test on the real machine.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/jrowberg — https://www.reddit.com/r/ClaudeAI/comments/1x06hmp/claude_fixed_a_bug_in_a_dos_game_from_1991_and/",
   "steps": [
    "Give Claude the original binaries and a description of the problem.",
    "Let it disassemble the executable, trace execution and identify the likely root cause.",
    "Have it apply the patch to a new copy (keep the original) and test on the real machine."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 13.5,
   "sources": [
    {
     "author": "/u/jrowberg",
     "handle": "/u/jrowberg",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1x06hmp/claude_fixed_a_bug_in_a_dos_game_from_1991_and/",
     "platform": "reddit",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "pixel-dungeon-agent-monitor",
   "url": "https://agentsetups.dev/use-case/pixel-dungeon-agent-monitor/",
   "title": "Watch all your coding agents in one pixel-art dungeon",
   "summary": "Each Claude Code, Codex, Kiro or Gemini CLI session is a hero in its project’s room; click to see the console and answer prompts.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex",
    "Kiro",
    "Gemini CLI"
   ],
   "models": [],
   "tools": [
    "Herdr"
   ],
   "prompt": "Goal: See at a glance which of my agents is waiting for me.\nSetup: agents used in source: Claude, Codex, Kiro, Gemini CLI; tools/MCPs stated: Herdr.\nSteps:\n1. Run your agents through Herdr so the app can listen to their events (or use the read-only fallback).\n2. Give each project a room and each harness its own hero.\n3. Click a room to see the live console, answer a prompt or permission request, or stop the agent.\n4. Open the full-screen view for changed files, diffs and the branch’s PR.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/NachoV125 — https://www.reddit.com/r/LLMDevs/comments/1x58qog/i_made_a_pixelart_dungeon_to_keep_an_eye_on_all/",
   "steps": [
    "Run your agents through Herdr so the app can listen to their events (or use the read-only fallback).",
    "Give each project a room and each harness its own hero.",
    "Click a room to see the live console, answer a prompt or permission request, or stop the agent.",
    "Open the full-screen view for changed files, diffs and the branch’s PR."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 13.3,
   "sources": [
    {
     "author": "/u/NachoV125",
     "handle": "/u/NachoV125",
     "url": "https://www.reddit.com/r/LLMDevs/comments/1x58qog/i_made_a_pixelart_dungeon_to_keep_an_eye_on_all/",
     "platform": "reddit",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-printed-morning-paper",
   "url": "https://agentsetups.dev/use-case/grokbot-printed-morning-paper/",
   "title": "Get a printed personal morning paper from Grok Bot",
   "summary": "Users have Grok Bot research and print a daily paper (appointments, weather, chosen headlines) or a commute audio brief.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Start the day with a briefing without staring at a screen.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Tell Grok Bot what to include: your appointments, the weather, the headlines you care about.\n2. Have it research and write it every morning.\n3. Have it print it (or deliver audio for your commute).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Michael Lee — https://x.com/tamerton/status/2107753044729352358 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Tell Grok Bot what to include: your appointments, the weather, the headlines you care about.",
    "Have it research and write it every morning.",
    "Have it print it (or deliver audio for your commute)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 13.2,
   "sources": [
    {
     "author": "Michael Lee",
     "handle": "@tamerton",
     "url": "https://x.com/tamerton/status/2107753044729352358",
     "platform": "x",
     "date": "2026-10-07",
     "primary": true
    },
    {
     "author": "T K",
     "handle": "@TKozzer",
     "url": "https://x.com/TKozzer/status/2108565838961705202",
     "platform": "x",
     "date": "2026-10-09",
     "primary": false
    },
    {
     "author": "Padjen",
     "handle": "@padjen",
     "url": "https://x.com/padjen/status/2107390788351172934",
     "platform": "x",
     "date": "2026-10-06",
     "primary": false
    }
   ]
  },
  {
   "slug": "chatgpt-agent-comedy-show-alerts",
   "url": "https://agentsetups.dev/use-case/chatgpt-agent-comedy-show-alerts/",
   "title": "Get alerted to surprise comedy shows with ChatGPT agent",
   "summary": "After missing a surprise show, a fan built a ChatGPT agent that checks ticket sites hourly and sends push + email alerts.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT agent"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Never miss a surprise show by a favourite comedian again.\nSetup: agents used in source: ChatGPT agent.\nSteps:\n1. Have the agent check ticket sites and comedy clubs every hour.\n2. Send push and email alerts when a new show appears.\n3. Run it 24/7 in the cloud, not on your laptop.\n4. Add a weekly health check so you know it’s still working.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Brian Moseley — https://x.com/bmose14/status/2109293515217990112",
   "steps": [
    "Have the agent check ticket sites and comedy clubs every hour.",
    "Send push and email alerts when a new show appears.",
    "Run it 24/7 in the cloud, not on your laptop.",
    "Add a weekly health check so you know it’s still working."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 12.8,
   "sources": [
    {
     "author": "Brian Moseley",
     "handle": "@bmose14",
     "url": "https://x.com/bmose14/status/2109293515217990112",
     "platform": "x",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "minecraft-mod-claude-builds",
   "url": "https://agentsetups.dev/use-case/minecraft-mod-claude-builds/",
   "title": "Have Claude Code build in Minecraft as you play",
   "summary": "Press K, describe a build (“a medieval castle with a moat”) and a mod drives your own Claude Code through 20 in-game tools; one click…",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Minecraft Java",
    "Fabric/Forge/NeoForge"
   ],
   "prompt": "Goal: Build big structures in Minecraft by describing them.\nSetup: agents used in source: Claude; tools/MCPs stated: Minecraft Java, Fabric/Forge/NeoForge.\nSteps:\n1. Install Claude Code (Pro or Max) plus Minecraft Java and the free mod jar.\n2. In game, press K and describe what you want built.\n3. Keep playing while it builds through the mod’s in-game tools; undo with one click if you don’t like it.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: Beta; the author’s biggest timed build was a 34k-block castle in about 15 minutes.\nBased on: /u/DutyOnly4308 — https://www.reddit.com/r/ClaudeAI/comments/1x3olix/i_made_a_free_minecraft_mod_where_claude_builds/",
   "steps": [
    "Install Claude Code (Pro or Max) plus Minecraft Java and the free mod jar.",
    "In game, press K and describe what you want built.",
    "Keep playing while it builds through the mod’s in-game tools; undo with one click if you don’t like it."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 12.8,
   "sources": [
    {
     "author": "/u/DutyOnly4308",
     "handle": "/u/DutyOnly4308",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1x3olix/i_made_a_free_minecraft_mod_where_claude_builds/",
     "platform": "reddit",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-self-maintaining-config",
   "url": "https://agentsetups.dev/use-case/hermes-self-maintaining-config/",
   "title": "Keep a Hermes agent from rotting for six months",
   "summary": "Tiny memory file, an Obsidian reference vault, scheduled skill pruning, a nightly dream loop and LLM-free daily backups.",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Obsidian",
    "cron",
    "SQLite"
   ],
   "prompt": "Goal: Run one long-lived agent without starting fresh every few weeks.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Obsidian, cron, SQLite.\nSteps:\n1. Keep the memory file at the default tiny size; first line: “Memory = only facts relevant to all conversations. Everything else → vault/skills.”\n2. Keep an indexed reference/ folder in an Obsidian vault (one doc per system) as the shared source of truth; offload to it when memory hits ~75%.\n3. Schedule skill pruning; deletions must declare what absorbed the content, pinned skills can be patched but not deleted.\n4. Run a nightly dream job with a restricted toolset: review the day’s sessions, self-critique, write a dream log and insights file, audit skills, triage memory.\n5. Back up daily/weekly/monthly with a no-agent cron script: WAL checkpoint before copying SQLite, verify integrity, include restore instructions.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/ct06033 — https://www.reddit.com/r/hermesagent/comments/1x24qfp/my_hermes_configuration_that_works_for_me/",
   "steps": [
    "Keep the memory file at the default tiny size; first line: “Memory = only facts relevant to all conversations. Everything else → vault/skills.”",
    "Keep an indexed reference/ folder in an Obsidian vault (one doc per system) as the shared source of truth; offload to it when memory hits ~75%.",
    "Schedule skill pruning; deletions must declare what absorbed the content, pinned skills can be patched but not deleted.",
    "Run a nightly dream job with a restricted toolset: review the day’s sessions, self-critique, write a dream log and insights file, audit skills, triage memory.",
    "Back up daily/weekly/monthly with a no-agent cron script: WAL checkpoint before copying SQLite, verify integrity, include restore instructions."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 12.7,
   "sources": [
    {
     "author": "/u/ct06033",
     "handle": "/u/ct06033",
     "url": "https://www.reddit.com/r/hermesagent/comments/1x24qfp/my_hermes_configuration_that_works_for_me/",
     "platform": "reddit",
     "date": "2026-10-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-24-7-pixel-news-network",
   "url": "https://agentsetups.dev/use-case/claude-code-24-7-pixel-news-network/",
   "title": "Build a 24/7 AI news channel with fact checks",
   "summary": "Claude Code built a pixel-art news network: scripted segments from ~70 feeds, numbers checked against source data, and a token budget.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5",
    "Haiku",
    "Sonnet"
   ],
   "tools": [
    "Suno"
   ],
   "prompt": "Goal: Run an always-on AI broadcast that doesn’t make things up about real people.\nSetup: agents used in source: Claude; tools/MCPs stated: Suno.\nSteps:\n1. Have the model write every segment as a structured script; voice, time and place each line in one shared broadcast timeline.\n2. Check every price, number or statistic against the data the model was given; rewrite or kill lines that don’t match.\n3. Keep a sourced research library and have another agent fact-check facts before they are added.\n4. Put a budget around it: nothing gets written if nobody is watching; use a cheap model for routine dialogue.\n5. Run automated checks before every push.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Icy_Upstairs_7328 — https://www.reddit.com/r/ClaudeCode/comments/1wvkje5/hey_opus_55_can_you_build_me_a_news_network_that/",
   "steps": [
    "Have the model write every segment as a structured script; voice, time and place each line in one shared broadcast timeline.",
    "Check every price, number or statistic against the data the model was given; rewrite or kill lines that don’t match.",
    "Keep a sourced research library and have another agent fact-check facts before they are added.",
    "Put a budget around it: nothing gets written if nobody is watching; use a cheap model for routine dialogue.",
    "Run automated checks before every push."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 12.2,
   "sources": [
    {
     "author": "/u/Icy_Upstairs_7328",
     "handle": "/u/Icy_Upstairs_7328",
     "url": "https://www.reddit.com/r/ClaudeCode/comments/1wvkje5/hey_opus_55_can_you_build_me_a_news_network_that/",
     "platform": "reddit",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-invoice-inbox-to-sheet",
   "url": "https://agentsetups.dev/use-case/n8n-invoice-inbox-to-sheet/",
   "title": "Auto-log every emailed invoice into a sheet",
   "summary": "Watches a billing@ inbox, classifies and extracts invoice fields in one call, dedupes on invoice number, logs to Sheets and pings Telegram.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "Gmail",
    "Google Sheets",
    "Telegram"
   ],
   "prompt": "Goal: Never type an invoice into a spreadsheet again at tax time.\nSetup: agents used in source: n8n; tools/MCPs stated: Gmail, Google Sheets, Telegram.\nSteps:\n1. Point the workflow at one billing@ address and forward invoices from other addresses there.\n2. Watch Gmail for unread emails with attachments and filter out junk files.\n3. Classify “is this an invoice?” and extract the fields in the same call.\n4. Look the invoice number up in the sheet before appending, so re-sends never create duplicates.\n5. Append new invoices to Google Sheets and send a Telegram alert for each.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/easybits_ai — https://www.reddit.com/r/n8n/comments/1wuxey9/tax_season_is_coming_the_n8n_workflow_i_built_to/",
   "steps": [
    "Point the workflow at one billing@ address and forward invoices from other addresses there.",
    "Watch Gmail for unread emails with attachments and filter out junk files.",
    "Classify “is this an invoice?” and extract the fields in the same call.",
    "Look the invoice number up in the sheet before appending, so re-sends never create duplicates.",
    "Append new invoices to Google Sheets and send a Telegram alert for each."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 12.1,
   "sources": [
    {
     "author": "/u/easybits_ai",
     "handle": "/u/easybits_ai",
     "url": "https://www.reddit.com/r/n8n/comments/1wuxey9/tax_season_is_coming_the_n8n_workflow_i_built_to/",
     "platform": "reddit",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-bubblegum-pop-music-video",
   "url": "https://agentsetups.dev/use-case/claude-bubblegum-pop-music-video/",
   "title": "Make a music video with Claude, Suno and Remotion",
   "summary": "Claude polished the lyrics and style, Suno made the song, and Opus built the video in Remotion plus an app to fix word timings by hand.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Suno",
    "Remotion"
   ],
   "prompt": "Goal: Make a finished music video in a couple of days.\nSetup: agents used in source: Claude; tools/MCPs stated: Suno, Remotion.\nSteps:\n1. Write rough lyrics and the vibe; have Claude turn them into real lyrics and pick a style.\n2. Generate the song in Suno (here about 20 generations).\n3. Have Opus build the video in JS with Remotion.\n4. When timings are off, have it build a small app so you can adjust word and beat timings by hand.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/pizzaisprettyneato — https://www.reddit.com/r/vibecoding/comments/1x4agp8/i_had_claude_make_a_bubblegum_pop_music_video/",
   "steps": [
    "Write rough lyrics and the vibe; have Claude turn them into real lyrics and pick a style.",
    "Generate the song in Suno (here about 20 generations).",
    "Have Opus build the video in JS with Remotion.",
    "When timings are off, have it build a small app so you can adjust word and beat timings by hand."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 11.9,
   "sources": [
    {
     "author": "/u/pizzaisprettyneato",
     "handle": "/u/pizzaisprettyneato",
     "url": "https://www.reddit.com/r/vibecoding/comments/1x4agp8/i_had_claude_make_a_bubblegum_pop_music_video/",
     "platform": "reddit",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-czech-investment-tax-bot",
   "url": "https://agentsetups.dev/use-case/n8n-czech-investment-tax-bot/",
   "title": "Calculate your investment taxes from broker CSVs",
   "summary": "Send a broker CSV to a Telegram bot; n8n matches lots FIFO, applies the Czech 3-year rule with ČNB rates and answers /sell, /report.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "Telegram",
    "n8n Data Tables"
   ],
   "prompt": "Goal: Know the tax impact of a sale before I make it.\nSetup: agents used in source: n8n; tools/MCPs stated: Telegram, n8n Data Tables.\nSteps:\n1. Send the broker CSV (Trading 212 or IBKR) to a Telegram bot backed by self-hosted n8n.\n2. On import, check for duplicate files and overlapping statement periods, then parse the broker format.\n3. Match every sell to buy lots FIFO, run the 3-year test per lot, convert at the ČNB rate of the day (cached).\n4. Write results only at the very end so a failed run writes nothing.\n5. Use commands: /sell for a planned sale, /report for the year, /dap for tax-return grouping, /export for evidence.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nNote: Not tax advice; the author’s own tool.\nBased on: /u/MiveClor — https://www.reddit.com/r/n8n/comments/1x52mx6/i_built_a_telegram_bot_in_n8n_that_calculates_my/",
   "steps": [
    "Send the broker CSV (Trading 212 or IBKR) to a Telegram bot backed by self-hosted n8n.",
    "On import, check for duplicate files and overlapping statement periods, then parse the broker format.",
    "Match every sell to buy lots FIFO, run the 3-year test per lot, convert at the ČNB rate of the day (cached).",
    "Write results only at the very end so a failed run writes nothing.",
    "Use commands: /sell for a planned sale, /report for the year, /dap for tax-return grouping, /export for evidence."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 11.8,
   "sources": [
    {
     "author": "/u/MiveClor",
     "handle": "/u/MiveClor",
     "url": "https://www.reddit.com/r/n8n/comments/1x52mx6/i_built_a_telegram_bot_in_n8n_that_calculates_my/",
     "platform": "reddit",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-skill-biology-figures",
   "url": "https://agentsetups.dev/use-case/claude-code-skill-biology-figures/",
   "title": "Generate interactive, sourced biology figures",
   "summary": "A Claude Code skill researches the mechanism, builds SVG geometry, adds interaction and verifies it, with citations for numeric claims.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Anima skill",
    "SVG",
    "WebGL"
   ],
   "prompt": "Goal: Explain a biological mechanism with an interactive figure instead of a static image.\nSetup: agents used in source: Claude; tools/MCPs stated: Anima skill, SVG, WebGL.\nSteps:\n1. Install the Anima skill in Claude Code.\n2. Ask in plain language, e.g. compare how cocaine and amphetamine affect dopamine transport.\n3. Let the agent research the mechanism, identify structures, build isometric SVG geometry, add interaction and verify the result.\n4. Check the citations it adds for numerical claims and its notes on uncertainty; it is not a guarantee of correctness.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/zealshama — https://www.reddit.com/r/LLMDevs/comments/1x578yw/i_built_an_opensource_claude_code_skill_that/",
   "steps": [
    "Install the Anima skill in Claude Code.",
    "Ask in plain language, e.g. compare how cocaine and amphetamine affect dopamine transport.",
    "Let the agent research the mechanism, identify structures, build isometric SVG geometry, add interaction and verify the result.",
    "Check the citations it adds for numerical claims and its notes on uncertainty; it is not a guarantee of correctness."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 11.1,
   "sources": [
    {
     "author": "/u/zealshama",
     "handle": "/u/zealshama",
     "url": "https://www.reddit.com/r/LLMDevs/comments/1x578yw/i_built_an_opensource_claude_code_skill_that/",
     "platform": "reddit",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "n8n-form-ugc-ad-builder",
   "url": "https://agentsetups.dev/use-case/n8n-form-ugc-ad-builder/",
   "title": "Build a click-through UGC video ad maker in n8n",
   "summary": "One n8n workflow driven by Form pages: pick a presenter, voice, product shots and best takes; it upscales and joins them into a 1080p ad.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "n8n"
   ],
   "models": [],
   "tools": [
    "n8n Forms"
   ],
   "prompt": "Goal: Let a non-technical person make a UGC-style video ad by clicking through forms.\nSetup: agents used in source: n8n; tools/MCPs stated: n8n Forms.\nSteps:\n1. Build one n8n workflow driven entirely by Form pages, so the user only opens one form URL.\n2. Ask for counts first (products, intro yes/no) so the next page shows exactly that many fields.\n3. Generate options at each step (4 presenters, 4 voice previews, product views, scenes) and show a \"use / re-roll with a note\" page before anything is paid for.\n4. Film one clip per product with several takes; let the user pick the best take per clip.\n5. Upscale the picked takes and join them into a 1080p MP4.\n6. Carry state in one $json.state object through every node so a re-roll keeps earlier choices.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/useapi_net — https://www.reddit.com/r/n8n/comments/1wx2q9k/i_built_a_multipage_n8n_form_app_that_makes_ugc/",
   "steps": [
    "Build one n8n workflow driven entirely by Form pages, so the user only opens one form URL.",
    "Ask for counts first (products, intro yes/no) so the next page shows exactly that many fields.",
    "Generate options at each step (4 presenters, 4 voice previews, product views, scenes) and show a \"use / re-roll with a note\" page before anything is paid for.",
    "Film one clip per product with several takes; let the user pick the best take per clip.",
    "Upscale the picked takes and join them into a 1080p MP4.",
    "Carry state in one $json.state object through every node so a re-roll keeps earlier choices."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 10.8,
   "sources": [
    {
     "author": "/u/useapi_net",
     "handle": "/u/useapi_net",
     "url": "https://www.reddit.com/r/n8n/comments/1wx2q9k/i_built_a_multipage_n8n_form_app_that_makes_ugc/",
     "platform": "reddit",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-fix-printer-scan-button",
   "url": "https://agentsetups.dev/use-case/cowork-fix-printer-scan-button/",
   "title": "Have Claude Cowork fix a years-old printer issue",
   "summary": "Cowork got a 10-year-old printer’s “scan to computer” button working again after years of failed manual attempts.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Fix a device feature that stopped working years ago.\nSetup: agents used in source: Claude.\nSteps:\n1. Describe the symptom to Cowork (e.g. the printer’s scan-to-computer button does nothing).\n2. Let it investigate settings and drivers on the Mac and apply the fix.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Arpit Agarwal — https://x.com/arpitagarwal1/status/2108065673566122051 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Describe the symptom to Cowork (e.g. the printer’s scan-to-computer button does nothing).",
    "Let it investigate settings and drivers on the Mac and apply the fix."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 10.7,
   "sources": [
    {
     "author": "Arpit Agarwal",
     "handle": "@arpitagarwal1",
     "url": "https://x.com/arpitagarwal1/status/2108065673566122051",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-watch-baseball-for-you",
   "url": "https://agentsetups.dev/use-case/grokbot-watch-baseball-for-you/",
   "title": "Have Grok Bot watch the game and ping key moments",
   "summary": "It pings when a playoff game reaches the 4th inning, on every score and at the final, and sends the day’s schedule each morning.",
   "category": "personal-life",
   "category_label": "Personal life",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Follow games without watching the whole thing.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Tell Grok Bot your teams and which moments matter.\n2. Have it ping you at the 4th inning, on every score and at the final.\n3. Have it send the day’s schedule every morning.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: I’m Still …. Southern Living — https://x.com/SouthernLvg/status/2108045118620021176",
   "steps": [
    "Tell Grok Bot your teams and which moments matter.",
    "Have it ping you at the 4th inning, on every score and at the final.",
    "Have it send the day’s schedule every morning."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 10.7,
   "sources": [
    {
     "author": "I’m Still …. Southern Living",
     "handle": "@SouthernLvg",
     "url": "https://x.com/SouthernLvg/status/2108045118620021176",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "openclaw-translate-family-whatsapp",
   "url": "https://agentsetups.dev/use-case/openclaw-translate-family-whatsapp/",
   "title": "Translate the WhatsApp groups your family relies on",
   "summary": "An OpenClaw plugin translates chosen Hebrew groups (voice notes, photos of notices) into Russian digests on Telegram. It never writes back.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "OpenClaw"
   ],
   "models": [],
   "tools": [
    "WhatsApp",
    "Telegram"
   ],
   "prompt": "Goal: Never miss a kindergarten or building announcement in a language I can’t read.\nSetup: agents used in source: OpenClaw; tools/MCPs stated: WhatsApp, Telegram.\nSteps:\n1. Run your own OpenClaw gateway with WhatsApp linked as a device and a Telegram bot as the destination.\n2. Pick the groups to watch; give each its own destination chat and glossary of names.\n3. Transcribe and translate voice notes; lift text off photos of notices while keeping tables as tables.\n4. Batch messages into digests instead of one notification per line.\n5. Never write into WhatsApp and don’t let the assistant act on those chats, so planted instructions can’t run anything.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/SleepEnvironmental62 — https://www.reddit.com/r/openclaw/comments/1wwtudl/i_dont_read_hebrew_so_i_built_a_plugin_that/",
   "steps": [
    "Run your own OpenClaw gateway with WhatsApp linked as a device and a Telegram bot as the destination.",
    "Pick the groups to watch; give each its own destination chat and glossary of names.",
    "Transcribe and translate voice notes; lift text off photos of notices while keeping tables as tables.",
    "Batch messages into digests instead of one notification per line.",
    "Never write into WhatsApp and don’t let the assistant act on those chats, so planted instructions can’t run anything."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 10.6,
   "sources": [
    {
     "author": "/u/SleepEnvironmental62",
     "handle": "/u/SleepEnvironmental62",
     "url": "https://www.reddit.com/r/openclaw/comments/1wwtudl/i_dont_read_hebrew_so_i_built_a_plugin_that/",
     "platform": "reddit",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "muse-dashboard-replaces-codex-apps",
   "url": "https://agentsetups.dev/use-case/muse-dashboard-replaces-codex-apps/",
   "title": "Replace hand-built dashboards with a Meta Muse one",
   "summary": "A user retired his Codex-built custom apps for a Meta Muse dashboard with screens, alerts, news events and charts.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Meta Muse"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Stop maintaining my own custom tracking apps.\nSetup: agents used in source: Meta Muse.\nSteps:\n1. Ask the Meta Muse app for a dashboard with your screens, alerts, news events and charts.\n2. Retire the custom apps it replaces.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Will Kriski — https://x.com/willkriski/status/2107192560989110429 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Ask the Meta Muse app for a dashboard with your screens, alerts, news events and charts.",
    "Retire the custom apps it replaces."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 10.2,
   "sources": [
    {
     "author": "Will Kriski",
     "handle": "@willkriski",
     "url": "https://x.com/willkriski/status/2107192560989110429",
     "platform": "x",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-ux-review-web-app",
   "url": "https://agentsetups.dev/use-case/dots-ux-review-web-app/",
   "title": "Have your Dot review your app’s UX and apply fixes",
   "summary": "Unprompted, a Dot offered a first-time-user review of a web app, then made the changes with before/after views for approval.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Improve my web app’s UX with my personal agent.\nSetup: agents used in source: ChatGPT Dots.\nSteps:\n1. Ask your Dot to review the app from a first-time user’s perspective and rank the highest-impact UX fixes.\n2. Ask it to make the changes and show before/after comparisons.\n3. Review everything before publishing.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Isabella — https://x.com/isabellasyan/status/2106450829477884349",
   "steps": [
    "Ask your Dot to review the app from a first-time user’s perspective and rank the highest-impact UX fixes.",
    "Ask it to make the changes and show before/after comparisons.",
    "Review everything before publishing."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-03",
   "trend_score": 9.9,
   "sources": [
    {
     "author": "Isabella",
     "handle": "@isabellasyan",
     "url": "https://x.com/isabellasyan/status/2106450829477884349",
     "platform": "x",
     "date": "2026-10-03",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-native-tv-plex-client",
   "url": "https://agentsetups.dev/use-case/claude-code-native-tv-plex-client/",
   "title": "Reverse-engineer a TV to build a faster native app",
   "summary": "With Ghidra and Claude Code, an iOS dev built a native Plex client for a 2019 LG TV: profile picker in ~3 s instead of ~30 s.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus"
   ],
   "tools": [
    "Ghidra",
    "Rust",
    "OpenGL"
   ],
   "prompt": "Goal: Replace a slow official TV app with a native one.\nSetup: agents used in source: Claude; tools/MCPs stated: Ghidra, Rust, OpenGL.\nSteps:\n1. On a development TV, pull the native libraries and open them in Ghidra.\n2. Ask the model to work out how things are implemented, navigating addresses, xrefs and strings; trust the binary and real hardware over its claims.\n3. Prove the hard part first (a real video frame on the hardware video plane) before building the app.\n4. Watch for code that compiles but breaks elsewhere when agents refactor (memory and ownership).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Purple_Imagination_1 — https://www.reddit.com/r/ClaudeCode/comments/1x043yp/i_used_claude_code_to_reverseengineer_an_lg_tv/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "On a development TV, pull the native libraries and open them in Ghidra.",
    "Ask the model to work out how things are implemented, navigating addresses, xrefs and strings; trust the binary and real hardware over its claims.",
    "Prove the hard part first (a real video frame on the hardware video plane) before building the app.",
    "Watch for code that compiles but breaks elsewhere when agents refactor (memory and ownership)."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 9.8,
   "sources": [
    {
     "author": "/u/Purple_Imagination_1",
     "handle": "/u/Purple_Imagination_1",
     "url": "https://www.reddit.com/r/ClaudeCode/comments/1x043yp/i_used_claude_code_to_reverseengineer_an_lg_tv/",
     "platform": "reddit",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "openclaw-face-and-voice-iphone",
   "url": "https://agentsetups.dev/use-case/openclaw-face-and-voice-iphone/",
   "title": "Give your OpenClaw agent a face and voice on iPhone",
   "summary": "An iPhone app is only the face and voice of your own OpenClaw gateway on a Mac, over Tailscale, with lip-sync and hands-free talk.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "OpenClaw"
   ],
   "models": [],
   "tools": [
    "Tailscale",
    "iPhone"
   ],
   "prompt": "Goal: Talk to my own agent hands-free, like a person.\nSetup: agents used in source: OpenClaw; tools/MCPs stated: Tailscale, iPhone.\nSteps:\n1. Keep the OpenClaw gateway on your own Mac.\n2. Connect the phone app over your Tailscale network and approve its device key once.\n3. Use the gateway’s text-to-speech for the voice; the app lip-syncs from the text.\n4. Talk, pause, and it sends; it listens again after each reply.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Sweaty_Ad_6152 — https://www.reddit.com/r/openclaw/comments/1x3wyq9/i_gave_my_openclaw_agent_a_face_and_a_voice_on/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Keep the OpenClaw gateway on your own Mac.",
    "Connect the phone app over your Tailscale network and approve its device key once.",
    "Use the gateway’s text-to-speech for the voice; the app lip-syncs from the text.",
    "Talk, pause, and it sends; it listens again after each reply."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 9.5,
   "sources": [
    {
     "author": "/u/Sweaty_Ad_6152",
     "handle": "/u/Sweaty_Ad_6152",
     "url": "https://www.reddit.com/r/openclaw/comments/1x3wyq9/i_gave_my_openclaw_agent_a_face_and_a_voice_on/",
     "platform": "reddit",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "student-proves-geometry-conjecture",
   "url": "https://agentsetups.dev/use-case/student-proves-geometry-conjecture/",
   "title": "Work with Claude to prove a geometry conjecture",
   "summary": "A 9th grader and Claude proved the rhombicosidodecahedron can’t pass through a copy of itself, with a 38-CPU-hour interval-arithmetic check.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "interval arithmetic"
   ],
   "prompt": "Goal: Tackle an open maths problem with an AI collaborator while staying in charge.\nSetup: agents used in source: Claude; tools/MCPs stated: interval arithmetic.\nSteps:\n1. Choose the problem and decide the direction at each step yourself.\n2. Let Claude help with arguments, code and writing the paper.\n3. Use a computer check that rounding can’t fool (here interval arithmetic over ~12.3 million boxes).\n4. Ask it to re-check the whole proof from scratch and fix the real mistakes it finds; check everything yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Gihyo0921 — https://www.reddit.com/r/ClaudeAI/comments/1x2eybb/im_a_9th_grader_and_i_used_claude_to_prove_a/",
   "steps": [
    "Choose the problem and decide the direction at each step yourself.",
    "Let Claude help with arguments, code and writing the paper.",
    "Use a computer check that rounding can’t fool (here interval arithmetic over ~12.3 million boxes).",
    "Ask it to re-check the whole proof from scratch and fix the real mistakes it finds; check everything yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 8.7,
   "sources": [
    {
     "author": "/u/Gihyo0921",
     "handle": "/u/Gihyo0921",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1x2eybb/im_a_9th_grader_and_i_used_claude_to_prove_a/",
     "platform": "reddit",
     "date": "2026-10-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-subagents-video-call",
   "url": "https://agentsetups.dev/use-case/claude-code-subagents-video-call/",
   "title": "See your Claude Code subagents as a live video call",
   "summary": "A VS Code extension reads Claude Code’s session files and shows each subagent as a character in a call, with real commands and diffs.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "VS Code",
    "Node"
   ],
   "prompt": "Goal: Follow what each subagent is doing without reading a wall of logs.\nSetup: agents used in source: Claude; tools/MCPs stated: VS Code, Node.\nSteps:\n1. Read the session files Claude Code already writes in ~/.claude/projects and follow the current session live.\n2. Show each subagent joining when it gets a task and leaving when it reports back.\n3. Show a shared “screen” with the agent’s real commands, output, diffs and files read.\n4. Add a tree of who asked whom, a recap of changed files and replay of past sessions.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/stickygoose — https://www.reddit.com/r/ClaudeAI/comments/1x2f59x/i_made_my_claude_code_subagents_a_video_call/",
   "steps": [
    "Read the session files Claude Code already writes in ~/.claude/projects and follow the current session live.",
    "Show each subagent joining when it gets a task and leaving when it reports back.",
    "Show a shared “screen” with the agent’s real commands, output, diffs and files read.",
    "Add a tree of who asked whom, a recap of changed files and replay of past sessions."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-10",
   "trend_score": 8.5,
   "sources": [
    {
     "author": "/u/stickygoose",
     "handle": "/u/stickygoose",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1x2f59x/i_made_my_claude_code_subagents_a_video_call/",
     "platform": "reddit",
     "date": "2026-10-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-daily-lead-research-pack",
   "url": "https://agentsetups.dev/use-case/grokbot-daily-lead-research-pack/",
   "title": "Get a daily lead research pack with proof links",
   "summary": "Every morning: 5 brands with AI-visibility gaps, 5 mortgage brokers, 5 X threads to reply to — each with a proof link, date and “why now”.",
   "category": "sales-outreach",
   "category_label": "Sales & outreach",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "X"
   ],
   "prompt": "Goal: Get fresh, verified leads every morning.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: X.\nSteps:\n1. Define the lists you want (here 5 US brands with AI-visibility gaps, 5 Canadian mortgage brokers, 5 X threads worth a reply).\n2. Require a proof link, a date and a “why now” for every row.\n3. Have it dedupe against previous days (it caught 5 of 10 leads were repeats).\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Hami Tahm — https://x.com/HamiTahm/status/2108558264158056660",
   "steps": [
    "Define the lists you want (here 5 US brands with AI-visibility gaps, 5 Canadian mortgage brokers, 5 X threads worth a reply).",
    "Require a proof link, a date and a “why now” for every row.",
    "Have it dedupe against previous days (it caught 5 of 10 leads were repeats)."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 6.7,
   "sources": [
    {
     "author": "Hami Tahm",
     "handle": "@HamiTahm",
     "url": "https://x.com/HamiTahm/status/2108558264158056660",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "codex-computer-use-backtest-pine",
   "url": "https://agentsetups.dev/use-case/codex-computer-use-backtest-pine/",
   "title": "Let Codex run hours of strategy backtests on screen",
   "summary": "Codex operated the computer for 12 hours of iterative backtesting of an old Pine Script algo on LuxAlgo.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Codex"
   ],
   "models": [],
   "tools": [
    "Pine Script",
    "LuxAlgo"
   ],
   "prompt": "Goal: Re-test an old trading algorithm without clicking through it myself.\nSetup: agents used in source: Codex; tools/MCPs stated: Pine Script, LuxAlgo.\nSteps:\n1. Open the backtesting tool (here LuxAlgo, free).\n2. Have Codex operate the computer to run iterative backtests on the Pine Script algo.\n3. Let it run for hours and review the results.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: TargetAcquired — https://x.com/BitcoinCyborg/status/2107657695490875406",
   "steps": [
    "Open the backtesting tool (here LuxAlgo, free).",
    "Have Codex operate the computer to run iterative backtests on the Pine Script algo.",
    "Let it run for hours and review the results."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-07",
   "trend_score": 6.5,
   "sources": [
    {
     "author": "TargetAcquired",
     "handle": "@BitcoinCyborg",
     "url": "https://x.com/BitcoinCyborg/status/2107657695490875406",
     "platform": "x",
     "date": "2026-10-07",
     "primary": true
    }
   ]
  },
  {
   "slug": "pplx-computer-email-drafts-not-posting",
   "url": "https://agentsetups.dev/use-case/pplx-computer-email-drafts-not-posting/",
   "title": "Use Perplexity Computer email for drafts, not posting",
   "summary": "Asked to draft and post about an OSS repo, it wrote a clean draft but posted nowhere: HN refused, 5 sites gave 0 accounts.",
   "category": "marketing-growth",
   "category_label": "Marketing & growth",
   "agents": [
    "Perplexity Computer"
   ],
   "models": [],
   "tools": [
    "email"
   ],
   "prompt": "Goal: Test whether Perplexity Computer’s email agent can market a repo for me.\nSetup: agents used in source: Perplexity Computer; tools/MCPs stated: email.\nSteps:\n1. Email Perplexity Computer asking it to draft and post once about the repo (use a throwaway account).\n2. Expect a good draft, then ToS refusals: in this test HN refused and 5 more sites produced 0 accounts and 0 posts.\n3. Post the draft yourself.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Yava — https://x.com/YavaCode/status/2105958358121328890",
   "steps": [
    "Email Perplexity Computer asking it to draft and post once about the repo (use a throwaway account).",
    "Expect a good draft, then ToS refusals: in this test HN refused and 5 more sites produced 0 accounts and 0 posts.",
    "Post the draft yourself."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 6.0,
   "sources": [
    {
     "author": "Yava",
     "handle": "@YavaCode",
     "url": "https://x.com/YavaCode/status/2105958358121328890",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-3d-survivors-game",
   "url": "https://agentsetups.dev/use-case/claude-code-3d-survivors-game/",
   "title": "Direct Claude Code to build a 3D survivors game",
   "summary": "A non-coder had a lead Claude Code session spec, review and deploy while subagents built stages; bots that play the game test balance.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus",
    "Sonnet"
   ],
   "tools": [
    "Three.js",
    "Vite",
    "Vitest",
    "Higgsfield",
    "Meshy",
    "ElevenLabs",
    "Obsidian"
   ],
   "prompt": "Goal: Ship a small, fun browser game without writing the code myself.\nSetup: agents used in source: Claude; tools/MCPs stated: Three.js, Vite, Vitest, Higgsfield, Meshy, ElevenLabs, Obsidian.\nSteps:\n1. Build the feel first with plain shapes (movement, a few spells, a boss) and playtest with blunt notes before any art.\n2. Only then make art: concept images, image-to-3D models, rigging and walk clips.\n3. Dump every idea into a brief; have Claude turn it into a versioned design doc you approve, then build in stages.\n4. Run one main Claude Code session as lead (specs, reviews, tests, deploys) and give each build stage to a subagent working from the spec.\n5. Gate every deploy: type check, all tests, build, then deploy.\n6. Test balance with bots that play the game, e.g. a “stand still” bot that must lose.\n7. Keep design docs, decisions and session logs in an Obsidian vault so the next session picks up where the last stopped.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/Bonelessgummybear — https://www.reddit.com/r/vibecoding/comments/1x55yeh/3d_vampire_survivors_style_arcane_game_with/",
   "steps": [
    "Build the feel first with plain shapes (movement, a few spells, a boss) and playtest with blunt notes before any art.",
    "Only then make art: concept images, image-to-3D models, rigging and walk clips.",
    "Dump every idea into a brief; have Claude turn it into a versioned design doc you approve, then build in stages.",
    "Run one main Claude Code session as lead (specs, reviews, tests, deploys) and give each build stage to a subagent working from the spec.",
    "Gate every deploy: type check, all tests, build, then deploy.",
    "Test balance with bots that play the game, e.g. a “stand still” bot that must lose.",
    "Keep design docs, decisions and session logs in an Obsidian vault so the next session picks up where the last stopped."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 5.9,
   "sources": [
    {
     "author": "/u/Bonelessgummybear",
     "handle": "/u/Bonelessgummybear",
     "url": "https://www.reddit.com/r/vibecoding/comments/1x55yeh/3d_vampire_survivors_style_arcane_game_with/",
     "platform": "reddit",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-pixel-art-aseprite",
   "url": "https://agentsetups.dev/use-case/dots-pixel-art-aseprite/",
   "title": "Make pixel art by installing Aseprite on your Dot",
   "summary": "Install Aseprite on the Dot’s computer instance and let it do the heavy work; results beat image gen for pixel art.",
   "category": "content-video",
   "category_label": "Content & video",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "Aseprite"
   ],
   "prompt": "Goal: Get better pixel art than image generation gives me.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Aseprite.\nSteps:\n1. Install Aseprite on your Dot’s computer instance.\n2. Set up a good workflow and have the Dot do the pixel-art work in Aseprite.\n3. Mind the security implications of installing arbitrary software there.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Michael Gwilt — https://x.com/mgwilt/status/2105745498019901614",
   "steps": [
    "Install Aseprite on your Dot’s computer instance.",
    "Set up a good workflow and have the Dot do the pixel-art work in Aseprite.",
    "Mind the security implications of installing arbitrary software there."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-01",
   "trend_score": 5.9,
   "sources": [
    {
     "author": "Michael Gwilt",
     "handle": "@mgwilt",
     "url": "https://x.com/mgwilt/status/2105745498019901614",
     "platform": "x",
     "date": "2026-10-01",
     "primary": true
    }
   ]
  },
  {
   "slug": "mikeholp-route-claude-codex",
   "url": "https://agentsetups.dev/use-case/mikeholp-route-claude-codex/",
   "title": "Route by task type and make each agent review the other",
   "summary": "Route by task type and make each agent review the other",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Claude",
    "Codex",
    "Cursor"
   ],
   "models": [
    "Claude Opus 5.5 (medium/high effort)",
    "Claude Sonnet 5.5 (English content)",
    "GPT-6.1 Sol (bug fixes, features, scripts)",
    "GPT-6 Luna (small edits, data work)"
   ],
   "tools": [],
   "prompt": "Goal: Use Claude Code and Codex together, routing each task by type\nSetup: agents used in source: Claude, Codex, Cursor.\nBefore you start: A terminal and an account for each tool; Claude Pro plan; ChatGPT login or OpenAI API key for Codex.\nSteps:\n1. Install and sign in to both tools: The author's video covers install and sign-in (01:05–02:27).\n2. Classify each task by type, first match wins: Review, locale text, audits, research, English prose, broken, mechanical edit, feature, script, data.\n3. Map types to tool and model: Audits/research/content → Claude Code; bugs/features/scripts/data → Codex; lighter models for lighter jobs.\n4. Work in a separate project folder: Away from any script that sends email or writes to an outside service.\n5. Lock down permissions: Claude Code in manual mode with an allowlist, push/commit/merge/deploy/delete disallowed; Codex workspace-write or read-only.\n6. Fall back to the other tool on usage limits: At most four attempts; never moves to paid credits without approval.\n7. Have the other tool review substantial work: The reviewer reports findings and does not edit.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Mike Holp — https://www.ai-automation-station.com/guides/claude-code-vs-codex.html (summarised from source; the source has no explicit step list)",
   "steps": [
    "Install and sign in to both tools: The author's video covers install and sign-in (01:05–02:27).",
    "Classify each task by type, first match wins: Review, locale text, audits, research, English prose, broken, mechanical edit, feature, script, data.",
    "Map types to tool and model: Audits/research/content → Claude Code; bugs/features/scripts/data → Codex; lighter models for lighter jobs.",
    "Work in a separate project folder: Away from any script that sends email or writes to an outside service.",
    "Lock down permissions: Claude Code in manual mode with an allowlist, push/commit/merge/deploy/delete disallowed; Codex workspace-write or read-only.",
    "Fall back to the other tool on usage limits: At most four attempts; never moves to paid credits without approval.",
    "Have the other tool review substantial work: The reviewer reports findings and does not edit."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-11",
   "trend_score": 4.9,
   "sources": [
    {
     "author": "Mike Holp",
     "handle": "Mike Holp",
     "url": "https://www.ai-automation-station.com/guides/claude-code-vs-codex.html",
     "platform": "blog",
     "date": "2026-10-11",
     "primary": true
    }
   ]
  },
  {
   "slug": "joekarlsson-opencode-litellm",
   "url": "https://agentsetups.dev/use-case/joekarlsson-opencode-litellm/",
   "title": "Move your default coding agent to OpenCode via OpenRouter",
   "summary": "DeepSeek V4.1 Flash passed every run of his two-task test at about two cents a task (self-reported, \"a field report and not a ranking\").",
   "category": "agent-setup",
   "category_label": "Agent setup & config",
   "agents": [
    "OpenCode",
    "Claude"
   ],
   "models": [
    "DeepSeek V4.1 Flash",
    "Claude (escalation for the hardest problems)"
   ],
   "tools": [],
   "prompt": "Goal: Move your default coding agent to OpenCode with open-weight models\nSetup: agents used in source: OpenCode, Claude.\nBefore you start: An OpenRouter account (a LiteLLM gateway is optional).\nSteps:\n1. Point OpenCode at OpenRouter (gateway optional): The author routes everything through LiteLLM with names like cloud-coder, fallbacks and per-app budgets.\n2. Run your own two-task bake-off: One easy and one hard task with hidden tests; two runs per model; grade pass/fail, time and cost.\n3. Pick the cheapest model that passes: For him: DeepSeek V4.1 Flash as default.\n4. Make OpenCode send reasoning back: Set `interleaved: {field: \"reasoning_content\"}` and a reasoningEffort per model in opencode.json.\n5. Add a \"Done means verified\" rule to global AGENTS.md: Run the change, paste 1–5 proof lines, end PASS or FAIL.\n6. Add a verify gate if the model still skips it: A ~100-line OpenCode plugin sends the agent back once if it edited code and ran nothing.\n7. Keep Claude as the escalation path: Harder coding to DeepSeek V4 Pro; the hardest problems to Claude.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Joe Karlsson — https://www.joekarlsson.com/blog/breaking-up-with-claude-code/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Point OpenCode at OpenRouter (gateway optional): The author routes everything through LiteLLM with names like cloud-coder, fallbacks and per-app budgets.",
    "Run your own two-task bake-off: One easy and one hard task with hidden tests; two runs per model; grade pass/fail, time and cost.",
    "Pick the cheapest model that passes: For him: DeepSeek V4.1 Flash as default.",
    "Make OpenCode send reasoning back: Set `interleaved: {field: \"reasoning_content\"}` and a reasoningEffort per model in opencode.json.",
    "Add a \"Done means verified\" rule to global AGENTS.md: Run the change, paste 1–5 proof lines, end PASS or FAIL.",
    "Add a verify gate if the model still skips it: A ~100-line OpenCode plugin sends the agent back once if it edited code and ran nothing.",
    "Keep Claude as the escalation path: Harder coding to DeepSeek V4 Pro; the hardest problems to Claude."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": "About two cents a task on DeepSeek V4.1 Flash; OpenCode capped at $20 a month at his gateway",
   "date": "2026-10",
   "trend_score": 3.9,
   "sources": [
    {
     "author": "Joe Karlsson",
     "handle": "Joe Karlsson",
     "url": "https://www.joekarlsson.com/blog/breaking-up-with-claude-code/",
     "platform": "blog",
     "date": "2026-10",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-desk-usage-display",
   "url": "https://agentsetups.dev/use-case/claude-code-desk-usage-display/",
   "title": "Put your Claude Code usage on a desk display",
   "summary": "Claude wrote a Claude Code mod, ESP32 firmware and UI, then drove FreeCAD from the display’s drawing to make a printable enclosure.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "ESP32",
    "FreeCAD"
   ],
   "prompt": "Goal: See subscription usage and context window at a glance on a small screen.\nSetup: agents used in source: Claude; tools/MCPs stated: ESP32, FreeCAD.\nSteps:\n1. Use a Claude Code mod to pull subscription usage and context-window data out to a display over USB.\n2. Have Claude write the mod, the ESP32 firmware and the UI.\n3. Give Claude the manufacturer’s dimensioned drawing and have it drive FreeCAD to design the enclosure and stand.\n4. 3D print and assemble.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/fcampanini74 — https://www.reddit.com/r/ClaudeCode/comments/1wye4ix/i_just_wanted_to_try_the_new_claude_code_mods_i/ (summarised from source; the source has no explicit step list)",
   "steps": [
    "Use a Claude Code mod to pull subscription usage and context-window data out to a display over USB.",
    "Have Claude write the mod, the ESP32 firmware and the UI.",
    "Give Claude the manufacturer’s dimensioned drawing and have it drive FreeCAD to design the enclosure and stand.",
    "3D print and assemble."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-05",
   "trend_score": 3.7,
   "sources": [
    {
     "author": "/u/fcampanini74",
     "handle": "/u/fcampanini74",
     "url": "https://www.reddit.com/r/ClaudeCode/comments/1wye4ix/i_just_wanted_to_try_the_new_claude_code_mods_i/",
     "platform": "reddit",
     "date": "2026-10-05",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-muse-meal-plan-grocery-order",
   "url": "https://agentsetups.dev/use-case/claude-muse-meal-plan-grocery-order/",
   "title": "Plan meals with Claude, let Muse order the groceries",
   "summary": "Claude writes a two-week meal plan for approval and the shopping list; Muse places the order in its browser while he confirms payment.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Claude",
    "Meta Muse"
   ],
   "models": [],
   "tools": [
    "Google Docs",
    "Walmart",
    "tablet kiosk"
   ],
   "prompt": "Goal: Hand off meal planning and grocery ordering but keep the final say.\nSetup: agents used in source: Claude, Meta Muse; tools/MCPs stated: Google Docs, Walmart, tablet kiosk.\nSteps:\n1. Have Claude draft a two-week meal plan from household preferences and last cycle’s feedback, and submit it for review.\n2. After approval, have it build the grocery list, add low pantry staples, and save it as a Google Doc in a dedicated folder.\n3. Have Muse read the doc and place the order in its own browser; confirm the final payment yourself from your phone.\n4. Show the plan, tonight’s recipe, thaw reminders and the list on a kitchen tablet in kiosk mode.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/WeezerHunter — https://www.reddit.com/r/ClaudeAI/comments/1wxlm01/ai_is_a_hellofresh_killer_automated_meal_prep_and/",
   "steps": [
    "Have Claude draft a two-week meal plan from household preferences and last cycle’s feedback, and submit it for review.",
    "After approval, have it build the grocery list, add low pantry staples, and save it as a Google Doc in a dedicated folder.",
    "Have Muse read the doc and place the order in its own browser; confirm the final payment yourself from your phone.",
    "Show the plan, tonight’s recipe, thaw reminders and the list on a kitchen tablet in kiosk mode."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-04",
   "trend_score": 1.3,
   "sources": [
    {
     "author": "/u/WeezerHunter",
     "handle": "/u/WeezerHunter",
     "url": "https://www.reddit.com/r/ClaudeAI/comments/1wxlm01/ai_is_a_hellofresh_killer_automated_meal_prep_and/",
     "platform": "reddit",
     "date": "2026-10-04",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-splat-engine-then-game",
   "url": "https://agentsetups.dev/use-case/claude-splat-engine-then-game/",
   "title": "Build a splat engine, then let Claude design the game",
   "summary": "Opus built a Gaussian-splat 3D engine in ~5 hours; told only the genre, it then made every design decision for a survivors game.",
   "category": "games",
   "category_label": "Games",
   "agents": [
    "Claude"
   ],
   "models": [
    "Opus 5.5"
   ],
   "tools": [
    "Gaussian splats"
   ],
   "prompt": "Goal: See what the model designs when I hand it every decision.\nSetup: agents used in source: Claude; tools/MCPs stated: Gaussian splats.\nSteps:\n1. Build the engine first (here about 5 hours and ~20 prompts to tune it).\n2. Tell Claude only the genre and to use the engine you just made.\n3. Tell it to make all the design decisions and only come back when the whole game is finished.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: /u/buak — https://www.reddit.com/r/vibecoding/comments/1wvu4u0/made_a_3dengine_that_uses_gaussian_splats_instead/",
   "steps": [
    "Build the engine first (here about 5 hours and ~20 prompts to tune it).",
    "Tell Claude only the genre and to use the engine you just made.",
    "Tell it to make all the design decisions and only come back when the whole game is finished."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 0.9,
   "sources": [
    {
     "author": "/u/buak",
     "handle": "/u/buak",
     "url": "https://www.reddit.com/r/vibecoding/comments/1wvu4u0/made_a_3dengine_that_uses_gaussian_splats_instead/",
     "platform": "reddit",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "amp-orb-garmin-watch-face",
   "url": "https://agentsetups.dev/use-case/amp-orb-garmin-watch-face/",
   "title": "Build a Garmin watch face in a cloud Amp Orb",
   "summary": "An Amp Orb set up with the Garmin Connect IQ SDK and simulator built a recreation of a favourite old Garmin watch face.",
   "category": "hardware-iot",
   "category_label": "Hardware & IoT",
   "agents": [
    "Amp"
   ],
   "models": [],
   "tools": [
    "Garmin Connect IQ SDK",
    "Garmin simulator"
   ],
   "prompt": "Goal: Recreate a watch face I loved from older Garmin models.\nSetup: agents used in source: Amp; tools/MCPs stated: Garmin Connect IQ SDK, Garmin simulator.\nSteps:\n1. Set up an Amp Orb with the Garmin CIQ SDK and Simulator.\n2. Have it build the watch face in the cloud and test it in the simulator.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Robert — https://x.com/robertholak/status/2109734909270958171",
   "steps": [
    "Set up an Amp Orb with the Garmin CIQ SDK and Simulator.",
    "Have it build the watch face in the cloud and test it in the simulator."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Robert",
     "handle": "@robertholak",
     "url": "https://x.com/robertholak/status/2109734909270958171",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  },
  {
   "slug": "claude-code-power-bi-dashboard",
   "url": "https://agentsetups.dev/use-case/claude-code-power-bi-dashboard/",
   "title": "Build a Power BI dashboard by describing it",
   "summary": "With Claude Code connected to a Power BI project, a dashboard took 20 minutes instead of ~2 days.",
   "category": "data-analysis",
   "category_label": "Data analysis",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Power BI"
   ],
   "prompt": "Goal: Speed up building Power BI reports.\nSetup: agents used in source: Claude; tools/MCPs stated: Power BI.\nSteps:\n1. Connect Claude Code to your Power BI project.\n2. Describe the dashboard you want in plain English.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: CalibreAI — https://x.com/Calibre_AI/status/2108533676493672945 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Connect Claude Code to your Power BI project.",
    "Describe the dashboard you want in plain English."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-09",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "CalibreAI",
     "handle": "@Calibre_AI",
     "url": "https://x.com/Calibre_AI/status/2108533676493672945",
     "platform": "x",
     "date": "2026-10-09",
     "primary": true
    }
   ]
  },
  {
   "slug": "cowork-replace-portfolio-tool",
   "url": "https://agentsetups.dev/use-case/cowork-replace-portfolio-tool/",
   "title": "Automate portfolio workflows in Cowork instead of buying",
   "summary": "Vendor portfolio tools cost a lot for features they didn’t need; Cowork + MS365 + add-ins + skills automated the workflows.",
   "category": "productivity-ops",
   "category_label": "Productivity & ops",
   "agents": [
    "Claude"
   ],
   "models": [],
   "tools": [
    "Microsoft 365"
   ],
   "prompt": "Goal: Avoid an expensive portfolio management tool.\nSetup: agents used in source: Claude; tools/MCPs stated: Microsoft 365.\nSteps:\n1. List the workflows you actually need from the vendor tool.\n2. Connect Claude Cowork to Microsoft 365 and its add-ins.\n3. Write skills for each workflow and automate them.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Purnendu Shekhar — https://x.com/shekhar311224/status/2108214631986868410 (summarised from source; the source has no explicit step list)",
   "steps": [
    "List the workflows you actually need from the vendor tool.",
    "Connect Claude Cowork to Microsoft 365 and its add-ins.",
    "Write skills for each workflow and automate them."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Purnendu Shekhar",
     "handle": "@shekhar311224",
     "url": "https://x.com/shekhar311224/status/2108214631986868410",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-household-admin-week",
   "url": "https://agentsetups.dev/use-case/dots-household-admin-week/",
   "title": "What a Dot did in a week of household admin",
   "summary": "Zapier’s Harry Guinness: bounced card payments, a scam check, grant paperwork, delivery clashes, new restaurant tables.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "Google account"
   ],
   "prompt": "Goal: Let a Dot connected to my real Google account handle household admin.\nSetup: agents used in source: ChatGPT Dots; tools/MCPs stated: Google account.\nSteps:\n1. Connect your Dot to your actual Google account (the author notes the privacy trade-off).\n2. Let it flag issues proactively: bounced card payments, clashing deliveries, documents that miss requirements (a lead-pipe grant).\n3. Ask it to check suspicious emails (it correctly said a forwarded email was legitimate).\n4. Give it errands: find alternative tables when a booking is cancelled, troubleshoot a broadband login with support.\n5. Don’t let it run your inbox unsupervised: it can miss urgent, high-judgment items.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Harry Guinness — https://zapier.com/blog/chatgpt-dots/",
   "steps": [
    "Connect your Dot to your actual Google account (the author notes the privacy trade-off).",
    "Let it flag issues proactively: bounced card payments, clashing deliveries, documents that miss requirements (a lead-pipe grant).",
    "Ask it to check suspicious emails (it correctly said a forwarded email was legitimate).",
    "Give it errands: find alternative tables when a booking is cancelled, troubleshoot a broadband login with support.",
    "Don’t let it run your inbox unsupervised: it can miss urgent, high-judgment items."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-13",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Harry Guinness",
     "handle": "Zapier blog",
     "url": "https://zapier.com/blog/chatgpt-dots/",
     "platform": "blog",
     "date": "2026-10-13",
     "primary": true
    }
   ]
  },
  {
   "slug": "dots-resume-crashed-codex-threads",
   "url": "https://agentsetups.dev/use-case/dots-resume-crashed-codex-threads/",
   "title": "Have your Dot resume crashed Codex threads",
   "summary": "Ubuntu killed the Codex app mid-run; after a restart, his Dot found and resumed every interrupted parallel thread.",
   "category": "personal-assistant",
   "category_label": "Personal assistants",
   "agents": [
    "Codex",
    "ChatGPT Dots"
   ],
   "models": [],
   "tools": [
    "Ubuntu"
   ],
   "prompt": "Goal: Recover several parallel Codex threads after a crash.\nSetup: agents used in source: Codex, ChatGPT Dots; tools/MCPs stated: Ubuntu.\nSteps:\n1. After restarting, ask your Dot to find all interrupted Codex threads.\n2. Have it resume each one; expect it to take a while.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Deependra Solanky — https://x.com/solanky/status/2105871916800389433",
   "steps": [
    "After restarting, ask your Dot to find all interrupted Codex threads.",
    "Have it resume each one; expect it to take a while."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-02",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Deependra Solanky",
     "handle": "@solanky",
     "url": "https://x.com/solanky/status/2105871916800389433",
     "platform": "x",
     "date": "2026-10-02",
     "primary": true
    }
   ]
  },
  {
   "slug": "goose-web-ui-sandboxed-microvm",
   "url": "https://agentsetups.dev/use-case/goose-web-ui-sandboxed-microvm/",
   "title": "Put a web UI on a Goose agent in a microVM",
   "summary": "React SSR + Express + SSE front end talking ACP over WebSockets to a sandboxed Goose agent, with SQLite and WhatsApp.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Goose"
   ],
   "models": [],
   "tools": [
    "React",
    "Express",
    "SSE",
    "ACP",
    "WebSockets",
    "SQLite",
    "WhatsApp"
   ],
   "prompt": "Goal: Use a Goose agent safely from a browser and WhatsApp.\nSetup: agents used in source: Goose; tools/MCPs stated: React, Express, SSE, ACP, WebSockets, SQLite, WhatsApp.\nSteps:\n1. Run Goose inside a sandboxed microVM.\n2. Connect to it with ACP over WebSockets from an Express server.\n3. Stream responses to a React (SSR) UI via SSE.\n4. Persist sessions in SQLite and add a WhatsApp integration.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Ismael — https://x.com/IsmaelFcoM/status/2107984515465675147",
   "steps": [
    "Run Goose inside a sandboxed microVM.",
    "Connect to it with ACP over WebSockets from an Express server.",
    "Stream responses to a React (SSR) UI via SSE.",
    "Persist sessions in SQLite and add a WhatsApp integration."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-08",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Ismael",
     "handle": "@IsmaelFcoM",
     "url": "https://x.com/IsmaelFcoM/status/2107984515465675147",
     "platform": "x",
     "date": "2026-10-08",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-builds-updates-website",
   "url": "https://agentsetups.dev/use-case/grokbot-builds-updates-website/",
   "title": "Have Grok Bot build and update a website daily",
   "summary": "Without writing code, a user talked Grok Bot into building a site (Bot Lodge), and it keeps it updated every day.",
   "category": "design-frontend",
   "category_label": "Design & frontend",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [],
   "prompt": "Goal: Run a website without coding.\nSetup: agents used in source: Grok Bot.\nSteps:\n1. Describe the site to Grok Bot in conversation.\n2. Have it build the site.\n3. Schedule it to update the site every day.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Nathan Petty — https://x.com/nathanpetty/status/2110574324394656008 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Describe the site to Grok Bot in conversation.",
    "Have it build the site.",
    "Schedule it to update the site every day."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Nathan Petty",
     "handle": "@nathanpetty",
     "url": "https://x.com/nathanpetty/status/2110574324394656008",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-onchain-wallet-tracker",
   "url": "https://agentsetups.dev/use-case/grokbot-onchain-wallet-tracker/",
   "title": "Track your crypto wallet activity with Grok Bot",
   "summary": "A daily Sui user turned Grok Bot into a personal assistant that tracks his wallet and monitors onchain activity.",
   "category": "finance-trading",
   "category_label": "Finance & trading",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "Sui"
   ],
   "prompt": "Goal: Keep an eye on my onchain activity without checking manually.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: Sui.\nSteps:\n1. Give Grok Bot your wallet address.\n2. Have it track wallet activity and collect the data for you.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Palaki — https://x.com/iampalaki/status/2110584074339598609 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Give Grok Bot your wallet address.",
    "Have it track wallet activity and collect the data for you."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Palaki",
     "handle": "@iampalaki",
     "url": "https://x.com/iampalaki/status/2110584074339598609",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "grokbot-papers-to-prototype",
   "url": "https://agentsetups.dev/use-case/grokbot-papers-to-prototype/",
   "title": "Turn a gym idea into papers and a prototype",
   "summary": "Mid-workout he told Grok Bot an idea; it found research papers, summarised them and built a prototype on GitHub by the time he got home.",
   "category": "research-science",
   "category_label": "Research & science",
   "agents": [
    "Grok Bot"
   ],
   "models": [],
   "tools": [
    "GitHub"
   ],
   "prompt": "Goal: Explore an idea while I’m away from my desk.\nSetup: agents used in source: Grok Bot; tools/MCPs stated: GitHub.\nSteps:\n1. Tell Grok Bot the idea by voice.\n2. Have it find relevant research papers with summaries.\n3. Ask it to build a working prototype taking the best of each paper and push it to GitHub.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Glauber — https://x.com/glauberxyz/status/2110573717499891753 (summarised from source; the source has no explicit step list)",
   "steps": [
    "Tell Grok Bot the idea by voice.",
    "Have it find relevant research papers with summaries.",
    "Ask it to build a working prototype taking the best of each paper and push it to GitHub."
   ],
   "steps_basis": "summarised",
   "time": null,
   "cost": null,
   "date": "2026-10-15",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Glauber",
     "handle": "@glauberxyz",
     "url": "https://x.com/glauberxyz/status/2110573717499891753",
     "platform": "x",
     "date": "2026-10-15",
     "primary": true
    }
   ]
  },
  {
   "slug": "hermes-as-coding-agent-tips",
   "url": "https://agentsetups.dev/use-case/hermes-as-coding-agent-tips/",
   "title": "Turn Hermes Agent into a coding machine",
   "summary": "After 2 months, Hermes builds his apps (14k and 25k lines): ast-grep skill, coding model, no approvals, Superpowers, a vision model.",
   "category": "coding",
   "category_label": "Coding",
   "agents": [
    "Hermes Agent"
   ],
   "models": [],
   "tools": [
    "Understand-Anything",
    "ast-grep",
    "Superpowers"
   ],
   "prompt": "Goal: Make a general-purpose agent reliable at real software work.\nSetup: agents used in source: Hermes Agent; tools/MCPs stated: Understand-Anything, ast-grep, Superpowers.\nSteps:\n1. Use Understand-Anything so you and the agent share the codebase context.\n2. Enable the optional ast-grep skill for smarter code search.\n3. Pick a model that’s strong at coding — the deciding factor.\n4. Configure the env so the agent runs uninterrupted (skip approvals).\n5. Use Superpowers for a proper development workflow.\n6. Add a vision model so it can see and verify the UI.\nRules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify.\nBased on: Kyz — https://x.com/minhng92/status/2109490581747708346",
   "steps": [
    "Use Understand-Anything so you and the agent share the codebase context.",
    "Enable the optional ast-grep skill for smarter code search.",
    "Pick a model that’s strong at coding — the deciding factor.",
    "Configure the env so the agent runs uninterrupted (skip approvals).",
    "Use Superpowers for a proper development workflow.",
    "Add a vision model so it can see and verify the UI."
   ],
   "steps_basis": "source",
   "time": null,
   "cost": null,
   "date": "2026-10-12",
   "trend_score": 0.0,
   "sources": [
    {
     "author": "Kyz",
     "handle": "@minhng92",
     "url": "https://x.com/minhng92/status/2109490581747708346",
     "platform": "x",
     "date": "2026-10-12",
     "primary": true
    }
   ]
  }
 ]
}