CLAUDE DUET IS A RESEARCH PREVIEW. THESE 10 REPOS WORK TONIGHT
everyone is refreshing for Duet access while the pieces to build your own sit on GitHub with over 600,000 stars between them
10 GitHub repositories to build the same thing on Claude Code:
01 MCP Servers → give Claude Code hands through official connectors for files, git and the web, so your agent can read the places your work actually lives
https://t.co/ZYi8LkaDUL
02 Basic Memory → keep everything Claude learns in plain Markdown files it can search and update, so you never re-explain a project again
https://t.co/mg1KCDv5K1
03 Mem0 → add a memory layer that keeps your preferences, people and past decisions across sessions, so every brief starts from what it already knows
https://t.co/6H27cKEVnP
04 Graphiti → track how facts change over time, so your agent knows the deadline moved instead of quoting the old one
https://t.co/hu1Bz0YV6m
05 n8n → schedule the morning brief, trigger your agent when an email lands and route its drafts back to you for approval
https://t.co/GZId50CAXh
06 Huginn → run agents that watch sites, feeds and inboxes on your behalf and only ping you when something actually changed
https://t.co/8ZvTOQyWLX
07 whisper.cpp → turn voice notes into text locally, so "remind me to call the bank" from your walk ends up in tomorrow's brief
https://t.co/TyvQzRHPev
08 Paperless-ngx → scan bills, contracts and letters into a searchable archive your agent checks before it reminds you of a deadline
https://t.co/C9nstF5zpB
09 Karakeep → drop links, notes and screenshots into one inbox with auto-tagging, so your agent sorts what you saved instead of you
https://t.co/eH7UUUAX3c
10 Langfuse → trace every run your agent makes while you're away, so you can see exactly what it read, what it drafted and why
https://t.co/A2X5MmtNWl
start with memory and one connector. a morning brief that knows your people beats ten automations that don't
then add the schedule. once it runs at 7am without you, put "ask before acting" in place before you connect anything that can send
memory → connectors → schedule → approvals. that's the whole Duet idea, built from parts you can inspect
how to wire all 10 together ↓
my safety rule let 10 dangerous commands through. 6 more lines and it lets through 0
i gave my agent team one rule: nothing dangerous runs until i say yes. 21 lines of python. it blocked git push and deploys, and i thought i was done
then i fed it 591 commands an agent team would actually run, and 10 dangerous ones went straight through without a warning. terraform apply, kubectl apply, docker push, aws s3 rm. rm -fr got in because i had only written rm -rf
i added 6 lines and ran the same 591 again. 31 out of 31 blocked, nothing slipped, and it didn't block a single normal command by mistake
the rule is in the article, with all 4 agent files
YOUR CONTENT TEAM IS NOW ONE XML FILE. GROK + 3 CLAUDE AGENTS DO 48 JOBS FOR $1.30 AND THE 49TH JOB IS STOPPING THEM FROM NUKING YOUR PROJECT
screenshot the prompt. that's the whole team.
grok scouts. haiku digs. sonnet writes. opus kills anything without a source
the jobs it does every morning:
→ morning scout: 50 posts from 20 accounts you picked, one API call
→ engagement ranker: keeps the 10 people actually reacted to
→ evidence collector: every claim gets a link
→ draft writer: touches nothing outside output/
→ claim checker: no [S#], no sentence
→ verdict writer: PASS or NOT READY, nothing in between
and the jobs nobody talks about:
→ git push stopper
→ rm -rf stopper (and rm -fr, the one i missed)
→ terraform, kubectl, docker push, aws s3 rm blockers
my first gate was 21 lines. it let 10 dangerous commands through
6 more lines → 31 of 31 blocked, 0 false alarms on 560 normal ones
$0.25 grok + $0.08 haiku + $0.32 sonnet + $0.63 opus = $1.30
every agent file, every prompt and the 27-line gate below ↓
F*ck YES... I made a prompt that stops Claude from making things up while it reverse-engineers a binary
the shift: Sonnet 5.5 maps the binary for cents → Opus 5.5 rebuilds the hard logic → Fable 5.1 only reviews what already passed tests
here’s 3 step guide:
step 1 → drop the CLAUDE.md from the image into your project root (every claim now needs an address or a test behind it)
step 2 → run Sonnet 5.5 and ask for a function map: ADDRESS | NAME | ROLE | EVIDENCE | CONFIDENCE
step 3 → switch to Opus 5.5 with that map and say something like:
“Reconstruct the behavior of [FUNCTION]. Write a spec plus two alternative interpretations and the minimum tests that tell them apart”
the result: you pay ~$0.30 per pass instead of $1.50 on Fable, and you catch the “this loop is CRC32” mistake before it lands in your code
Paste it now. Then read article below to master Claude reverse engineering: