Juan van der Hamen y León, Still Life with Sweets and Pottery, 1627. National Gallery of Art, CC0.
You don't need nine chats. You need one door, plus memory.
Good morning.
The week argued one thing, over and over: a personal agent stack is now a product, not a hobby prompt. People are shipping org charts. Chief of Staff on the door, specialists behind it, memory that survives a new tab. That is the category forming under Grok Bot, Hermes, SuperMemory, and Chroma Foundation. If you keep chatting every bot yourself, you are buying the old company, not the new one.
The public just packaged what a few people were already running. One door. A night shift. A shared brain.
Three Grok Bot posts said the same thing with different costumes.
Treat one bot as the only human door. Put the whole config in the description field. No files. Connect inbox, calendar, news, plus one publishing channel. Then add the other bots over two weeks, three at a time. You only ever talk to the top one. Pasting an article is how work gets distributed. Closest thing to running a company with no employees, if you believe the hype. Believe the org chart instead.
The 24/7 wrapper sold a team that never quits and never asks for a salary. A recap of someone else's six-bot research desk claimed to replace a large vendor stack and a full research week. Bookmark-bait tone. No disclosed strategy. Steal the desk metaphor. Do not steal implied alpha. Night shift is a packaging lesson, not a trading system.
Same pattern off-platform. Split the stack: a VPS bot stays always-on (Telegram, sandboxes); the laptop talks to it over a custom skill. Assistant in the room. Remote Chief of Staff on the box. Heavy jobs off the laptop. One surface for both.
At Sentry Hackweek, a recorder transcribes and a router decides todo versus "this is work," then kicks agents for code or research. Hardware is optional. The router is the product. Talk once. Let the top bot classify.
One-input starts keep showing up: drop a website, agents go. Steal the paste-URL desk, not the marketing vertical. The same idea appears for mockups you describe instead of code, for a story engine that is more play than ops, and for Codex cutting a recap of its own editing job. One bot, one cut. Instinct remains a watchlist. No demo in the text.
Okara · Describe-it · Tommy Geoco / Nora · Brent Schooley · Jason Shuman
Keep a single entry point. Do not chat nine bots.
Chroma Foundation, a research preview, learns from agent sessions and keeps a self-improving wiki of what a person or team knows. It plugs into Codex, Claude Code, Cursor, Slack, or any agent over MCP. Versioning, citations, access control, SOC 2. Coding sessions stay private to the author. Priced like infra, roughly $30/user/month plus usage. Family and civic data can wait until that privacy story is boring.
SuperMemory plugins are free, with one shared memory across Claude, Codex, OpenCode, and similar tools. The demo: plan a site in Claude Code, open Codex, say "retrieve the plan," and it is already there. Same job as Foundation. Cheaper. More tactical. Skip it if the privacy model is fuzzier than Chroma's.
Re-explaining the same project to every new bot is the bug. Pick one memory. Do not run both and hope they merge in your head.
Once memory exists, the useful job is luck. Point a model at a personal corpus — meetings, email, Slack, LinkedIn, notes — and look for unreciprocated favors, mentor matches, and intros both sides would value. Overnight desk research the model started without being asked. That is a Chief of Staff that increases luck, not CRM spam.
/design in Claude Code generates a few artboards for a feature. You pick one, edit, implement. The canvas lives in the coding session. Token-hungry research preview. Decide the one-tap interaction on a board before anyone writes UI code.
Sundrop already filters a camera roll down to the photos people actually want. Beta users still missed the value. They rebuilt onboarding as a show-not-tell sequence and sent another TestFlight. The tech was fine. The first-run story was not. Products die when the magic is invisible.
The week's design votes all point the same way: fewer controls, a 24-hour design pass, one switch and rice happens, a turntable with mechanical knobs and no app. Copy the interaction, not the kitchen or the vinyl. Fancy landing motion is for marketing. Keep the working screen quiet. Claude Tag in Slack is a coworker surface, not a new religion.
Jake Castillo · Adam Kasprzak · Ritwik Pavan · Meng To · Donn Felker
Christensen's last class, resurfaced: apply disruption theory to your life. Wrong metric kills companies. Seasons beat a daily scoreboard. The same trap shows up when a dashboard becomes the product.
Two health notes, neither is an app score. Dumping a raw 23andMe file into Claude surfaced APOE4 — roughly 3x late-onset Alzheimer risk, worse lipids. Genome plus LLM is a watch list. Confirm with a physician. Elsewhere, 3-mode circadian bulbs: light as personal OS, not a feature ticket.
Always-on research desks are a labor story. They are not a position.
Stand up one door and one memory, then force the core tap through /design before code.
- Name the only bot you will talk to this week. Everything else is staff.
- Pick Chroma Foundation or SuperMemory. Not both. Feed it the project constraints you already repeat.
- In Claude Code: /design a few options for the one-tap action. Pick the artboard a tired human can finish in three seconds. Implement that one. Quiet screen. Show the magic on first run.
If you still have energy, add a voice router: talk once, the top bot classifies "log it" versus "this is work." Hardware later.
Until next Friday.