Christopher 🇺🇸

A modern adaptation of "The Myth of Sisyphus" by Albert Camus. I leave Prometheus on the edge of his keyboard, ready to post. One always encounters the mob's rage again. But Prometheus teaches a higher fidelity that negates the echo chambers and raises truths. He too concludes that all is well. This digital landscape, henceforth without echo, seems to him neither barren nor pointless. Each pixel of that screen, each byte of that data stream, in itself forms a universe. The struggle itself toward clarity is enough to fill one's heart. One must imagine Prometheus smiling.

The agent decided the bar for done is not simply a number.

flavor of the week ~ “This is a goldmine."

@rvcas cmux has some kinks to work out but most satisfying experience I’ve seen.

The Claude desktop app is a steaming pile of crap tbh, buggy as hell

@dani_avila7 This is very nice

Semantic analysis dashboard for Claude Code Templates... built with Perplexity Computer aimtpl.com has 1,500+ components: SKILLs, Subagents, Commands, MCPs, Hooks, and more. I’d been meaning to run a semantic analysis to extract distribution KPIs and classify everything properly. Had a prototype… but it kept going nowhere. Until Computer + two shots did it for me in 26 min 1 sec. I gave it the GitHub link and the task, let it run… and forgot about it. Then the Computer notification popped up: done ✅ That’s the magic of Computer: highly effective results with almost no context, 100% autonomous

@bekacru why not GitBetter?

Introducing Better Hub We tried to improve GitHub. It’s ambitious project and super early, but our team already uses it by default. Give it a try (and its open-source)

@BChris91 github.com/manaflow-ai/cm… mapped to cmd+control+f in nightly! will release after some dogfooding. lmk if you had something else in mind

Introducing cmux: the open-source terminal built for coding agents. - Vertical tabs - Blue rings around panes that need attention - Built-in browser - Based on Ghostty When Claude Code needs you, the pane glows blue and the sidebar tells you why. No Electron/Tauri. Just Swift/Appkit.

@lawrencecchen I use hotkey all the time in ghostty to fullscreen. For cmux, it’s built in a way that I already want to keep the app in full screen. The ability to full screen the active pane in a workspace but leave the vertical workspaces sidebar showing would be really cool.

@BChris91 not today, how would you like this behavior to work?

@lawrencecchen I’d love to have hotkey to full sceen my active pane. Is that possible?

@BChris91 lmk if you run to any issues!

@Amank1412 Not DRY about DRY.

CEO of Y Combinator shared his CLAUDE.md prompt for Claude Code It helps him ship 4,000+ line features with full tests in about an hour: This prompt pushes Claude to: Decide if the plan is overbuilt, underbuilt, or "engineered enough" before writing any code Aggressively review test coverage, edge cases, and failure modes Look for performance risks, scaling issues, and refactoring opportunities But the real difference is the workflow. Instead of jumping into implementation, he makes Claude: Do a structured review (architecture → code quality → tests → performance) Present tradeoffs with opinionated recommendations Pause for feedback before proceeding In other words, Garry is using it as a senior engineer reviewing the system before changes are made. For small teams, this is a game changer. When you don't have a staff engineer reviewing every PR, you design the review process into your Al.

@melvynx x.com/bchris91/statu…

don't use it ☠️

"Cons: Requires me to be a good listener to the team." Is this supervisor cooked?

@nityeshaga Had the team research and compare two posts I saw today against the company's current practices. Great post and the team agrees! Was also just thinking about time-stamping session workflows. Glad to hear you validate that pattern.

How We Built an AI Project Manager Using Claude Code Claude Code for non-technical work is going to sweep the world by storm in 2026. This is how we built Claudie, our internal project manager for the consulting business. This process provides a great peek into my role as an applied AI engineer. My Role I'm an applied AI engineer at @every. My job is to take everything we learn about AI — from client work, from the industry, from internal experiments — and turn it into systems that scale. Curriculum, automations, frameworks. I turn the insights clients give us on discovery calls to curriculum that designers can polish into final client-ready materials. When there's a repetitive task across sales, planning, or delivery, I build the automation, document it, and train the internal team to use. The highest-value internal automation I've built so far is the one I'm about to tell you about. What We Needed to Automate Every Consulting runs on Google Sheets. Every client gets a detailed dashboard — up to 12 tables per sheet — tracking people, teams, sessions, deliverables, feedback, and open items. Keeping these sheets accurate and up-to-date is genuinely a full person's job. @NataliaZarina, our consulting lead, was doing that job on top of 20 other things. She's managing client relationships, running sales, making final decisions on scope and delivery — and also manually updating dashboards, cross-referencing emails and calendar events, and keeping everything current. It was the work of two people, and she was doing both. So I automated the second person. Step 1: Write a Job Description The first thing I did was ask Natalia to write a job description. Not for an AI agent — for a human. I asked her to imagine she's hiring a project manager: what would she want this person to do, what qualities would they have, what would be an indicator of them succeeding in their role, and everything else you'd put in a real job description. See screenshot 1. Once I had this job description, I started thinking about how to turn it into an agent flow. That framing — treating it like hiring a real person — ended up guiding every architectural decision we made. More on that later. Step 0: Build the Tools Before any of the agent work could happen, we needed Claude Code to be able to access our Google Workspace. That's where the consulting business lives — Gmail, Calendar, Drive, Sheets. Google does not have an official MCP server for their Workspace tools. But here's something most people don't know: MCP is simply a wrapper on top of an API. If you have an API for something, you basically have an MCP for it. I used Claude Code's MCP Builder skill — I gave it the Google Workspace API and asked it to build me an MCP server, and it did. Once it was confirmed that Claude Code could work with Google Sheets, that was the biggest unknown resolved, and we knew it would be able to do the work we needed. Version 1: Slash Commands Now it was time for context engineering. The first thing we tried was to create a bunch of slash commands — simple instructions that tell Claude what to do for each piece of work. This treated slash commands as text expanders, which is what they are, but it didn't work. It failed for one critical reason: using MCP tools to read our data sources and populate our sheets was very expensive in terms of context. By the time the agent was able to read our data sources and understand what was needed, it would be out of context window. We all know what that does to quality — it just drops drastically. So that didn't work. Version 2: Orchestrator and Sub-Agents This is also exactly when Anthropic released the new Tasks feature. We decided the new architecture would work by having our main Claude be the orchestrator of sub-agents, creating tasks that each get worked on by one sub-agent. But this ran into another unexpected problem. The main Claude would have its context window overwhelmed when it started 10 or more sub-agents in parallel. Each sub-agent would return a detailed report of what they did, and having so many reports sent to the orchestrator at the same time would overwhelm its context window. For example, our very first tasks launch data investigation agents which look at our raw data sources and create a detailed report about what has happened with a client over a specific period of time, based on a particular source like Gmail or Calendar. The output of these sub-agents needs to be read by all the sub-agents down the line — up to 35 of them. There would definitely be a loss in signal if it was the job of the main orchestrator to pass all required information between sub-agents. The Fix: A Shared Folder So we made one little change. We made every sub-agent output their final report into a temp folder and tell the orchestrator where to find it. Now the main Claude reads reports as it sees fit, and every downstream sub-agent can read the reports from earlier phases directly. This totally solved the problem. And it also improved communication between sub-agents, because they could read each other's full output without the orchestrator having to summarize or relay anything. See screenshot 2. Version 3: From Skills to a Handbook With the orchestration working, I initially created separate skills for each specific piece of work — gather-gmail, gather-calendar, check-accuracy, check-formatting, and so on. Eleven skills in total. Each sub-agent would read the skill it needed and get all the context for its task. This worked, but it was ugly. These were very specific, narrow skills, and it created all sorts of fragility in the system. Not to mention that it was difficult for even the humans to read and maintain. That's when the job description framing came back around. We started by treating this like hiring a real person. We wrote them a job description. So what do you do once you've actually hired someone? You give them an onboarding handbook — a document that covers how you approach things on your team and tells them to use it to get the job done, all aspects of their job. So that's what we built. One single project management skill that contains our entire handbook, organized into chapters: • Foundation — who we are, the team, our tools and data sources, when to escalate, data accuracy standards • Daily Operations — how to gather data from all our sources • Client Dashboards — how the dashboards are structured, what the master dashboard tracks, how to run quality checks • New Clients — how to onboard a new client and set up their dashboard from scratch Now when a sub-agent spins up, it reads the foundation chapters first (just like a new hire would), then reads the chapters relevant to its specific task. The handbook replaced eleven fragmented skills with one coherent source of truth. Here's what the final architecture looks like: See screenshot 4. What This Felt Like This was the most exhilarating work I've done in two weeks, and it was all of the things at once. Working with @NataliaZarina was the most important part. We were on calls for hours, running Claude Code sessions on each of our computers and trading inputs. She has the taste — she knows what the dashboards should look like, what the data should contain, what quality means for our clients. I have the AI engineering. Working together on this was genuinely exciting. Then there's the speed. We went through three major architectural generations in a span of two weeks. Everything was changing so fast. And what was actually the most exciting was how hard we were driving Claude Code. I've been using Claude Code for programming for months, but I was not driving it this hard before. This last couple weeks, I was consistently running out of my usage limits. In fact, both Natalia and I were running out of our combined usage limits on the ultimate max plans on multiple days. When you're consuming that much AI inference, you can imagine how fast things are moving. And that was just exciting as fuck. This was also a completely novel problem. Applied AI engineering as a discipline is still new, and this was the first real big shift in how I think about it. Why Now, and Why 2026 Here's why I opened with the claim that Claude Code for non-technical work will sweep the world in 2026. We realized that if you give Claude Code access to the tools you use as a non-technical person and do the work to build a workflow that covers how you actually use those tools, that is all you need. That's how non-technical work works. The reason this hasn't been done until now is that we were running Claude Code at its limits. This would not have been possible with a previous version of the AI or a previous version of Claude Code. We're literally using the latest features and the latest model. It requires reasoning through and understanding of the underlying tools and how to operate them, along with planning capabilities and context management capabilities that did not exist even six months ago. But now they do. And we're only in January. Every piece of the stack that made this possible is brand new: • MCP Builder skill — I built our own Google Workspace MCP server by asking Claude Code to use the Google Workspace API. That was not possible before Anthropic released MCP Builder on Oct 16, 2025 • Opus 4.5 — Its reasoning and planning capabilities made the entire orchestration possible. The agent needs to understand complex sheet structures, figure out what data goes where, and coordinate across dozens of sub-agents. Released Nov 24, 2025. • The Tasks feature — Sub-agent orchestration through Tasks made Version 2 and 3 possible at all. This was released Jan 23, 2026. That's why I'm saying Claude Code for non-technical work will sweep 2026. The building blocks just arrived.

Took a week to upgrade from Pro to Max. Longest week of my life.

@TheBTCTherapist BRICS ditching dollar to back UNIT as competing reserve currency

Holy hell. Who is buy all this gold and silver?

@lulumeservey Call it the socialist tax. Yes they will support it today. But when it harms California irreparably, then the people will associate that harm with socialism. Opportunity for a teachable moment.

Do NOT call it the Billionaire Tax or Wealth Tax In politics, naming is everything (eg “death tax” vs “estate tax”) The BILLIONAIRE TAX is named *perfectly* 3/4 of California voters want billionaires to pay more in taxes! If you oppose this bill, do NOT concede that it is a “tax” on “billionaires” If you are calling it by the name that its sponsors carefully gave it, you are losing

@lulumeservey I’m skeptical that trying to trick the populace to not be adversarial to billionaires with adversarial to billionaire messaging will work. If leftist want to be divorced from wealth then they will get that. This is a common historical occurrence. You reap what you sow. Good luck.

Optimal messaging for a California politician: “Billionaires don’t care about California. They don’t care if we go broke and can’t afford healthcare. They’re fairweather residents. Since this is just a transaction to them, they should pay their fair share to be here. I love California and care about our middle class, and I’m here to stick it out with you no matter what. I’m not going anywhere. So are you going to vote with me, with us, or with the carpetbagger billionaires?” Please don’t give them the ammo for this.

@iAnonPatriot No turning back for California now.

Never forget when Los Angeles REMOVED U-turn signs because they offended the LGBTQ community.. We’re living in a South Park episode. 😭😭

@Prathkum A new generation of developers will show up who only know how to debug code with an LLM.

A new generation of developers will show up who can’t debug their own logic because they have outsourced their entire mental model to an LLM.