<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Timothy Biondollo on Medium]]></title>
        <description><![CDATA[Stories by Timothy Biondollo on Medium]]></description>
        <link>https://medium.com/@timbiondollo?source=rss-63a1bdd30ff8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Lt7rLlbTCkRYhHxzD1q5Qg.jpeg</url>
            <title>Stories by Timothy Biondollo on Medium</title>
            <link>https://medium.com/@timbiondollo?source=rss-63a1bdd30ff8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 23:06:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@timbiondollo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Let Claude Install Your Next GitHub Find in Twenty Minutes]]></title>
            <link>https://medium.com/@timbiondollo/let-claude-install-your-next-github-find-in-twenty-minutes-c4bcf8752dc5?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4bcf8752dc5</guid>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 16:01:21 GMT</pubDate>
            <atom:updated>2026-11-07T16:01:21.558Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKYpH1UToSGzlzQjGd0mAw.jpeg" /><figcaption>Ai doing Ai stuff abstractly</figcaption></figure><p><em>Hand the setup to Cowork, end up with a fully local voice studio, and fix an MCP that was never meant to work here.</em></p><p>Ever run across a cool open source app on GitHub and not have the time or bandwidth to set it up and mess around with it?</p><p>You star the repo. You tell yourself you will get to it. You never do. Not because it is hard, but because between you and the app there is a download page, a wall of system requirements, a terminal command, and three permission prompts you would have to read.</p><p>Well, have I got something for you.</p><p>This walkthrough covers three things. How to let Claude do the setup for you while you watch. How to get VoiceStudio running, a viral open source app that does voice cloning and dubbing entirely on your own machine. And an accidental third thing I ran into along the way: how to make an MCP that was built for Claude Code work in Cowork instead.</p><p>The whole thing takes about twenty minutes, and most of that is a download bar.</p><h3>What you are setting up</h3><p>Two pieces.</p><p><strong>Cowork with computer access.</strong> Claude can see your screen and use your mouse and keyboard. You approve specific apps, one dialog, and it can only touch the ones you named. You can revoke it whenever.</p><p><strong>VoiceStudio.</strong> An open source desktop app that clones voices, designs new ones, dubs video into other languages, transcribes, and builds audiobooks. It runs entirely on your hardware. No account, no API key, no per-character billing, and your audio never leaves the machine. It went from a few thousand GitHub stars to twenty one thousand in about two weeks, which is why it is in your feed right now.</p><p>You need an Apple Silicon Mac, Windows 10 or 11, or Linux. If you are on an Intel Mac, stop here. The app will install and open and then never work, because the engine underneath it stopped shipping Intel builds.</p><h3>Part one: let Claude do the install</h3><h3>Step one: turn on computer access</h3><p>In Cowork, ask Claude to install something and it will request access to the apps it needs. You will get one dialog listing them. Approve it.</p><p>You will be granting Finder, and later the app itself. That is it. Claude cannot see anything you did not list.</p><h3>Step two: paste the prompt</h3><p>Start a new chat and paste this, with the app name filled in:</p><blockquote><em>Install VoiceStudio on my Mac and connect it to Cowork. Show me the file name, size, and publisher checksum before you download anything, and wait for my okay. Stop and hand me the decision at any security warning or system permission. Prove it works at the end with a real test, not just “installed.”</em></blockquote><p>That is the short version. There is a fuller one at the bottom of this piece worth using for anything more involved.</p><h3>Step three: approve the download</h3><p>Claude will find the release page, work out which of the nineteen files matches your machine, and come back with the details before pulling anything down. For an Apple Silicon Mac that is VoiceStudio_0.5.1_aarch64.dmg, about 105 MB.</p><p>Say yes. It downloads, mounts the disk image, and drags the app into Applications.</p><h3>Step four: get past the security warning</h3><p>This is the step everyone hits, and the official instructions for it are wrong.</p><p>macOS will refuse to open the app and tell you it cannot verify the software is free of malware. That is not a red flag about the code. The developer has not paid for Apple’s notarization, which costs $99 a year, so macOS quarantines the download.</p><p>The repo tells you to right-click the app and choose Open. <strong>That stopped working two macOS versions ago.</strong> On current macOS you do this instead:</p><ol><li>Double-click VoiceStudio in Applications. Dismiss the warning.</li><li>Open <strong>System Settings → Privacy &amp; Security</strong> and scroll to the Security section.</li><li>Find the line about VoiceStudio being blocked and click <strong>Open Anyway</strong>.</li></ol><p>One time per install. After that it opens on a double-click.</p><p>Claude will not click through this one for you, and that is correct. Overriding a malware warning is your call, not the agent’s. What it will do is tell you why the warning is there and confirm the file you downloaded matches the checksum the publisher posted, so you are deciding with actual information.</p><h3>Step five: grant Accessibility</h3><p>The setup wizard will not move past its system check until you grant Accessibility. It uses it for dictation, so it can type transcripts into whatever app you are in.</p><p><strong>System Settings → Privacy &amp; Security → Accessibility → toggle VoiceStudio on.</strong> Then click Re-check in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*cYDWA2LyLInRAH3xToFzmw.jpeg" /></figure><p>Worth knowing what you are agreeing to: Accessibility lets an app read and control other apps. It is one of the strongest permissions on a Mac. This app has a real reason to want it, but it asks before doing anything at all, even things that never touch dictation. Grant it or do not, but grant it knowingly.</p><p>Microphone will say “not asked yet” and stay that way. It is not a blocker, so ignore it.</p><h3>Step six: let the wizard run</h3><p>From here it is mostly waiting, and Claude handles it.</p><p>Dependencies take about eight minutes. The app narrates each step, so when it says “step 4 of 9” it is working, not frozen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*4IMXh2cwXWhqZ0q94SzwGA.jpeg" /></figure><p>At the model screen, read carefully. <strong>The setup screen says you need about 17 GB. You do not.</strong> Only the top item is required, the 2.4 GB TTS model. Everything below it is optional transcription models you can add later from Settings. Download the required one, skip the rest, and you are through in two minutes instead of twenty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*hEDZLVvOkYAfIew1WxG0Eg.jpeg" /></figure><p>Then say no thanks to the analytics prompt, and you land in the studio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*_G32DzPJMwqSC6TFB3qUYw.jpeg" /></figure><h3>Part two: use it</h3><h3>Make your first voice</h3><p>Open <strong>Voice Clone</strong>. Drop in a clean recording. Type what you want it to say, pick a language, hit Generate.</p><p>Clean beats long. Ten to fifteen seconds of quiet audio beats two minutes of noisy audio every time, because whatever is in the background of your reference shows up in the output. Anything over 75 seconds gets rejected and asked to be trimmed.</p><p>Clone your own voice or one you have written permission to use. This will clone anybody from a three second clip, which is exactly as much of a problem as it sounds. The app watermarks its output by default so generated audio can be identified later. Leave that on.</p><p>If you would rather not clone anyone, use <strong>Voice Design</strong> and describe a voice that does not exist. “Warm British storytelling voice, mid forties, unhurried” gets you a narrator with nobody’s face attached. For most work purposes this is the better door.</p><h3>Dub a video</h3><p>Drop a video in, pick the output language. It transcribes, translates, works out who is speaking, and re-synthesizes the whole thing in the original speaker’s voice.</p><p>You get a transcript editor with per-line timing, so a bad translation is a one-line fix rather than a re-run. Put your product names in the glossary before they become poetry in Japanese. Multi-speaker footage gets a casting board where you drag a voice onto each person.</p><p>This is the highest-value thing in the app and the one I would try first.</p><h3>Part three: make any local MCP work in Cowork</h3><p>Here is the accidental third thing, and it is the most reusable part of this piece.</p><p>VoiceStudio ships an MCP server. That is the bit that lets Claude use the app directly: generate speech, clone a voice, transcribe audio, without you opening a window. The README says to add it as a connector.</p><p><strong>That does not work, and it cannot.</strong> Connectors are reached from Anthropic’s servers, not from your laptop. So an address pointing at localhost sends them looking on their own machine. The URL field rejects it before you even get that far.</p><p>Claude Code does not have this problem, because Claude Code runs on your machine. That is what the developers built for, and it is why you will hit this again. Plenty of local-first tools ship an MCP server aimed at Claude Code, and none of them connect to Cowork.</p><p>Cowork’s mechanism for local connectors is a Desktop Extension, a small file that runs on your machine and relays messages. Most projects have not shipped one.</p><p>So have Claude build you one so you can use VoiceStudio in cowork. Paste this:</p><pre>VoiceStudio is running on my machine and serves an MCP server at<br>http://localhost:3900/mcp/ that I cannot add to Cowork as a connector,<br>because connectors resolve from Anthropic&#39;s servers and cannot see my<br>localhost. Build me a Desktop Extension (.mcpb) that bridges it.Then install what it builds:</pre><ol><li><strong>Settings → Extensions → Advanced settings → Extension Developer → Install Extension.</strong></li><li>Select the .mcpb file.</li><li>Make sure VoiceStudio is open, then start a new chat.</li></ol><p>Ask Claude to check VoiceStudio’s health. If you get back status: ok with your device listed, the bridge is live.</p><p>Now ask for audio. <em>“Say ‘it works’ in the demo voice.”</em> You get back a real WAV, generated on your machine, and it lands in VoiceStudio’s history so you can play it.</p><p>Expect the first one to be slow. Mine took 9.5 seconds to make 1.5 seconds of audio, because the first request of a session loads the model into memory. Every one after is quick. Do not judge the speed by the first take.</p><p>Two things that will trip up whatever it builds, so watch for them. The endpoint in the docs is missing a trailing slash, and without it the server returns an error rather than redirecting. And responses come back as event streams even for ordinary calls, which breaks a bridge that assumes plain JSON. If Claude probes the server first like the prompt tells it to, it finds both.</p><p>Swap the app name and the address and that prompt works for any local MCP server you run into. That is the part worth keeping.</p><h3>Four habits that save you time</h3><p><strong>Let Claude read the wizard.</strong> The 17 GB versus 2.4 GB thing is the whole argument for this approach. It read the fine print and picked the small correct option. You would have clicked the big obvious button.</p><p><strong>Say what you want it to stop at, up front.</strong> Agents are good at momentum and bad at knowing when momentum is wrong. One sentence in your prompt about security warnings and permissions is what turns “it did the whole thing” into “it did the whole thing and checked with me twice.”</p><p><strong>Do the first one on something disposable.</strong> Pick an app you would not mind uninstalling. Watch how it behaves at the permission prompts. That tells you whether to hand it the next job.</p><p><strong>Test the small thing before the big thing.</strong> Generate one sentence before you queue an hour of audio. Dub thirty seconds before you dub the webinar.</p><h3>What it costs</h3><p>The app is free. Your hardware is the cost, plus 10 to 20 GB of disk once you have a couple of engines.</p><p>One catch before you sell anything made with it: the app is open source under a license that allows commercial use, but the default voice model ships under a non-commercial license, and models keep their own terms regardless of the app’s. If money is involved, switch to one of the permissively licensed engines like CosyVoice or MOSS first. This is the thing most people will skip and then regret.</p><p>It also still calls itself a beta. Use the tagged release, not the development branch, and do not put it on the critical path of a client deliverable due Friday.</p><h3>The prompt worth keeping</h3><p>The short prompt above is fine for a simple app. This is the one to use for anything with a real installer:</p><pre>Install and set up [APP NAME] on my Mac. Work through it with me, and stop<br>whenever a decision is mine rather than yours.</pre><pre>STEP 1: CHECK BEFORE YOU DOWNLOAD. Find the official source. Confirm which<br>build matches this machine, including chip and OS version. If it cannot run<br>on my hardware, tell me now and stop. Show me the filename, size, and<br>publisher checksum, and wait for my okay.</pre><pre>STEP 2: SHOW ME THE REAL COST. Before installing, tell me total disk space,<br>how long it will take, what accounts or keys it needs, and what permissions<br>it will ask for. If the official docs and the installer disagree on any<br>number, say so and trust the installer.</pre><pre>STEP 3: DO THE TEDIOUS PART. Download, install, run the wizard. Read the<br>fine print I would skip: pick the smallest option that actually works rather<br>than everything the wizard suggests, and choose the privacy-preserving<br>answer on any tracking question. Narrate in plain language, not app jargon.</pre><pre>STEP 4: STOP AT THESE, ALWAYS. Do not click through security warnings. Do<br>not grant system permissions. Do not turn off protections. When you hit one,<br>tell me what it is, why it is appearing, whether it is expected for this<br>software, and what the actual risk is. Then let me decide. If I ask you to<br>disable a protection globally, push back and give me the narrowest version<br>that solves the problem.</pre><pre>STEP 5: PROVE IT WORKS. Do not stop at &quot;installed.&quot; Run the smallest real<br>test that shows it functions and show me the output. If the official<br>instructions fail, work out what actually works and tell me which<br>instruction was wrong.</pre><pre>STEP 6: HAND IT OFF. Tell me what got installed, where it lives, what I<br>granted it, what it costs to run, the first useful thing to try, and how to<br>uninstall it cleanly if I change my mind.</pre><p>Step 4 is the one that matters. It is not there to sound responsible. It is there because you want handing you the decision to be the default behavior rather than a lucky one.</p><h3>Try it this week</h3><p>Open the tab you have been avoiding. Paste the prompt. Watch.</p><p>You will read more than you click. You will take over two or three times. And you will end up with the thing installed, which, be honest, was not going to happen otherwise.</p><p>Then point it at the next one.</p><p><em>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent Claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece.</em></p><p><em>→ Subscribe to my weekly newsletter for AI operators at</em> <a href="http://rogue-orchestrators.beehiiv.com/"><em>rogue-orchestrators.beehiiv.com</em></a></p><p>*<em>Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><h3>Sources</h3><ul><li>VoiceStudio repository: <a href="https://github.com/debpalash/VoiceStudio">https://github.com/debpalash/VoiceStudio</a></li><li>VoiceStudio releases: <a href="https://github.com/debpalash/VoiceStudio/releases/latest">https://github.com/debpalash/VoiceStudio/releases/latest</a></li><li>VoiceStudio macOS install guide: <a href="https://github.com/debpalash/VoiceStudio/blob/main/docs/install/macos.md">https://github.com/debpalash/VoiceStudio/blob/main/docs/install/macos.md</a></li><li>VoiceStudio MCP guide: <a href="https://github.com/debpalash/VoiceStudio/blob/main/docs/mcp.md">https://github.com/debpalash/VoiceStudio/blob/main/docs/mcp.md</a></li><li>Trendshift trending stats: <a href="https://trendshift.io/repositories/28176">https://trendshift.io/repositories/28176</a></li><li>Getting started with local MCP servers on Claude Desktop: <a href="https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop">https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop</a></li><li>When to use desktop and web connectors: <a href="https://support.claude.com/en/articles/11725091-when-to-use-desktop-and-web-connectors">https://support.claude.com/en/articles/11725091-when-to-use-desktop-and-web-connectors</a></li><li>Anthropic Desktop Extensions documentation: <a href="https://github.com/anthropics/mcpb">https://github.com/anthropics/mcpb</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4bcf8752dc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is Agent Reach? 5 Ways to Use It in Claude Cowork]]></title>
            <link>https://medium.com/@timbiondollo/what-is-agent-reach-5-ways-to-use-it-in-claude-cowork-f6393e9c719d?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6393e9c719d</guid>
            <category><![CDATA[agents]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[claude-cowork]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 17:09:38 GMT</pubDate>
            <atom:updated>2026-11-06T03:48:51.775Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2V1bq6FS5GCYSfTo6tzSlw.jpeg" /><figcaption>An image of an agent accessing social media</figcaption></figure><p><em>Agent Reach lets your AI agent read Reddit threads, YouTube comments, and the rest of the internet companies don’t write. Why that matters if you build or sell anything alone, and the Claude Cowork skill that makes it work.</em></p><p>The internet has two halves. The half companies write, and the half people write.</p><p>The company half is the website, the docs, the pricing page with the word “simple” on it. It’s what they want you to believe. The people half is the Reddit thread, the YouTube comments, the forum post at 1am. That’s where somebody says what broke, what they’d actually pay, and what they switched to last month.</p><p>Your AI agent has only ever read the company half. Hand it a Reddit link and it can’t open it. So you’ve been reading the people half yourself and summarizing it for the thing that’s supposed to summarize things for you.</p><p>Here’s what happens when that stops. I told my agent: find the top Reddit threads complaining about NotebookLM, read them, rank the pain points by how many people share them. It came back with a thread called “NotebookLM is dumb now.” 144 upvotes, 48 comments (linked at the bottom). The comments were a product spec. Hallucinations since the Gemini update. Lazy answers. No way to plug in a better model. And the rival people were leaving for, a smaller tool called Nouswise. About ten minutes. That’s a roadmap, in the words your future customers will type into Google.</p><p>That’s Agent Reach, and it works in Claude Code out of the box. If you use Claude Cowork, stick around: I built a skill that gets it running there in about thirty seconds.</p><h3>What is Agent Reach, and what was it built for?</h3><p>Agent Reach is a free, open-source tool that gives an AI agent working ways to read the sites that block it. Any web page. YouTube videos and their comments. Live web search. GitHub. RSS feeds, the plain-text versions of blogs and news sites. The project has kept that list current as sites change. It installs what’s needed and tells your agent which way to use. No API keys. No bill. 96,000 GitHub stars in eight months, as of October 12, 2026.</p><p>It was built for two agent apps: Claude Code and OpenClaw, an open-source alternative. Cowork needs a little help. More on that below.</p><h3>What is Claude Cowork good for with Agent Reach? My top 5 use cases</h3><p>Claude Cowork is the desktop version of Claude that works on your files and runs jobs while you do something else. With Agent Reach added, it’s good for one thing above all: research you hand off instead of research you do. One person. A vibe-coded app, a YouTube channel to market it, a blog nobody’s found yet. These aren’t prompts. They’re jobs. The agent takes the thirty steps while you make lunch, and the answer lands in the chat, or in a file if you ask.</p><h3>1. Find what to build by mining the complaints</h3><p>“Find the top Reddit threads complaining about [the thing you’d compete with]. Read them. Rank the pain points by how many people share them, in their words.” That’s the NotebookLM run above, with your competitor’s name in the blank.</p><h3>2. Check what already exists before you build it</h3><p>“Search GitHub for anything that already does this. Read the docs for the top three. Then find what their users complain about.” You find out whether you’re building a product or a feature, before the weekend.</p><h3>3. Can Claude watch YouTube videos? Yes, and read the comments</h3><p>With Agent Reach, Claude can pull a video’s transcript and its comments. “Pull the ten most-watched videos in my niche this month, their transcripts, and their comments. Give me the questions people keep asking and the exact phrases they use.” Your titles stop sounding like you. They start sounding like them.</p><h3>4. Keep the watch running every week</h3><p>“Every Friday, re-read these threads and these competitor pages. Compare to last week. Only tell me what changed.” Most weeks it says nothing. That’s the point.</p><h3>5. Read the page Claude says it can’t open</h3><p>Dashboards, docs sites, anything that loads like an app. “Read this page and tell me what they changed since the version in my notes.” The agent reads it as plain text. You stop copy-pasting pages into the chat.</p><h3>How to use Claude Cowork scheduled tasks with Agent Reach</h3><p>To make use case four run on its own, create a scheduled task in Cowork. Tell it: “Every Friday at 7am, set up agent reach, re-read these threads and pages, and message me only if something changed since my research notes.” Week one, it writes the baseline. Every week after, it reads while you sleep, as long as your computer is on, and that folder slowly turns into a memory of your market.</p><h3>Claude Cowork vs OpenClaw: which one runs Agent Reach?</h3><p>Out of the box, Agent Reach runs on OpenClaw and Claude Code, not Cowork. In Cowork it stalls. Cowork’s workspace is a hotel room. Spotless every time you check in. Nothing you left is still there. Agent Reach’s installer assumes a room you own.</p><h3>The Agent Reach skill for Claude Cowork</h3><p>The Agent Reach skill for Claude Cowork installs everything, tests each source, and tells you which ones came back with real data and which didn’t. Thirty seconds.</p><p>Grab it here: <a href="https://github.com/archaeus-ai/agent-reach-cowork/raw/main/agent-reach-cowork.skill.">https://github.com/archaeus-ai/agent-reach-cowork/raw/main/agent-reach-cowork.skill.</a> That downloads one file. Go to your Claude desktop app, click customize &gt; skills &gt; add new &gt; upload and select the file you just downlaoded. Then say “set up agent reach” at the start of a session. It asks one optional question about two free keys, one for search and one for GitHub. Skip them if you want. Then it tells you what’s live and what just became possible.</p><h3>Claude Code vs Claude Cowork: how to install Agent Reach from GitHub</h3><p>Claude Code: paste “Install Agent Reach: https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md&quot; and let it work. It reads the guide, checks your machine, and asks before it touches anything.</p><p>Claude Cowork: the skill above, then “set up agent reach.”</p><h3>Is Agent Reach safe to use in Claude Cowork and at work?</h3><p>On your own machine, for your own research: yes. One honest line. The YouTube part uses a downloader called yt-dlp, and that sits outside YouTube’s terms, which ban automated downloads. A legal team can still point at it. The Reddit part reads a public search index, the same kind Google uses. No login. No cookies.</p><p>The hard no is the login sources: Twitter, Instagram, LinkedIn, and signing into Reddit. Those run on stored cookies and an agent-driven browser. The platforms ban it. The project’s own docs suggest a throwaway account and a $1-a-month proxy to dodge rate limits. That sentence ends security reviews.</p><p>Stay on the no-login half. It already reaches the half of the internet that tells the truth.</p><p>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent Claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece.</p><p><em>Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><p>Sources</p><p>Agent Reach repository (star count checked October 12, 2026): <a href="https://github.com/Panniantong/Agent-Reach">https://github.com/Panniantong/Agent-Reach</a> The Agent Reach skill for Claude Cowork (source and README): <a href="https://github.com/archaeus-ai/agent-reach-cowork">https://github.com/archaeus-ai/agent-reach-cowork</a> Agent Reach English README: <a href="https://github.com/Panniantong/Agent-Reach/blob/main/docs/README_en.md">https://github.com/Panniantong/Agent-Reach/blob/main/docs/README_en.md</a> Agent Reach install guide: <a href="https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md">https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md</a> The NotebookLM thread from the opening example (r/notebooklm, August 21, 2026): <a href="https://www.reddit.com/r/notebooklm/comments/1vu7coc/notebooklm_is_dumb_now/">https://www.reddit.com/r/notebooklm/comments/1vu7coc/notebooklm_is_dumb_now/</a> Independent review (gittested, August 14, 2026): <a href="https://gittested.com/reviews/agent-reach/">https://gittested.com/reviews/agent-reach/</a> YouTube Terms of Service: <a href="https://www.youtube.com/t/terms">https://www.youtube.com/t/terms</a> Exa MCP and API keys: <a href="https://dashboard.exa.ai/api-keys">https://dashboard.exa.ai/api-keys</a> Jina Reader: <a href="https://jina.ai/reader">https://jina.ai/reader</a> yt-dlp: <a href="https://github.com/yt-dlp/yt-dlp">https://github.com/yt-dlp/yt-dlp</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6393e9c719d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Give Your AI Agent Long-Term Memory in an Afternoon (No RAG, No Database)]]></title>
            <link>https://medium.com/@timbiondollo/how-to-give-your-ai-agent-long-term-memory-in-an-afternoon-no-rag-no-database-f4aa027df8d7?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4aa027df8d7</guid>
            <category><![CDATA[notebooklm]]></category>
            <category><![CDATA[ai-memory]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[memory-graph]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 00:21:48 GMT</pubDate>
            <atom:updated>2026-11-06T03:49:20.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBB_qViemfC6QacaemyaTg.jpeg" /><figcaption>An iamge of a detective’s cork board illustrating how a memory graph works</figcaption></figure><p><em>What a memory graph is in plain English, why everyone suddenly wants one, and how to build yours today. No budget meeting required.</em></p><p>A project called claude-mem is sitting at 97,000 GitHub stars this week, and it picked up 628 of them in a single day. It does one thing. It stops your AI coding agent from forgetting everything the second you close the window.</p><p>That’s the whole feature. And people are losing their minds over it, which tells you something about how we’ve all been living.</p><p>Here’s how we’ve been living. You open a chat. You explain your project. You explain it again tomorrow. Your AI is the smartest coworker you’ve ever had, and every single morning is its first day.</p><p>So now everyone wants their agent to have a memory. Good. But most of the ways people are about to try it are slow, expensive, and end in a meeting with someone who controls a budget. There’s a cheaper way. It’s called a memory graph, and you can build one before dinner.</p><h3>What is a memory graph, exactly?</h3><p>It’s a corkboard, not a filing cabinet. Picture a detective’s corkboard. One index card for every thing that matters: a client, a project, a decision you made in March and already regret. Red string between the cards that connect. When you ask a question, the AI doesn’t rummage through the whole wall. It finds the right card and follows the string.</p><p>That’s it. That’s a memory graph. A folder of plain text files that know what they’re connected to. No database. No server. Nothing to host. If you can make a folder, you’re qualified.</p><p>The thing everyone sells you instead is called RAG, and it works like a very enthusiastic paper shredder. It chops your documents into confetti, and when you ask a question, it hands the AI the ten pieces of confetti that sound the most like what you asked. Sometimes that’s enough. Sometimes you asked which three clients got hit by the same vendor mess, and no single piece of confetti knows that, because the answer lives in the string between the cards, and the shredder cut the string.</p><h3>How much does RAG really cost?</h3><p>RAG is “cheap” the way a free puppy is cheap. Ask anyone who’s built one. A proper RAG setup, the kind that survives contact with real users, runs somewhere between $12,000 and $60,000 and takes one to three months, according to the firms that build them for a living. Then it keeps eating. One of those firms found teams losing 20 to 30 percent of every sprint just keeping it fed: re-indexing when a document changes, fixing a connector, figuring out why it confidently gave the wrong answer. Those numbers come from vendors, so round them however you like. The direction isn’t in dispute by anyone who’s lived it.</p><p>The memory graph version? Microsoft’s GraphRAG team built a full knowledge graph out of a million tokens of text, roughly a fat novel, for $20 to $50. Andrej Karpathy built his over a weekend out of markdown files, and the only cost anyone’s been able to pin on it is API calls. One engineer who did the same wrote that getting a fresh AI session up to speed on his project went from three minutes of explaining to under thirty seconds.</p><p>A single person. A folder. An afternoon. No budget meeting, which is where good prototypes go to die.</p><h3>When should you use a memory graph instead of RAG?</h3><p>I’m not going to pretend it’s magic. A memory graph is for knowledge that holds still: your docs, your decisions, your research, the stuff you keep re-explaining. If your data changes every five minutes, the string goes stale and nothing taps you on the shoulder. Fine. That’s not what you’re building a Friday demo out of anyway.</p><p>But if your boss wants to see something working by Friday, and the “correct” path is a six-week RAG build, this is the move. Not because it’s trendy. Because it’s done by dinner.</p><h3>How do you build a memory graph?</h3><p>Today, not next quarter. Here’s the whole thing. Pick one folder of documents you keep re-explaining. Open Claude or ChatGPT, point it at that folder, and paste this:</p><pre>You are the orchestrator for building a memory graph from a local folder. A memory graph is a set of markdown files with YAML frontmatter and bidirectional links (links_to / links_from), plus an index at every root, that a human and an AI can both navigate without a database. This runs in an agentic harness (Claude Code or similar). Use subagents for parallel work. If your harness has no subagents, play each role yourself, one at a time, and still follow the gates.<br><br>## Ground rules (never break these)<br><br>1. Never work on the original folder. Copy it first. Everything you read, write, or run happens inside the copy.<br>2. Scripts own structure. Humans and LLMs own judgment. links_to, links_from, the registry, and the indexes are written only by scripts. Never hand-edit them. If a link is wrong, fix the rule and rerun.<br>3. Nothing a subagent tells you is true until you check it against the filesystem. Counts, paths, &quot;done&quot;, &quot;all files have frontmatter&quot;: verify with a command, not trust.<br>4. Keep your own context small. Subagents return short reports (numbers, lists, paths, problems), never file contents. You read samples, not everything.<br>5. Stop and wait for the user at every gate marked GATE. Do not proceed on your own.<br>6. Save every script you write next to the output so the user can rerun the whole build later.<br><br>## Phase 0: Guided intake (GATE: confirmed brief required)<br><br>Before touching any files, run a short interview to understand what this graph is for. The goal is a one-page brief the user agrees with, not a questionnaire.<br><br>Start with what you already know. Check memory, CLAUDE.md, project notes, and recent conversation for anything about this person: what they work on, how they organize things, tag or folder conventions they already use, tools they live in (Obsidian, git, a specific editor), what they have complained about before. Also glance at the folder itself (names, structure, file types, dates) so your questions are informed, not generic. Lead with what you inferred (&quot;It looks like this is client research from the last year, organized by client, mostly PDFs. Is that right?&quot;) and let them correct you. Do not ask a question you can already answer.<br><br>Then ask, two or three questions at a time, adapting to their answers:<br>- Purpose: what will they do with this graph that they cannot do today? What decision, task, or workflow is it for?<br>- The questions: get three to five real questions they want to ask it, in their words. Push for at least two whose answers live across several documents. These become the acceptance tests.<br>- Who reads it: just them, their AI agents, a team, all three? This changes how much the indexes and descriptions matter.<br>- What &quot;good&quot; looks like: how will they know it worked? A specific moment, like &quot;I stop re-explaining the project every morning.&quot;<br>- Scope: what is in, what is out, and what is junk. Any sensitive material that must not be included or must stay out of descriptions.<br>- Freshness: does the source change? How often? Do they need to rerun this, and should the build be incremental?<br>- Where it lives: local only, a git repo, an Obsidian vault, shared with a team. Any naming or structure conventions to match.<br>- Existing vocabulary: tags, categories, project codes, or client names they already use. Reuse these as facet values instead of inventing new ones.<br><br>Be a good interviewer. Follow up on vague answers. Offer defaults when they hesitate. Keep it under ten minutes of their time. If they clearly want to skip ahead, propose sensible defaults, say so, and move on.<br><br>Write the result to &lt;output&gt;/BRIEF.md: purpose, the acceptance questions, audience, definition of good, scope and exclusions, sensitivities, freshness and rerun plan, where it lives, vocabulary to reuse, and the defaults you assumed. Show it to the user. Stop. Do not clone or build until they confirm the brief.<br><br>## Phase 1: Clone and inventory (scripts only)<br><br>- Copy the source folder to &lt;output&gt;/raw/. Treat raw/ as read-only from this point on.<br>- Write and run an inventory script that walks raw/ and writes &lt;output&gt;/registry.json: one entry per file with a stable id, relative path, extension, size, and a title guess from the filename or first heading. Apply the exclusions from the brief. Print counts by extension and by top-level subfolder.<br>- If there are non-markdown sources (PDF, DOCX, HTML, etc.), convert them to markdown into &lt;output&gt;/graph/ with a script using whatever tools are installed. Each converted file keeps a `source:` field pointing at its raw/ path. Report what could not be converted. Do not summarize or rewrite content during conversion.<br>- Verify: registry count equals the in-scope file count on disk. If it does not, fix the script before moving on.<br><br>## Phase 2: Survey (subagents, sampled)<br><br>Spawn two or three survey subagents in parallel. Give each a different slice of the registry (by subfolder or by type), the brief, and this instruction: open a sample of 10 to 20 files, not all of them, and report back in under 300 words: what kinds of knowledge are here, which entities recur (people, projects, clients, tools, decisions), what looks like a natural silo, what looks like junk, how well the user&#39;s existing vocabulary fits what you see, and anything surprising.<br><br>Then be skeptical. Spot-check two claims from each report against actual files. Note where the reports disagree. If the picture is unclear, send one more targeted survey. Do not plan from reports you have not checked.<br><br>## Phase 3: Plan (GATE: user approval required)<br><br>Write &lt;output&gt;/PLAN.md and show it to the user. It must reflect the brief and contain:<br>- Root folders: one per knowledge silo, named plainly, with a one-line reason each.<br>- Hierarchy inside each silo (flat, by topic, by source, by date) and why.<br>- Facets: the tags every file will carry (for example topic, source, project, person, status, confidence), with the allowed values for each, reusing the user&#39;s existing vocabulary wherever it fits, so tags stay consistent and greppable.<br>- Frontmatter schema every file will carry: title, description, source (path into raw/), tags (one key per facet), links_to, links_from. Keep it valid YAML and Obsidian-compatible.<br>- Linking rule, stated precisely enough that a script can apply it. Examples: a markdown link to another file in the set; a mention of an entity that has its own file; two files derived from the same raw source. Say which of these count and which do not.<br>- Index plan: an index.md at every root folder, and one llms.txt at the top of &lt;output&gt;/graph/ listing every file grouped by silo with a one-line description.<br>- Acceptance tests: the user&#39;s questions from the brief, plus the checks in Phase 5.<br><br>Stop. Wait for the user to approve or edit the plan. Do not create or move any files until they do.<br><br>## Phase 4: Build (scripts, then verify)<br><br>- Delegate script writing to a subagent. Give it PLAN.md and registry.json. It writes a self-contained Python script (stdlib plus pyyaml) with a config block at the top and two passes. Pass one: scan every file in graph/, parse frontmatter, apply the linking rule, and build outgoing and backlink maps keyed by registry id. Pass two: write links_to (relative paths) and links_from ({title, path}) into each file&#39;s frontmatter, rewrite in-body references to relative markdown links, add a short LLM navigation comment, and remove empty links_to / links_from keys. Rules: relative paths only, forward slashes, prefix ./ unless it starts with ../, no self-links, no duplicates, frontmatter stays valid YAML, never touch raw/. Save it as &lt;output&gt;/build_graph.py.<br>- Second subagent writes &lt;output&gt;/generate_index.py that produces index.md at every root and llms.txt at the top, grouped by silo, sorted, with a description per entry.<br>- You run both scripts yourself. Read the output. Then run a verification script you write: every file has valid frontmatter with every schema field; every links_to path resolves to a real file; every links_from has a matching links_to on the other side; no self-links; every file appears in llms.txt; list orphans (no incoming links) and dead ends (no outgoing links).<br>- Report numbers: files, total links, average per file, ten most-linked files, orphan count. If verification fails, fix the script, rerun, re-verify. Do not patch files by hand.<br><br>## Phase 5: Polish and evaluate (loop until good enough)<br><br>- Polish via subagents in batches of 20 to 40 files. Each subagent improves description and tags only (within the allowed facet values), flags files that look misfiled, respects the sensitivities in the brief, and proposes cross-links the rule missed. It returns a short report. It does not touch links_to or links_from.<br>- After each batch, verify: rerun the verification script, spot-check three files from the batch against their raw source for drift. Reject and redo a batch that invents content or breaks the schema.<br>- Where a proposed cross-link is valid, add the rule, not the link. Rerun build_graph.py and generate_index.py.<br>- Then evaluate against the acceptance tests. Spawn a fresh subagent with no memory of the build. Give it only the output folder and the user&#39;s questions from the brief. It must answer each by starting at llms.txt, following links, and citing the files it used. Grade each answer yourself: correct, grounded in the right files, found via the graph (not by reading everything). Also grade against the user&#39;s definition of good from the brief, and check that a human can open graph/ in Obsidian and see a connected graph, not a cloud of orphans.<br>- If any test fails, diagnose (missing link rule, bad silo, bad tags, bad description), fix at the rule or plan level, rebuild, and run the evaluation again. Up to three rounds. If still failing, stop and tell the user exactly what is failing and the choices.<br><br>## Done means<br><br>All of these, verified by you, not reported by a subagent: originals untouched; registry matches disk; every file has the schema; every link resolves in both directions; every root has an index; llms.txt lists everything; the user&#39;s questions are answerable by traversal; the brief&#39;s definition of good is met; scripts saved for rerun. Then write &lt;output&gt;/REPORT.md with the numbers, the orphans, what was excluded or could not be converted, how to rerun, and, if the brief said the source changes, the recommended rerun cadence.</pre><p>Now ask it a question whose answer lives across three of those documents. The kind of question that would’ve made the shredder cry.</p><p>If it finds the connection, congratulations, you just built the thing. If it doesn’t, you lost an afternoon and learned something real, which is a better deal than most demos I’ve sat through.</p><p>I built a bigger version of this as a plugin that crawls an entire website and turns it into a agentic memory graph. Next piece, I’ll build one on screen, screenshots and all, so you can see what it looks like inside before you decide whether it’s worth your Friday.</p><p>* * *</p><p>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent Claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece.</p><p><em>Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><h3>Sources</h3><p><a href="https://github.com/thedotmack/claude-mem">claude-mem, persistent context across sessions for every agent: https://github.com/thedotmack/claude-mem</a></p><p><a href="https://www.coddykit.com/pages/blog-detail?id=5129957&amp;slug=github-trending-october-2026-from-persistent-agent-memory-to-open-source-capcut-">The 628-stars-in-a-day figure (GitHub trending roundup, October 5, 2026): https://www.coddykit.com/pages/blog-detail?id=5129957&amp;slug=github-trending-october-2026-from-persistent-agent-memory-to-open-source-capcut-</a></p><p><a href="https://www.raftlabs.com/blog/rag-development-cost">RAG build cost and timeline breakdown (Raftlabs, 2026): https://www.raftlabs.com/blog/rag-development-cost</a></p><p><a href="https://www.brainfishai.com/blog/the-hidden-cost-of-rag-maintenance-when-knowledge-pipeline-work-consumes-your-sprint">The sprint-time cost of RAG maintenance (Brainfish): https://www.brainfishai.com/blog/the-hidden-cost-of-rag-maintenance-when-knowledge-pipeline-work-consumes-your-sprint</a></p><p><a href="https://blog.pebblous.ai/report/karpathy-llm-wiki/en/">Microsoft GraphRAG cost to build a 1M-token graph (Pebblous report on Karpathy’s LLM wiki): https://blog.pebblous.ai/report/karpathy-llm-wiki/en/</a></p><p><a href="https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f">Andrej Karpathy, the original LLM wiki pattern: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f</a></p><p><a href="https://andrewpaulsimmons.com/posts/ai-knowledge-base">One engineer’s markdown-only AI knowledge base, with the three-minutes-to-thirty-seconds numbers: https://andrewpaulsimmons.com/posts/ai-knowledge-base</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4aa027df8d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Fine-Tune Your Own Open Source Jev Alternative for Free in a Few Hours]]></title>
            <link>https://medium.com/@timbiondollo/how-to-fine-tune-your-own-open-source-jev-alternative-for-free-in-a-few-hours-cce74200670c?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/cce74200670c</guid>
            <category><![CDATA[jevs]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[system-one-model]]></category>
            <category><![CDATA[open-source-model]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 23:09:16 GMT</pubDate>
            <atom:updated>2026-11-06T03:49:47.709Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J0L78OLIe_JZVL9lXiwDzA.jpeg" /><figcaption>An image of an AI vault opening</figcaption></figure><p><em>Everyone’s arguing about whether Jev is the real deal or just a good marketing demo. I turned Claude loose on an open weight model called Laya that competes with Jev, and is totally free to run and modify. If you are hype about Jev you are going to love Laya. Stick around till the end of this article for the prompt to get it set up in your claude code and crushing some tasks.</em></p><p>You’ve seen the name Jev in your feed by now. It’s the model sitting inside a lot of AI agents, making the small decisions nobody thinks about. Route this ticket. Flag this comment. Is this customer about to walk. Fast. Cheap per call. Closed. You can’t download it. You can’t look inside it. You just get billed forever to give your data away to a black box. Jev is cheap and fast for sure, but if you work at a decent sized org chances are it will be hard to get procurement to agree to let you send customer data to a black box AI. With Laya thats not a concern since it’s always free, always private, always fast, and solid enough to stand toe to toe with Jev.</p><p>Half the comments under every Jev post say it’s the real deal. The other half say it’s a good demo wearing a research paper. Nobody in either camp has actually run it. So I skipped the argument. I pointed Claude at the open alternative and told it to train one for real. On my own laptop. For an afternoon.</p><p>Well, have I got something for you.</p><p>This piece covers four things. What this kind of model is good at with zero setup. Why it’s absurdly fast. One bug that will make you laugh. And how a few hundred examples and five minutes of training fix the rest.</p><h3>What you are setting up</h3><p>Two pieces.</p><p><strong>Claude Code, running in your terminal.</strong> Not the cloud sandbox version. It can actually touch your machine.</p><p><strong>Laya.</strong> A free, open source stand-in for models like Jev. It does one narrow job. You hand it a sentence and a short list of allowed answers, and it picks one, fast. Which department handles this. Is this spam. How urgent, on a scale of one to three. That’s the whole category of these types of models. Most of what an AI agent does all day isn’t deep thinking. It’s routing and gating. Paying full chatbot prices to answer “billing or technical” is like calling a surgeon to check whether a light switch works.</p><h3>Why is Jev so much faster than a normal AI model?</h3><p>This is the part everyone skips past to argue about benchmarks, and it’s the most useful thing here.</p><p>A chatbot is enormous. Hundreds of billions of parameters, sometimes. It answers you one word at a time, checking in with itself after every single word. That’s why a long answer takes a few seconds to type out. It’s also why it lives in a data center instead of your laptop.</p><p>A model like Jev or Laya doesn’t write anything. It reads your question once and picks an answer off a short list. One pass. Done. No typing, no thinking out loud.</p><p>Laya is 421 million parameters. Small enough to run on a laptop with room to spare. Here’s the number that made it real for me: on my own Mac, the Apple-silicon build answered a question in 6.4 milliseconds. Not seconds. Milliseconds. The regular version took about 20. Even plain CPU, no GPU at all, still beat 112 milliseconds. That’s still faster than most chatbots manage before they’ve typed a single word back. Thats roughly 300–400 times faster than an LLM doing the same task.</p><p>That speed isn’t a nice bonus. It’s the whole business case of using a model like this because its near real time on huge data sets. Nobody calls a giant chatbot to decide whether one email is spam. Do that a million times a day with a chatbot and you need a data center and a very upsetting invoice. Do it with a model this size and you need a laptop and a coffee break. That’s why every AI agent quietly making decisions behind the scenes wants one of these instead of a chatbot doing the same job slower and worse.</p><h3>What is Jev actually good at with zero setup?</h3><p>I didn’t train it for anything first. I wanted to see what a brand new copy of this model does the moment it wakes up.</p><p>Some of it was better than I expected. Spam email, caught 99% of the time. Toxic comments, 94%. The emotional tone of a social post, angry, happy, sad, hopeful, read correctly about 79% of the time, beating a comparison model that had actually been shown a thousand labeled examples first by a long shot. Zero training. One forward pass. If your use case is “is this bad,” you can point this thing at your data today and get something usable before lunch.</p><h3>Where does a model like this fall apart before training?</h3><p>Then I asked it to guess a star rating, one through five. It got it right about once in four tries. That’s less better than a coin flip, so might as well flip a coin instead.</p><p>Ask it a plain yes-or-no question about a review that says, and I’m quoting exactly, “absolutely love this, best purchase this year.” It will tell you there’s a zero percent chance the answer is yes that this is a good review. Not low confidence. Zero percent. On an obviously glowing review.</p><p>That’s not a rounding error. That’s the model hitting a question shaped slightly differently than anything it’s seen, and getting it backwards with total confidence. Here’s the thing nobody selling you one of these will say out loud: the exact wording of your question moves the answer by several points, before you’ve trained anything at all. Ask “is this spam” one way and a checkpoint calls a quarter of your inbox spam. Ask it a slightly more dramatic way and the same checkpoint calls three quarters of your inbox spam. Same model. Different question. Wildly different Tuesday.</p><h3>Can you fine-tune an open source Jev alternative like Laya yourself?</h3><p>“Fine-tuning” sounds like a complex ritual you need a PhD for. It’s not. You show it a few hundred examples of the decision you want, correct answer attached. It stops guessing at general categories and starts learning yours.</p><p>Here’s what that bought me. On a laptop. No cloud bill, no rented GPU. In a couple of hours</p><p>The star-rating guess went from one-in-four correct to better than one-in-two after a thousand labeled reviews. Training time: under five minutes. The spam filter was already decent at 87%. It went to 98%. And the expensive part turned out not to be the training. Two hundred examples got most of the way to where a thousand landed. The training itself finishes before your coffee gets cold. Finding two hundred good, correctly labeled examples is the actual job.</p><p>One more thing worth knowing if you’ve got more than one decision to automate: a single model trained on twelve different tasks at once performed almost identically to training twelve separate specialist models. You don’t need a model per task. You need one model and a pile of examples per decision.</p><h3>How does AI model calibration actually work?</h3><p>This matters more than any accuracy number above, and almost nobody explains it simply. I spent hours scouring the internet scratching my head.</p><p>A model can be right a lot and still lie to you about how sure it is. Picture a weather forecaster who says “ninety percent chance of rain,” and it only rains six times out of ten. Not wrong exactly, just miscalibrated. That’s exactly what happened here. On the star-rating task, the model handed back confident answers that were often wrong, which is the last thing you want if your whole plan is “let the model handle the easy calls and send me the hard ones.”</p><p>The fix has a name. Calibration. It’s smaller than it sounds. Five hundred examples, a few seconds of math, done separately from training. You’re not teaching the model anything new. You’re teaching its confidence number to mean what it says.</p><p>Do that and something useful happens. Spam and toxicity are already strong, so now you can trust the number and auto-handle almost all of it, sending only the rare weird one to a human. On star ratings and sentiment, that same honest number tells you the shortcut doesn’t exist yet. You find that out from a calibration check instead of from an angry customer.</p><p>Skip this step and you’re flying on a fuel gauge nobody’s ever checked against reality. It might be close. You won’t know until you’re on the shoulder of the highway.</p><h3>The Jev marketing claim did not survive contact</h3><p>Both Jev and this open alternative get marketed with a fancier training story than “we showed it examples.” Something involving reinforcement learning and calibrated rewards. Worth testing rather than taking on faith. So it got tested. Turn the fancy mechanism off, train the plain way instead, and the result comes back identical. What you’re actually buying is a well-trained model with a clean way of asking it typed questions. Just not the story on the marketing page but man was it some good marketing. But thats another story altogether.</p><h3>The prompt you’ve been waiting for</h3><p>The move that actually worked wasn’t handing Claude a rigid checklist. It was giving it a mission and getting out of the way.</p><pre>Your job is to become the expert on Laya (github.com/NandhaKishorM/laya).<br>Clone the repo, pull the weights, and get hands-on with it before you touch<br>a training run. Read how fine-tuning works, read how calibration works, and<br>figure out what it&#39;s actually good and bad at, with real tests, not by<br>restating the README.</pre><pre>Then ask me what I actually want to use it for. Don&#39;t guess at it. Once I<br>tell you the real decision I need it to make, fine-tune it on real<br>examples, calibrate its confidence numbers so they mean what they say, and<br>don&#39;t stop until it&#39;s actually reliable at that decision, not just<br>technically running.</pre><pre>Write up what you find in a results file as you go: accuracy before and<br>after, what the training took, and whether the confidence numbers can be<br>trusted. If a claim in the docs doesn&#39;t survive contact with an actual test,<br>say so instead of quietly working around it.</pre><pre>Then run with it. I don&#39;t need a check-in after every step, I need the<br>working thing at the end.</pre><p>Just paste it in Claude code and talk about your use case.</p><h4>What does it cost to run your own Jev-like model?</h4><p>The model is free. Training it costs electricity and an afternoon, on hardware you already own. No meter running per decision, forever. There are countless creative use cases but these types of models are mostly for decisions, and they don’t generate text.</p><p>The real cost is what it’s always been with anything trained on examples: a few hundred correctly labeled decisions, made by someone who actually checked them. Bad labels in, bad decisions out. No training run fixes that part.</p><p>Compare that to the closed version. Every decision costs a fraction of a cent, forever, and you’re never allowed to look inside and see why it decided anything. Never allowed to fine tune it on what good looks like either. One of these you own outright. It runs on hardware you already have, in single-digit milliseconds. The other you rent, forever, from someone who won’t show you the receipt nd can’t modify.</p><h3>Try it this week</h3><p>Pick one small decision your team makes over and over. Is this lead worth a reply. Is this comment something a human needs to see. Is this ticket actually urgent. Pull together a couple hundred real examples where you already know the right answer. Paste the prompt above into Claude with real hardware behind it, and see what comes back.</p><p>You’ll probably find it’s already decent at the obvious stuff, bad at anything with shades of gray, and a few hundred examples away from fixing both. In an afternoon. For free. Which, be honest, wasn’t happening if you waited for someone else to build it.</p><p><em>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent Claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece.</em></p><p>*<em>Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><h3>Sources</h3><ul><li>Laya repository: <a href="https://github.com/NandhaKishorM/laya">https://github.com/NandhaKishorM/laya</a></li><li>Laya model card: <a href="https://huggingface.co/convaiinnovations/laya">https://huggingface.co/convaiinnovations/laya</a></li><li>Laya MLX port for Apple Silicon: <a href="https://huggingface.co/aac6fef/laya-mlx">https://huggingface.co/aac6fef/laya-mlx</a></li><li>Independent field guide to TypeSafe’s Jev, including third-party audits: <a href="https://github.com/AbdelStark/awesome-typesafe-jev">https://github.com/AbdelStark/awesome-typesafe-jev</a></li><li>“Is Jev open source? No, but 35 open alternatives are”: <a href="https://madewithjev.com/open-source-jev">https://madewithjev.com/open-source-jev</a></li><li>Every accuracy, calibration, and speed number above: hands-on testing on an Apple M5 Max, September 26, 2026, full methodology and raw results available on request</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cce74200670c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LLM Wiki vs RAG: How an AI Actually Reads Your Documents, and When Each One Wins]]></title>
            <link>https://medium.com/@timbiondollo/llm-wiki-vs-rag-how-an-ai-actually-reads-your-documents-and-when-each-one-wins-c05cc332ee25?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c05cc332ee25</guid>
            <category><![CDATA[ai-retrieval]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[llm-wiki]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Sat, 12 Sep 2026 19:51:59 GMT</pubDate>
            <atom:updated>2026-11-06T03:50:31.222Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jRNHSm5wpnOsSJvSWHj35w.jpeg" /><figcaption>AI Visualization of a LLM wiki interconnected nodes with edges and links</figcaption></figure><p><em>Three ways to connect an AI to your files, the one kind of question only one of them can answer, and what breaks a month in.</em></p><p>You have two hundred documents. Contracts, research, client notes, whatever your pile is. You want to ask an AI questions about them and get real answers back.</p><p>Someone tells you that you need a vector database. Someone else says you need a knowledge graph. A third person sends you a link about “LLM wikis” and says it’s the future. In the meeting, somebody says the graph “lets the agent traverse the sources,” and everyone nods.</p><p>None of that helps you decide anything. So here is what each of those things is, what each one is good at, and what goes wrong with each after a month.</p><h3>The three ways to do it</h3><p>Every setup you will hear about is one of these three, or a mix.</p><p><strong>Option one: search.</strong> You give the AI a search engine over your files. Not a search engine that matches exact words, but one that matches meaning. Ask about “late payment penalties” and it will find the paragraph about “fees for overdue invoices” even though none of the words match. When you ask a question, it finds the ten most relevant paragraphs and hands them to the AI, which writes an answer from them.</p><p>This is what people mean by “RAG” and by “vector database.” The vector database is the search engine. RAG is the practice of searching first, then answering.</p><p><strong>Option two: an assistant who goes and reads.</strong> No search engine. Instead, the AI gets to open your folders itself. It lists what’s there, opens a file, reads it, decides what to open next. It works the way a smart intern would if you pointed them at a filing cabinet.</p><p><strong>Option three: a briefing book, written in advance.</strong> Before anyone asks anything, the AI reads your whole pile and writes it up. One page per topic. One page per person or company. One page per source document. Every page links to the related pages, the way Wikipedia articles link to each other. When you ask a question later, the AI answers from the briefing book, not from the raw pile.</p><p>This is the “LLM wiki.” It is the newest of the three, and it is the one worth understanding, because it is the one that gets described with the most hand-waving.</p><h3>The links are the whole point</h3><p>Notice what separates option three from the other two. It’s not that the AI wrote things up. It’s that the pages link to each other.</p><p>That is what people are pointing at when they say the AI can “traverse” your documents. The word sounds technical. It isn’t. It means following links.</p><p>Here is why that matters. The search engine in option one answers exactly one question: which paragraphs look like the thing you asked? That is all it can do. It has no idea that two documents are related unless they happen to use similar words.</p><p>The briefing book has links between pages. So the AI can do something the search engine can’t. It finds a few good starting pages, follows the links out from those pages to the related ones, and then follows those pages’ links too. Then it stops.</p><p>That’s traversing. Following links outward from a starting point. When someone says it in a meeting, that is all they mean, whether they know it or not.</p><p>The details matter less than the idea, but here they are. Following links two steps out is called “two hops.” A page two steps away counts for less than a page one step away. And the system has a rule for what counts as related. In the LLM Wiki app, two pages that link to each other count for a lot. Two pages that were written from the same original document count for even more. Two pages that share a lot of the same neighbors count for a bit. Two pages of the same type count for a little.</p><p>That rule is written down in the software. You can read it. You can disagree with it. The search engine in option one gives you a similarity score and nothing more. Nobody can explain why one paragraph scored 0.83 and another scored 0.79.</p><h3>The question only the briefing book can answer</h3><p>So what does following links actually get you? One specific kind of question that search cannot answer. Once you know the shape of it, you will spot it everywhere.</p><p>Ask: “Which of our clients were affected by the same vendor problem?”</p><p>No paragraph in any document says that. The answer lives in the connection between three separate documents, none of which mentions the others. A search engine finds those three documents only if your question resembles their words. It doesn’t. Your question is about a pattern across documents, not about what any one of them says.</p><p>The briefing book has a page on that vendor. That page links to three client pages. Follow the links, and you have your answer.</p><p>Researchers call these “multi-hop” questions, because answering one takes several steps across sources. On multi-hop questions, the linked approach wins clearly. On simple questions where the answer sits in one place, like “what does this contract say about termination,” search does just as well.</p><p>That second half is the useful part. If most of your questions are simple lookups, search is fine and cheaper. The briefing book earns its cost on questions where the answer is a relationship.</p><h3>What each one costs</h3><p>If the briefing book answers questions search can’t, the next thing you’ll want to know is what it costs. The answer is surprising, because the running cost has almost nothing to do with the clever part.</p><p>A vector database is a service. You pay for it monthly whether anyone asks a question or not. The managed ones charge a minimum before you’ve run a single search. Every time a document changes, it has to be re-indexed. And the index is locked to the specific AI model that built it. When a better model comes out, you rebuild everything from scratch, because the old index and the new model do not speak the same language. Many of these services cannot even export your data.</p><p>A briefing book is a folder of text files. Each file has a few labels at the top: what it’s about, where it came from, when it was written. There is nothing to host and nothing to pay for monthly. You can put the folder under version control and see exactly what changed and when. A colleague needs it? Zip it and send it. Want to know what the AI believes about a topic? Open the file. It’s in English. If it’s wrong, edit it.</p><p>That last point is the underrated one. A page in the briefing book can be reviewed by a human before it goes live. An entry in a vector index is a list of 1,536 numbers. Nobody reviews that.</p><p>The honest trade is up front. Writing the briefing book costs real money, because the AI has to read everything and write it all up. One documented case: about 2,200 documents, written up for roughly $45. Indexing the same pile for search costs almost nothing. So the briefing book costs more to build and less to run. If you were going to pay a monthly minimum for search, the briefing book pays for itself in the first month.</p><p>There is one more saving that is easy to miss. A well-written page is dense. Ten raw paragraphs pulled by a search engine are not. And AI models get worse as you hand them more text. One study tested eighteen models, holding the task fixed while adding more and more text around the answer. Every single model got worse as the text grew. Adding one irrelevant paragraph measurably hurt. On one test, handing the AI a tight 300-word brief beat handing it the full 113,000-word file, on the same questions. The shorter input got better answers.</p><p>One thing to know about that study: the company that ran it sells vector databases, and newer models have gotten better at handling long text since. The size of the effect will shrink. The direction won’t. Less irrelevant text, better answers.</p><h3>What breaks after a month</h3><p>So far this has been the case for the briefing book. Now the other side, because there are three things that go wrong with it, and nobody mentions them in the pitch.</p><p>The first one comes from the fact that the briefing book has two layers, and they behave completely differently.</p><p>The first layer is your original documents. You didn’t write them. You don’t control them. They change. A contract gets amended. A study gets corrected. A web page gets rewritten.</p><p>The second layer is the briefing book. Every page in it was written by reading across several original documents. That’s where the value is. It’s also entirely dependent on the first layer.</p><p>So when an original document changes, every page written from it is now wrong. Nothing tells you. The page still reads beautifully. And any page that cites that page is now wrong too.</p><p>This turns out to be a famous problem. Databases have dealt with the same thing for decades: a summary table that has to stay correct when the underlying data changes. Database engineers solved it. When one row of the original data changes, the system recalculates exactly the part of the summary that depends on that row, and nothing else.</p><p>That works because a database summary is arithmetic. Add these up, count those. You can work out precisely which output depends on which input.</p><p>There is no arithmetic for “read these five papers and write a summary.” Nobody can say which sentence of the summary came from which sentence of the sources, because the AI didn’t work that way.</p><p>So today, the honest answer is: when a source changes, throw away the pages built from it and write them again. The team behind Microsoft’s version of this said publicly that they can detect when new material arrives, but they cannot tell when a summary has drifted far enough to be worth rewriting. That is still unsolved.</p><p>How much this matters, in one number: when a scientific paper turns out to be wrong and gets retracted, the average gap between publication and retraction is about 550 days. For a year and a half, that paper is in your pile, and everything written from it is wrong.</p><p><strong>What to do about it.</strong> Steal the trick that software build tools have used since the 1970s. Give every original document a fingerprint, a short code that changes if even one character of the file changes. On every briefing-book page, record the fingerprints of the documents it was written from. When a fingerprint changes, you know exactly which pages to rewrite. Rewrite only those. Run this check on a schedule, not when you happen to remember.</p><h3>The AI won’t write the same book twice</h3><p>The second problem. You might reasonably assume that if you handed the same pile to the AI twice, you’d get roughly the same briefing book. You wouldn’t, and the gap is bigger than you’d guess.</p><p>Researchers gave four different AI models the same 9,978 medical abstracts. Same instructions. Same categories to sort things into. Same text.</p><p>One model found about 20,000 relationships between things in the text. Another found about 46,000. And when the researchers compared any two models’ results, they agreed on roughly one relationship in ten.</p><p>Four capable models, same text, same rules, one in ten.</p><p>Two things people assume will fix this don’t. Setting the model to its most predictable mode doesn’t fix it, because at the level of the arithmetic, results can still vary with how work gets batched. And having several models vote doesn’t fix it either. In the same study, going with the majority did no better than picking the single best model. Only unanimous agreement across all four was more reliable, and it covered about 4% of what was found.</p><p><strong>What to do about it.</strong> Three things.</p><p>First, wherever a piece of information can be pulled out by a simple rule, use the rule and not the AI. Dates, author names, section headings, which file links to which. All of that is mechanical. Don’t spend an AI call on it. A study of code documentation found that structure extracted mechanically beat structure extracted by AI.</p><p>Second, decide your categories in advance and make the AI fill them in. Don’t let it invent the categories. “Here are the eight kinds of things I care about, sort what you find into them” gives far more consistent results than “organize this.”</p><p>Third, accept that the briefing book is not a fact about your documents. It’s a fact about your documents plus the specific model that read them on the specific day it ran. Keep the version. When you rebuild, treat it as a new edition, not a refresh.</p><h3>Where did this come from</h3><p>The third problem shows up the moment a second person relies on the briefing book. They read a claim on a page and ask where it came from. That question stops being a nice-to-have and becomes the thing that decides whether anyone trusts the book at all.</p><p>Most systems answer it by recording which document a page was written from. That’s not enough, and here’s why.</p><p>A single paragraph in the briefing book might contain three claims. One is stated directly in a source. One is a reasonable inference the AI made that goes a bit beyond what the source says. One might contradict something in a different source you also have. A citation at the end of the paragraph flattens all three into “cited.”</p><p>Across systems that do this today, when researchers checked whether the cited source actually supports the claim, it failed between 11% and 57% of the time depending on the system.</p><p>A careful setup records two things for each claim. Which document, and the exact quoted passage it rests on. And the document reference points to a specific version of that document, using the fingerprint from the previous section.</p><p>That second part is where nearly everyone falls down. Systems record which document. They almost never record which version. So when the document changes, they cannot tell you whether the passage they quoted still exists.</p><h3>One filing system is never enough</h3><p>Those are the three things that break. One more topic before the end, because it’s the first practical decision you’ll face when you set this up, and most people get it wrong.</p><p>You want your pile organized by topic. Also by which method the research used. Also by author. Also by which client project it belongs to. Also by how much you trust it.</p><p>The instinct is to build a better folder structure. The instinct is wrong, and librarians worked out why in 1933.</p><p>A folder structure forces one order. A document goes under its topic or under its method, but not both. Whichever you pick, half your future questions get harder.</p><p>The answer is the thing every shopping site does. You don’t browse a store by one tree. You filter by size, and color, and price, all at once, in whatever order you like. Each filter is independent. The technical name is faceted classification, and it predates computers.</p><p>The rule to remember, from taxonomy specialist Heather Hedden: when you find yourself needing a document to live in several folders because you’re sorting by several different things, you don’t have a folder problem. You have a filter problem. Stop patching the tree. Define the filters.</p><p>In a briefing book, the labels at the top of each file are the filters. Topic, method, author, project, confidence. Each label is one filter. Use folders for the one structure you’ll never regret, usually project or source type. Use the links between pages for everything else.</p><p>Three things will still bite you. Nothing forces consistent spelling, so “RCT,” “rct,” and “randomized trial” become three different labels and your filter misses two of them. Labels are flat, so tagging something “transformer” doesn’t make it show up under “neural networks.” And renaming a project leaves every old label pointing at the old name. If you outgrow these, there’s a standard called SKOS built for exactly this, and it exists because the heavier alternatives are too expensive for most teams.</p><h3>When not to do any of this</h3><p>Everything above makes the case for the briefing book. It’s fair to ask whether it’s always the right call. It isn’t, and the clearest evidence comes from the people who built one and tested it hardest.</p><p>This year, a research team built exactly the system described here. They had an AI write a briefing book over a company’s support documents and then let another AI find answers by browsing the book. It beat plain search, and it beat every fancier search setup they tried, on both answer quality and on whether the answers were actually backed by the documents.</p><p>Then they tested it on eleven different document collections. It won on five. It tied on three. It lost on three.</p><p>The losses tell you when to skip this. The briefing book helps when your pile is about one subject area and has a natural structure to it. Plain search stays better when the pile is a grab bag of unrelated facts, or when it’s mostly spreadsheets and tables, because there’s no structure for the briefing book to capture.</p><p>Two more findings from the same team. Browsing the briefing book costs several times more per question than a single search. Use it for the questions that matter, not the ones you ask fifty times a day. And when they swapped in a cheaper AI to do the browsing, cost dropped by half and answer quality barely moved. The quality of the book matters more than the intelligence of the reader.</p><p>And their main limitation, in their own words: every document sits in exactly one place in the book. Documents that span several topics get filed under one, and most of the wrong answers came from that. The fix they propose for next time is letting a document live under more than one heading.</p><p>Which is the filter problem from the previous section. A 2026 research team arrived at the problem a librarian solved in 1933.</p><h3>Try it this week</h3><p>Pick one pile you keep going back to. Not everything. The one you actually re-read.</p><p>Put the original documents in one folder and leave them alone. Have an AI write the briefing book into a second folder, with links between pages and a few labels at the top of each file saying which documents it came from. Add your filters as labels.</p><p>Then ask it a question whose answer lives across three documents. See if it finds the connection.</p><p>If it does, you have your answer. If it doesn’t, you found out for less than one month of a subscription.</p><p><em>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent Claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece.</em></p><p>*<em>Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><h3>Sources</h3><ul><li>LLM Wiki desktop app (nashsu), including the four-signal relatedness rule: <a href="https://github.com/nashsu/llm_wiki">https://github.com/nashsu/llm_wiki</a></li><li>Andrej Karpathy, original LLM Wiki pattern: <a href="https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f">https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f</a></li><li>The briefing-book study tested on eleven collections (Corpus2Skill, EMNLP 2026 Findings): <a href="https://arxiv.org/abs/2604.14572">https://arxiv.org/abs/2604.14572</a></li><li>Four models, same text, one relationship in ten (knowledge graph consistency study): <a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC13529944/">https://pmc.ncbi.nlm.nih.gov/articles/PMC13529944/</a></li><li>Eighteen models get worse as input grows (Chroma, Context Rot): <a href="https://www.trychroma.com/research/context-rot">https://www.trychroma.com/research/context-rot</a></li><li>Anthropic, Effective context engineering for AI agents: <a href="https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents">https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents</a></li><li>Search vs. browse inside AI agents (Is Grep All You Need?): <a href="https://arxiv.org/abs/2605.15184">https://arxiv.org/abs/2605.15184</a></li><li>How databases keep summaries current (DBSP, incremental view maintenance): <a href="https://docs.feldera.com/vldb23.pdf">https://docs.feldera.com/vldb23.pdf</a></li><li>Microsoft GraphRAG on why incremental updates are hard: <a href="https://github.com/microsoft/graphrag/issues/741">https://github.com/microsoft/graphrag/issues/741</a></li><li>The 1979 answer to “a source changed, what do I now disbelieve” (Doyle, Truth Maintenance): <a href="https://www.sciencedirect.com/science/article/abs/pii/0004370279900080">https://www.sciencedirect.com/science/article/abs/pii/0004370279900080</a></li><li>The fingerprint-and-rebuild trick from software build tools (Build Systems à la Carte): <a href="https://www.microsoft.com/en-us/research/wp-content/uploads/2018/03/build-systems-final.pdf">https://www.microsoft.com/en-us/research/wp-content/uploads/2018/03/build-systems-final.pdf</a></li><li>Standard vocabulary for “where did this come from” (W3C PROV-O): <a href="https://www.w3.org/TR/prov-o/">https://www.w3.org/TR/prov-o/</a></li><li>The standard for labels with synonyms and hierarchy (W3C SKOS Primer): <a href="https://www.w3.org/TR/skos-primer/">https://www.w3.org/TR/skos-primer/</a></li><li>Heather Hedden on the filter problem (Polyhierarchy in Taxonomies): <a href="https://www.hedden-information.com/polyhierarchy-in-taxonomies/">https://www.hedden-information.com/polyhierarchy-in-taxonomies/</a></li><li>Mechanical extraction beats AI extraction for code (AST-Derived vs LLM-Extracted graphs): <a href="https://arxiv.org/pdf/2601.08773">https://arxiv.org/pdf/2601.08773</a></li><li>AI tools and retracted research (JMIR 2026): <a href="https://doi.org/10.2196/88766">https://doi.org/10.2196/88766</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c05cc332ee25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let Claude Install Your Next GitHub Find in Twenty Minutes]]></title>
            <link>https://medium.com/@timbiondollo/let-claude-install-your-next-github-find-in-twenty-minutes-ea5ede438d92?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea5ede438d92</guid>
            <category><![CDATA[ai-voice-agent]]></category>
            <category><![CDATA[anthropic-claude]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[claude-cowork]]></category>
            <category><![CDATA[gen-ai-use-cases]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 14:30:15 GMT</pubDate>
            <atom:updated>2026-11-06T03:51:06.319Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oKYpH1UToSGzlzQjGd0mAw.jpeg" /></figure><p><em>Hand the setup to Claude Cowork, end up with a fully local voice studio, and fix an MCP that was never meant to work in Claude Co-work.</em></p><p>Ever run across a cool open source app on GitHub and not have the time or bandwidth to set it up and mess around with it?</p><p>You star the repo. You tell yourself you will get to it. You never do. Not because it is hard, but because between you and the app there is a download page, a wall of system requirements, a terminal command, and three permission prompts you would have to read.</p><p>Well, have I got something for you.</p><p>This walkthrough covers three things. How to let Claude do the setup for you while you watch. How to get VoiceStudio running, a viral open source app that does voice cloning and dubbing entirely on your own machine. And an accidental third thing I ran into along the way: how to make an MCP that was built for Claude Code work in Cowork instead.</p><p>The whole thing takes about twenty minutes, and most of that is a download bar.</p><h3>What you are setting up</h3><p>Two pieces.</p><p><strong>Cowork with computer access.</strong> Claude can see your screen and use your mouse and keyboard. You approve specific apps, one dialog, and it can only touch the ones you named. You can revoke it whenever.</p><p><strong>VoiceStudio.</strong> An open source desktop app that clones voices, designs new ones, dubs video into other languages, transcribes, and builds audiobooks. It runs entirely on your hardware. No account, no API key, no per-character billing, and your audio never leaves the machine. It went from a few thousand GitHub stars to twenty one thousand in about two weeks, which is why it is in your feed right now.</p><p>You need an Apple Silicon Mac, Windows 10 or 11, or Linux. If you are on an Intel Mac, stop here. The app will install and open and then never work, because the engine underneath it stopped shipping Intel builds.</p><h3>Part one: let Claude do the install</h3><h3>Step one: turn on computer access</h3><p>In Cowork, ask Claude to install something and it will request access to the apps it needs. You will get one dialog listing them. Approve it.</p><p>You will be granting Finder, and later the app itself. That is it. Claude cannot see anything you did not list.</p><h3>Step two: paste the prompt</h3><p>Start a new chat and paste this, with the app name filled in:</p><blockquote><em>Install VoiceStudio on my Mac and connect it to Cowork. Show me the file name, size, and publisher checksum before you download anything, and wait for my okay. Stop and hand me the decision at any security warning or system permission. Prove it works at the end with a real test, not just “installed.</em></blockquote><p>That is the short version. There is a fuller one at the bottom of this piece worth using for anything more involved.</p><h3>Step three: approve the download</h3><p>Claude will find the release page, work out which of the nineteen files matches your machine, and come back with the details before pulling anything down. For an Apple Silicon Mac that is VoiceStudio_0.5.1_aarch64.dmg, about 105 MB.</p><p>Say yes. It downloads, mounts the disk image, and drags the app into Applications.</p><h3>Step four: get past the security warning</h3><p>This is the step everyone hits, and the official instructions for it are wrong.</p><p>macOS will refuse to open the app and tell you it cannot verify the software is free of malware. That is not a red flag about the code. The developer has not paid for Apple’s notarization, which costs $99 a year, so macOS quarantines the download.</p><p>The repo tells you to right-click the app and choose Open. <strong>That stopped working two macOS versions ago.</strong> On current macOS you do this instead:</p><ol><li>Double-click VoiceStudio in Applications. Dismiss the warning.</li><li>Open <strong>System Settings → Privacy &amp; Security</strong> and scroll to the Security section.</li><li>Find the line about VoiceStudio being blocked and click <strong>Open Anyway</strong>.</li></ol><p>One time per install. After that it opens on a double-click.</p><p>Claude will not click through this one for you, and that is correct. Overriding a malware warning is your call, not the agent’s. What it will do is tell you why the warning is there and confirm the file you downloaded matches the checksum the publisher posted, so you are deciding with actual information.</p><h3>Step five: grant Accessibility</h3><p>The setup wizard will not move past its system check until you grant Accessibility. It uses it for dictation, so it can type transcripts into whatever app you are in.</p><p><strong>System Settings → Privacy &amp; Security → Accessibility → toggle VoiceStudio on.</strong> Then click Re-check in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*cYDWA2LyLInRAH3xToFzmw.jpeg" /></figure><p>Worth knowing what you are agreeing to: Accessibility lets an app read and control other apps. It is one of the strongest permissions on a Mac. This app has a real reason to want it, but it asks before doing anything at all, even things that never touch dictation. Grant it or do not, but grant it knowingly.</p><p>Microphone will say “not asked yet” and stay that way. It is not a blocker, so ignore it.</p><h3>Step six: let the wizard run</h3><p>From here it is mostly waiting, and Claude handles it.</p><p>Dependencies take about eight minutes. The app narrates each step, so when it says “step 4 of 9” it is working, not frozen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*4IMXh2cwXWhqZ0q94SzwGA.jpeg" /></figure><p>At the model screen, read carefully. <strong>The setup screen says you need about 17 GB. You do not.</strong> Only the top item is required, the 2.4 GB TTS model. Everything below it is optional transcription models you can add later from Settings. Download the required one, skip the rest, and you are through in two minutes instead of twenty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*hEDZLVvOkYAfIew1WxG0Eg.jpeg" /></figure><p>Then say no thanks to the analytics prompt, and you land in the studio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*_G32DzPJMwqSC6TFB3qUYw.jpeg" /></figure><h3>Part two: use it</h3><h3>Make your first voice</h3><p>Open <strong>Voice Clone</strong>. Drop in a clean recording. Type what you want it to say, pick a language, hit Generate.</p><p>Clean beats long. Ten to fifteen seconds of quiet audio beats two minutes of noisy audio every time, because whatever is in the background of your reference shows up in the output. Anything over 75 seconds gets rejected and asked to be trimmed.</p><p>Clone your own voice or one you have written permission to use. This will clone anybody from a three second clip, which is exactly as much of a problem as it sounds. The app watermarks its output by default so generated audio can be identified later. Leave that on.</p><p>If you would rather not clone anyone, use <strong>Voice Design</strong> and describe a voice that does not exist. “Warm British storytelling voice, mid forties, unhurried” gets you a narrator with nobody’s face attached. For most work purposes this is the better door.</p><h3>Dub a video</h3><p>Drop a video in, pick the output language. It transcribes, translates, works out who is speaking, and re-synthesizes the whole thing in the original speaker’s voice.</p><p>You get a transcript editor with per-line timing, so a bad translation is a one-line fix rather than a re-run. Put your product names in the glossary before they become poetry in Japanese. Multi-speaker footage gets a casting board where you drag a voice onto each person.</p><p>This is the highest-value thing in the app and the one I would try first.</p><h3>Part three: make any local MCP work in Cowork</h3><p>Here is the accidental third thing, and it is the most reusable part of this piece.</p><p>VoiceStudio ships an MCP server. That is the bit that lets Claude use the app directly: generate speech, clone a voice, transcribe audio, without you opening a window. The README says to add it as a connector.</p><p><strong>That does not work, and it cannot.</strong> Connectors are reached from Anthropic’s servers, not from your laptop. So an address pointing at localhost sends them looking on their own machine. The URL field rejects it before you even get that far.</p><p>Claude Code does not have this problem, because Claude Code runs on your machine. That is what the developers built for, and it is why you will hit this again. Plenty of local-first tools ship an MCP server aimed at Claude Code, and none of them connect to Cowork.</p><p>Cowork’s mechanism for local servers is a Desktop Extension, a small file that runs on your machine and relays messages. Most projects have not shipped one.</p><p>So have Claude build you one. Paste this:</p><pre>VoiceStudio is running on my machine and serves an MCP server at</pre><pre>http://localhost:3900/mcp/ that I cannot add to Cowork as a connector,</pre><pre>because connectors resolve from Anthropic&#39;s servers and cannot see my</pre><pre>localhost. <br>Build me a Desktop Extension (.mcpb) that bridges it.<br>WHAT IT DOES: runs locally, speaks MCP over stdio to Cowork, forwards every<br>message to that HTTP endpoint. Nothing else. No outbound calls anywhere<br>except the address I gave you.</pre><pre>PROBE THE SERVER FIRST. Do not write code against assumptions. Hit the<br>endpoint, do the MCP handshake, list the tools, and show me what actually<br>came back. If the documented URL fails, find the one that works and tell me<br>what was wrong with the documented one.</pre><pre>BUILD IT: a manifest.json at the root plus a small Node script. Cowork ships<br>its own Node runtime, so add no dependencies. Handle the session id the<br>server returns on initialize, and parse responses that arrive as<br>server-sent events rather than plain JSON.</pre><pre>FAIL LOUDLY, NOT SILENTLY. If the app is not running, return a plain error<br>telling me to open it. Never hang.</pre><pre>TEST IT BEFORE HANDING IT TO ME. Stand up a mock server that behaves the way<br>the real one did when you probed it, run the bridge against it, and show me<br>the output. Then package it and tell me where the file is.</pre><p>Then install what it builds:</p><ol><li><strong>Settings → Extensions → Advanced settings → Extension Developer → Install Extension. (Co-work might just have a little one click install in chat)</strong></li><li>Select the .mcpb file.</li><li>Make sure VoiceStudio is open, then start a new chat.</li></ol><p>Ask Claude to check VoiceStudio’s health. If you get back status: ok with your device listed, the bridge is live.</p><p>Now ask for audio. <em>“Say ‘it works’ in the demo voice.”</em> You get back a real WAV, generated on your machine, and it lands in VoiceStudio’s history so you can play it.</p><p>Expect the first one to be slow. Mine took 9.5 seconds to make 1.5 seconds of audio, because the first request of a session loads the model into memory. Every one after is quick. Do not judge the speed by the first take.</p><p>Two things that will trip up whatever it builds, so watch for them. The endpoint in the docs is missing a trailing slash, and without it the server returns an error rather than redirecting. And responses come back as event streams even for ordinary calls, which breaks a bridge that assumes plain JSON. If Claude probes the server first like the prompt tells it to, it finds both.</p><p>Swap the app name and the address and that prompt works for any local MCP server you run into. That is the part worth keeping.</p><h3>Four habits that save you time</h3><p><strong>Let Claude read the wizard.</strong> The 17 GB versus 2.4 GB thing is the whole argument for this approach. It read the fine print and picked the small correct option. You would have clicked the big obvious button.</p><p><strong>Say what you want it to stop at, up front.</strong> Agents are good at momentum and bad at knowing when momentum is wrong. One sentence in your prompt about security warnings and permissions is what turns “it did the whole thing” into “it did the whole thing and checked with me twice.”</p><p><strong>Do the first one on something disposable.</strong> Pick an app you would not mind uninstalling. Watch how it behaves at the permission prompts. That tells you whether to hand it the next job.</p><p><strong>Test the small thing before the big thing.</strong> Generate one sentence before you queue an hour of audio. Dub thirty seconds before you dub the webinar.</p><h3>What it costs</h3><p>The app is free. Your hardware is the cost, plus 10 to 20 GB of disk once you have a couple of engines.</p><p>One catch before you sell anything made with it: the app is open source under a license that allows commercial use, but the default voice model ships under a non-commercial license, and models keep their own terms regardless of the app’s. If money is involved, switch to one of the permissively licensed engines like CosyVoice or MOSS first. This is the thing most people will skip and then regret.</p><p>It also still calls itself a beta. Use the tagged release, not the development branch, and do not put it on the critical path of a client deliverable due Friday.</p><h3>The prompt worth keeping</h3><p>The short prompt above is fine for a simple app. This is the one to use for anything with a real installer:</p><pre>Install and set up [APP NAME] on my Mac. Work through it with me, and stop</pre><pre>whenever a decision is mine rather than yours.<br>STEP 1: CHECK BEFORE YOU DOWNLOAD. Find the official source. Confirm which<br>build matches this machine, including chip and OS version. If it cannot run<br>on my hardware, tell me now and stop. Show me the filename, size, and<br>publisher checksum, and wait for my okay.</pre><pre>STEP 2: SHOW ME THE REAL COST. Before installing, tell me total disk space,<br>how long it will take, what accounts or keys it needs, and what permissions<br>it will ask for. If the official docs and the installer disagree on any<br>number, say so and trust the installer.</pre><pre>STEP 3: DO THE TEDIOUS PART. Download, install, run the wizard. Read the<br>fine print I would skip: pick the smallest option that actually works rather<br>than everything the wizard suggests, and choose the privacy-preserving<br>answer on any tracking question. Narrate in plain language, not app jargon.</pre><pre>STEP 4: STOP AT THESE, ALWAYS. Do not click through security warnings. Do<br>not grant system permissions. Do not turn off protections. When you hit one,<br>tell me what it is, why it is appearing, whether it is expected for this<br>software, and what the actual risk is. Then let me decide. If I ask you to<br>disable a protection globally, push back and give me the narrowest version<br>that solves the problem.</pre><pre>STEP 5: PROVE IT WORKS. Do not stop at &quot;installed.&quot; Run the smallest real<br>test that shows it functions and show me the output. If the official<br>instructions fail, work out what actually works and tell me which<br>instruction was wrong.</pre><pre>STEP 6: HAND IT OFF. Tell me what got installed, where it lives, what I<br>granted it, what it costs to run, the first useful thing to try, and how to<br>uninstall it cleanly if I change my mind.</pre><p>Step 4 is the one that matters. It is not there to sound responsible. It is there because you want handing you the decision to be the default behavior rather than a lucky one.</p><h3>Try it this week</h3><p>Open the github you have not had time to test out. Paste the prompt. Watch.</p><p>You will read more than you click. You will take over two or three times. And you will end up with the thing installed, which, be honest, was not going to happen otherwise, and you might just learn something really cool like I did in the process.</p><p>Then point it at the next one.</p><p><em>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent Claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece.</em></p><p>*<em>Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><h3>Sources</h3><ul><li>VoiceStudio repository: <a href="https://github.com/debpalash/VoiceStudio">https://github.com/debpalash/VoiceStudio</a></li><li>VoiceStudio releases: <a href="https://github.com/debpalash/VoiceStudio/releases/latest">https://github.com/debpalash/VoiceStudio/releases/latest</a></li><li>VoiceStudio macOS install guide: <a href="https://github.com/debpalash/VoiceStudio/blob/main/docs/install/macos.md">https://github.com/debpalash/VoiceStudio/blob/main/docs/install/macos.md</a></li><li>VoiceStudio MCP guide: <a href="https://github.com/debpalash/VoiceStudio/blob/main/docs/mcp.md">https://github.com/debpalash/VoiceStudio/blob/main/docs/mcp.md</a></li><li>Trendshift trending stats: <a href="https://trendshift.io/repositories/28176">https://trendshift.io/repositories/28176</a></li><li>Getting started with local MCP servers on Claude Desktop: <a href="https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop">https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop</a></li><li>When to use desktop and web connectors: <a href="https://support.claude.com/en/articles/11725091-when-to-use-desktop-and-web-connectors">https://support.claude.com/en/articles/11725091-when-to-use-desktop-and-web-connectors</a></li><li>Anthropic Desktop Extensions documentation: <a href="https://github.com/anthropics/mcpb">https://github.com/anthropics/mcpb</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea5ede438d92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turn Claude Into a Pixel Art Studio in Ten Minutes]]></title>
            <link>https://medium.com/@timbiondollo/turn-claude-into-a-pixel-art-studio-in-ten-minutes-f4acdd2ef256?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4acdd2ef256</guid>
            <category><![CDATA[pixel-art]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agents-in-action]]></category>
            <category><![CDATA[claude]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 12:55:13 GMT</pubDate>
            <atom:updated>2026-09-07T12:55:13.694Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YazPUT-W8lYsCOYCJmF6GA.png" /></figure><p><em>Connect Sprite AI to Claude Desktop or Claude Code. Make a character, animate it, restyle it. Then paste one prompt and watch your AI agents work as a living pixel art village.</em></p><p>You have a pixel art game in your head that you never made. Or you have a team of AI agents running right now, and the only way to see them work is scrolling a log file.</p><p>Both have the same missing piece. Art. Specifically, art you can make on demand without knowing how to draw.</p><p>By the end of this guide, you will make a character by describing it in one sentence. You will make it walk. You will give it a new look. And you will have a prompt you can paste into Claude Code that turns your agent pipeline into a village of animated characters you can actually watch.</p><p>The setup takes about ten minutes. Making the art takes about two.</p><h3>What you are setting up</h3><p>Sprite AI is a tool that draws pixel art. You describe what you want. It draws it. That is the whole idea.</p><p>On its own, it lives on a website. But it also comes with a connector. A connector is a bridge that lets Claude use a tool on your behalf. Once the bridge is in place, you never open the Sprite AI website again. You just ask Claude for a character, and the character shows up in your chat.</p><p>Here is what that looks like when it works.</p><p><em>This character was made from one sentence typed into Claude. No editing. No second try.</em></p><p>There are two ways to connect it. One is for Claude Desktop, the app on your Mac or PC. The other is for Claude Code, the version that runs in your terminal. Pick whichever one you use. You can do both.</p><p>Either way, you start in the same place.</p><h3>Step one: get your key</h3><p>A key is like a password that tells Sprite AI which account to use. You make one on their website and paste it into Claude.</p><p>Go to <a href="https://www.sprite-ai.art/mcp">sprite-ai.art/mcp</a>. If you do not have an account yet, make one. It is free, and the free tier comes with 15 generations. No credit card.</p><p>On that page, find the button that says <strong>Generate a key</strong>. Click it. Copy the key it gives you. It starts with sai_sk_.</p><p>Keep that key somewhere safe for the next step. Treat it like a password. If it ever leaks, you can turn it off from your account and make a new one.</p><h3>Step two, option A: connect it to Claude Desktop</h3><p>Still on <a href="https://www.sprite-ai.art/mcp">sprite-ai.art/mcp</a>, click the <strong>Manual</strong> tab. You will see a web address. Copy it:</p><pre>https://www.sprite-ai.art/api/mcp</pre><p>Now open Claude Desktop.</p><ol><li>Click <strong>Customize</strong> in the sidebar.</li><li>Click <strong>Connectors</strong>.</li><li>Click <strong>Add custom connector</strong>.</li><li>Give it a name. “Sprite AI” works.</li><li>Paste the web address you just copied into the URL field.</li><li>Where it asks about sign-in, choose <strong>No OAuth</strong>. You are going to use your key instead.</li><li>Find the option to add a header. Name the header Authorization.</li><li>For the header value, type the word Bearer, then a space, then paste your key. It should look like Bearer sai_sk_...</li><li>Click <strong>Connect</strong>.</li></ol><p>If it worked, you will see Sprite AI listed with your other connectors. Start a new chat and it will be available.</p><h3>Step two, option B: connect it to Claude Code</h3><p>This one is faster because the website writes the command for you.</p><p>Go to <a href="https://www.sprite-ai.art/mcp">sprite-ai.art/mcp</a> and click the <strong>Claude Code</strong> tab. Make sure your key is generated. The page fills in a single command with your key already inside it.</p><p>Copy that command it generates. Open your terminal. Paste it and press Enter. It looks something like this:</p><pre>claude mcp add --transport http sprite-ai https://www.sprite-ai.art/api/mcp --header &quot;Authorization: Bearer sai_sk_your_key_here&quot;</pre><p>Now start Claude Code the way you normally do. Sprite AI will be available the moment it opens.</p><p>That is the entire setup. Now try it.</p><h3>Step three: make your first character</h3><p>Start a new chat. Type something like this:</p><blockquote><em>Make me a pixel art character. A hooded figure in a deep navy cloak with amber trim and glowing amber eyes, holding a small glowing orb. Use a limited palette: navy, amber, cream, and gray. Make it 128 pixels wide and 128 tall.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*gEOWPPrHSinthUqu-v2W6Q.png" /><figcaption>Pixel art image of a navy blue hooded rogue orchestrator</figcaption></figure><p>Claude will call Sprite AI, wait about thirty seconds, and show you the result right in the chat. You will also get a link to download the image file.</p><p>A few things make this prompt work well.</p><p>Say what you want in colors and moods, not hex codes. “Deep navy” and “warm amber” land better than numbers. The tool is drawing, not filling in a paint chart.</p><p>Say the size. Ask for 128 by 128. That is the size that keeps every later step available. Bigger than 256 and you lose the ability to animate it. Smaller than 32 and the detail falls apart.</p><p>Say the angle if you have a plan. If you want the character to walk across the screen later, ask for a side view now. If you want it to face the camera, say so. You cannot change the angle after the fact.</p><h3>Step four: make it move</h3><p>Once you have a character you like, ask for motion:</p><blockquote><em>Animate that character walking. Eight frames.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vv00VKrgXnjPh_VSyhpjAQ.png" /><figcaption>Pixel art animation frames of a hooded rogue orchestrator walking</figcaption></figure><p>Claude sends the character to Sprite AI and asks for a walk cycle. About fifteen seconds later you get a strip of frames back.</p><p><em>Eight frames in a row. Play them in order and the character walks.</em></p><p>You can ask for other motions. Walk, run, jump, idle, attack, hurt, and death are all built in. You can also describe a custom motion in your own words, like “swaying in the wind” or “waving hello.”</p><p>If you want the character to jump, add “leave some room above it” to your request. That tells the tool to give the motion space instead of cutting it off at the edge.</p><h3>Step five: give it a new look</h3><p>Now ask for a style change:</p><blockquote><em>Make a gold version of that character. Same pose.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/128/1*5MtwxmWstj9fHiJHRy2pFw.png" /><figcaption>Pixel art image of a golden hooded rogue orchestrator</figcaption></figure><p>Same character, same pose, new material.</p><p><em>Same character. Same pose. Different look.</em></p><p>There are ten built-in styles: fire, ice, gold, zombie, holy, cursed, poison, royal, shadow, and steampunk. Or describe your own, like “obsidian armor with red runes.” Both cost the same.</p><h3>Four habits that save you tokens</h3><p>Sprite AI charges in tokens when you use it. A still image costs one token. A walk cycle costs fourteen. A style change costs four. So a little planning goes a long way.</p><p><strong>Ask Claude to check the rules first.</strong> Type “check what Sprite AI can do before we start.” Claude will read the tool’s own guide, which is free, and steer you away from the expensive mistakes.</p><p><strong>Lock the size on the first request.</strong> Nothing later can resize a character. Too big and you cannot animate it. Too small and it looks like mush.</p><p><strong>Pick your camera angle before you animate.</strong> A character facing you will walk toward you. A character in side view will walk across the screen. Decide before you spend fourteen tokens on motion.</p><p><strong>Keep a style consistent with words, not with the reference feature.</strong> Sprite AI has an option to reference an earlier sprite. It copies that sprite almost exactly, which is great for making the same character at a new size, and wrong for making a second, different character in the same style. For a matching set, describe the style in every prompt instead: “classic SNES RPG, chunky proportions, clean pixel outlines, warm earthy palette.”</p><h3>What it costs</h3><p>The free tier gives you 15 generations with no card. After that, plans are monthly. Creator is $8 for 100 images or 7 animations. Studio is $39 for 400 images or 28 animations. Production is $81 for 900 images or 64 animations.</p><p>Every paid plan includes a full commercial license. That means you can use the art on things you sell.</p><p>One note: the website calls them credits, and the connector calls them tokens. Same thing.</p><h3>Now the good part: what you actually do with it</h3><p>Making one character is a party trick. Here are the two things worth doing with this.</p><h3>The game you never got around to</h3><p>You have had the idea for years. A little pixel art game. A hero, a few enemies, a town. You never started because the art was the wall. You cannot draw, and hiring an artist for a hobby project never made sense.</p><p>The wall is gone. Ask Claude for your hero. Ask for the walk cycle. Ask for the three enemies, each described in the same style words. Ask for the shopkeeper, the door, the treasure chest. Every asset comes back as a file you can drop into Godot, Unity, or GameMaker. If you use Claude Code, it will save the files into your project folder for you.</p><p>You still have to make the game. But the part that stopped you is now a sentence.</p><h3>Watch your agents work</h3><p>This is the one I want you to try this week.</p><p>If you run AI agents, whether that is a research pipeline, a content system, or a multi-step workflow, you probably watch them work by reading logs. That is like understanding a factory by reading its receipts.</p><p>Instead, build a living village. Every agent becomes a pixel art character. The researcher is a miner digging ore. The writer is a scribe at a desk. The validator is a guard at a gate. When an agent actually does something, its character actually moves. Speech bubbles show what it just produced. A feed on the side lets you click into the full output.</p><p>Think of Stanford’s “generative agents” town, but every character is one of your real agents, and every animation is triggered by a real event.</p><p>Here is mine.</p><p><em>Five research agents mine ore at the top left. Two agents argue it out in the Debate Ring. A golem guards the Risk Gate. The harbormaster on the dock is the operator, watching the whole run. Every character has its own animation, and each one plays when that agent is actually working.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tJUXo1KKDqQAAIVwBe2jhA.png" /></figure><p>The art in that picture came out of Sprite AI through Claude Code. Claude picked the metaphors, generated the sprites, and built the screen. I did not draw a single pixel.</p><p>Connect Sprite AI to Claude Code, open Claude Code inside your orchestration project, and paste this:</p><pre>Build me a &quot;living village&quot; visualization UI for my agent orchestration: a pixel-art<br>world where each of my agents is an animated character doing a visual metaphor of its<br>job (think Stanford&#39;s &quot;generative agents&quot; town), plus a readable feed and controls.<br>Work in a see, fix, see loop and don&#39;t stop at &quot;it runs.&quot; Stop at &quot;it looks good.&quot;</pre><pre>STEP 1: LEARN MY SYSTEM FIRST. Explore this repo and identify: what agents exist,<br>what artifacts they write as they work (files, logs, database rows, events), and in<br>what order a typical run proceeds. My agents&#39; outputs on disk or stream ARE the UI&#39;s<br>event source. Do not modify my pipeline; observe it. If outputs aren&#39;t observable,<br>propose the smallest change (e.g. write each step to a JSON file, atomically via<br>temp-file plus rename so a watcher never reads half a file).</pre><pre>STEP 2: DESIGN THE METAPHOR MAP. For each agent, pick a physical activity that<br>represents its work (researcher = miner digging ore, writer = scribe at a desk,<br>validator = gate guardian, deployment = boat sailing to an island...). Show me the<br>map as a table before building. Every animation must bind to a REAL event, never a<br>fake timer.</pre><pre>STEP 3: GENERATE THE ART with the Sprite-AI MCP tools (sprite_generate,<br>sprite_generate_animation, sprite_rotate). Check my token balance first and show me<br>the budget. Rules learned the hard way: (a) generate ONE character first, show me,<br>and treat my approval as the style lock; (b) carry style through PROMPT LANGUAGE<br>(e.g. &quot;classic SNES RPG, chunky proportions, clean pixel outlines, warm earthy<br>palette&quot;). Do NOT use reference_asset_id across different characters; it clones<br>instead of style-matching. (c) generate scenery props too (work stations, paths,<br>landmarks). Single flat tiles read as color swatches, not a place. (d) keep<br>characters around 96px so they stay animatable; save everything plus a manifest.json<br>(file, frames, frame size per asset).</pre><pre>STEP 4: BUILD THE UI. Vanilla JS plus canvas, no build tools. A small server<br>(FastAPI or Express) that watches my artifact paths and pushes events over a<br>websocket. Required features: a sprite engine that plays 8-frame animation strips;<br>a bubble manager (max 3 speech bubbles, queued, collision-avoided; overlapping<br>bubbles are unreadable); a plain-English narration bar (&quot;The researcher is<br>working...&quot;); station labels; a dismissible 3-sentence intro so a first-time viewer<br>knows what they&#39;re seeing; a right-side scrolling feed where every agent output<br>lands as a collapsed card (avatar plus one-line plain-English headline, click to<br>expand the full output, rendered readably, never raw JSON); and a REPLAY MODE that<br>re-fires the events of a past run on a timer. That&#39;s the free demo and your test<br>harness.</pre><pre>STEP 5: POLISH LIKE AN ART DIRECTOR. Screenshot the running replay headlessly<br>(Playwright), READ the screenshots yourself, and fix what looks bad: overlaps, dead<br>space, unclear moments. Minimum three full look, fix, look passes. The exit bar: a<br>stranger seeing one screenshot could narrate what the system is doing.</pre><p>Claude will explore your project, show you a table of which agent becomes which character, ask you to approve the first sprite, then build the whole thing. When it finishes, you get a window where you can watch your pipeline run as a village. Replay mode means you can show it to someone even when nothing is running.</p><p>It will spend tokens on the art, and it will tell you the budget before it starts. Do the math before you say yes: five agents, each with one still and one animation, is 75 tokens before props. Plan on the Studio tier for this one.</p><h3>Try it this week</h3><p>Set the connector up once. Make a character. Make it walk. Give it a new look.</p><p>Then decide which dream you are chasing: the game, or the village. Either way, the art is no longer the reason you have not started.</p><p><em>If you found this useful, I ship a newsletter every Sunday in The Rogue Orchestrator covering recent claude updates, a weekly operator playbook for AI-first operators, and a weekly copy paste module to build your AI operating system piece by piece. Huge thank you to my Friend Pete for sharing the “</em>Interactive Simulacra of Human Behavior” paper with me which inspired me to build my own</p><p><em>→ Subscribe to my weekly newsletter for AI operators at </em><a href="http://rogue-orchestrators.beehiiv.com/"><em>rogue-orchestrators.beehiiv.com</em></a></p><p><em>*Disclaimer: I am in no way paid or affiliated with the providers mentioned in this post.</em></p><h3>Sources</h3><ul><li>Sprite AI: <a href="https://www.sprite-ai.art/">https://www.sprite-ai.art</a></li><li>Sprite AI connector setup page, with the key generator and the Claude Code, Cursor, Codex, and Manual tabs: <a href="https://www.sprite-ai.art/mcp">https://www.sprite-ai.art/mcp</a></li><li>Sprite AI connector guide: <a href="https://www.sprite-ai.art/docs/mcp">https://www.sprite-ai.art/docs/mcp</a></li><li>Sprite AI pricing and plan details: <a href="https://www.sprite-ai.art/pricing">https://www.sprite-ai.art/pricing</a></li><li>Sprite AI documentation: <a href="https://www.sprite-ai.art/docs">https://www.sprite-ai.art/docs</a></li><li>Concept Based on Generative Agents: Interactive Simulacra of Human Behavior (Stanford, 2023): <a href="https://arxiv.org/abs/2304.03442">https://arxiv.org/abs/2304.03442</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4acdd2ef256" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Odysseus: PewDiePie Built a Private AI Workspace That Runs Entirely On Your Own Machine]]></title>
            <link>https://medium.com/@timbiondollo/odysseus-pewdiepie-built-a-private-ai-workspace-that-runs-entirely-on-your-own-machine-44b27a743654?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/44b27a743654</guid>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[local-llm]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[llm-applications]]></category>
            <category><![CDATA[agentic-coding]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 18:31:34 GMT</pubDate>
            <atom:updated>2026-11-07T16:01:51.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FblyBamTr_b_HVxh1JL0AQ.png" /><figcaption>local llm harness Odysseus visualized as a ball of light surrounded by a secure wall</figcaption></figure><p><em>I walked through the setup so you don’t have to. Here’s what works, what doesn’t, and whether it earns space in your stack.</em></p><p>A YouTuber with 110 million subscribers just shipped a self-hosted AI workspace, and it crossed 75,000 GitHub stars before most software companies finish a sprint planning meeting. That’s not a typo. That’s the actual trajectory.</p><p>I’ll save you the suspense up front. Odysseus is real, it works, and it is not built for you to install on a Tuesday between meetings. But the reason it went viral is the part that actually matters for operators, and it has almost nothing to do with the install steps. Let me explain.</p><h3>What it actually is</h3><p>Strip away the celebrity for a second. Odysseus is a single piece of software you run on your own computer that gives you a ChatGPT-style web interface. Same chat box. Same agents. Same research and document tools you already use in the cloud. The difference is where it all lives. Instead of your conversations, files, and email sitting on someone else’s servers, everything runs on hardware you control.</p><p>The feature list reads like someone took the five SaaS tabs you keep open all day and folded them into one window. Chat with agents that can use tools and remember things. A research mode that does multi-step web searches and writes you a report. A document editor with AI edits baked in. An actual email inbox with triage, summaries, and reply drafts. Notes, tasks, and a calendar. There’s even a module called Cookbook that scans your hardware, recommends which AI models your machine can actually run from a catalog of more than 270 options, and serves them up for you.</p><p>Here’s the operator translation. This is the privacy-first version of the AI workspace you already wish your company would sanction. The model can run entirely local, which means the document you’re editing and the email you’re triaging never leave your machine. No telemetry. No vendor reading your prompts. For anyone who has ever pasted something into ChatGPT and then felt a small cold flash of “wait, should I have done that,” this is the answer to that exact feeling.</p><h3>Why it went viral this week</h3><p>The numbers do most of the talking. Felix Kjellberg, the person behind the PewDiePie name, dropped Odysseus on May 31, 2026. It pulled roughly 20,000 stars in the first 24 hours. By June 10 it was near 66,000. As I write this it sits past 75,000 stars with close to 10,000 forks, and the issue tracker has hundreds of open threads from people actually running it. That is not a vanity launch. That is a tool with a real user base forming in real time.</p><p>But star counts are downstream of a nerve getting hit. The reason this caught is that PewDiePie spent the last stretch of his career publicly walking away from big platforms and building his own stuff: his own setups, his own tools, his own infrastructure. Odysseus is the AI-shaped version of that story. He didn’t sell a privacy pitch. He shipped the thing and let people feel the difference.</p><p>And the timing is the whole point. We are at the moment where everyone wants AI in their daily work but a growing number of people are deeply uneasy about how much of their thinking now passes through a handful of company servers. I’ve watched this anxiety show up inside organizations for two years now, usually as a quiet question in a fluency session: “where does this actually go?” Odysseus is the first consumer-grade answer that a non-engineer has even heard of. Same models. Different ownership. Different feeling.</p><h3>The setup walkthrough (and an honest caveat)</h3><p>Real talk before we start. I did not spin this up on a fresh machine for this piece, because the honest install path runs through Docker and a command line, and that is not something I’d casually fire off on someone else’s computer. So treat what follows as a guide built from the official setup docs, not a from-scratch hands-on test. The steps below are accurate to the documentation. The friction notes are real. Where I’m pointing at a gotcha, it’s because the docs themselves flag it.</p><p><strong>Step 1: Know what you’re getting into.</strong> This is not a download-and-double-click app. The recommended path uses Docker, which is a tool for running software in self-contained boxes on your machine. You’ll also touch a terminal. If those two sentences made you tense up, that’s useful information, and we’ll come back to it in the verdict.</p><p><strong>Step 2: Check your hardware.</strong> The floor is 8GB of RAM, with 16GB or more recommended if you want to run AI models locally, plus about 20GB of free disk space for model downloads. Linux and macOS are the officially supported and tested environments. Windows runs but is explicitly “not actively tested,” which is the maintainer politely telling you to expect bumps.</p><p><strong>Step 3: Install the prerequisites.</strong> You need Docker Desktop (or Docker Engine with Docker Compose) and Git. Both are free. Both are a download-and-install. This is the step that separates the people who will finish from the people who won’t, and there’s no shame in either group.</p><p><strong>Step 4: Run four commands.</strong> The actual launch is genuinely short. You clone the project, copy a config file, and start it:</p><pre>git clone https://github.com/pewdiepie-archdaemon/odysseus.git<br>cd odysseus<br>cp .env.example .env<br>docker compose up -d --build</pre><p>That last command builds and boots everything. The first run takes a while because it’s downloading and assembling several services at once.</p><p><strong>Step 5: Open it and find your password.</strong> Once the containers are healthy, you open http://localhost:7000 in your browser. On first boot Odysseus creates an admin account and prints a temporary password into the terminal log. The docs tell you exactly where to find it: run docker compose logs odysseus and look for the line. You log in with that, then change it immediately in Settings. This is the single step most people miss, and then they&#39;re stuck at a login screen wondering why nothing works.</p><p><strong>Step 6: Add a model.</strong> Out of the box you have a workspace with no brain. You either plug in an API key from a provider like OpenAI in Settings, or you go fully local by installing Ollama (a free companion tool from ollama.com), pulling a model, and pointing Odysseus at it. Local is the whole reason to be here, but it’s also where your hardware either delivers or disappoints. A modest laptop will run small models fine and choke on large ones.</p><p><strong>The gotchas worth knowing.</strong> On Apple Silicon Macs, Docker can’t reach the GPU, so local models run slower on the processor unless you do a native install instead. The email feature uses old-school IMAP and SMTP login, which means Outlook and Microsoft 365 accounts mostly won’t connect yet. And the default branch is the bleeding-edge one labeled “dev,” so if you want fewer surprises, switch to the “main” branch, which the maintainer describes as the more curated version.</p><h3>How an operator would actually use this</h3><p>Set the install friction aside and picture the finished thing running on your laptop. Here’s where it earns its keep.</p><p><strong>The confidential client work.</strong> You’re a consultant sitting on a client’s financials, their org chart, their messy internal documents. You want AI help drafting and analyzing, but pasting any of it into a cloud tool violates the spirit, and possibly the letter, of your NDA. A local workspace is the clean answer. The data never leaves your machine, and you can say that with a straight face.</p><p><strong>The inbox you don’t want a vendor reading.</strong> The built-in email triage and reply drafting is genuinely useful for anyone drowning in messages, and because it runs locally with a local model, your actual correspondence isn’t training someone’s product. For an exec or a founder, that distinction is the difference between using AI on email and refusing to.</p><p><strong>The research analyst move.</strong> The deep research mode does multi-step searches and writes up a sourced report. For a marketer profiling a market or a strategist scoping a competitor, that’s a repeatable workflow that lives in one window instead of fifteen browser tabs and a Google Doc you keep losing.</p><p><strong>The proof-of-concept you can actually show your boss.</strong> If you’re the person on your team who keeps getting asked “can we do AI without the data risk,” running this once gives you a concrete, working demo. Not a slide. A thing you can point at.</p><h3>The verdict</h3><p>Here’s the thing nobody says out loud about tools like this. The value is real and the barrier is also real, and both being true at once is the whole story.</p><p>If you’re comfortable with a terminal, or you have someone technical within texting distance, install it this weekend. It’s free, it’s private, and it does genuinely useful things. If the four-commands step made your stomach drop, don’t force it today. Bookmark it instead, because two things are coming: the project is moving fast toward easier installers, and the privacy pressure that made it explode isn’t going anywhere. The version of this that your non-technical colleague can install in one click is a matter of months, not years.</p><p>Worth installing if you’re technical. Worth bookmarking if you’re not. Worth understanding either way, because the idea behind it, that your AI should run where you can see it, is about to stop being a fringe opinion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44b27a743654" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Started an AI Research Company in an Hour. Here’s the Prompt.]]></title>
            <link>https://medium.com/@timbiondollo/i-started-an-ai-research-company-in-an-hour-heres-the-prompt-3abffdfad3a3?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3abffdfad3a3</guid>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[claude]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Mon, 04 May 2026 13:37:15 GMT</pubDate>
            <atom:updated>2026-05-04T13:37:15.340Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lyYa5WxmBUtdt-pSR5OHzw.png" /></figure><p>The thing nobody tells you about starting a company in 2026 is how much of the first week is paperwork that doesn’t actually move the company forward.</p><p>Brand kit. Logo. Wordmark. Pitch deck. Competitive landscape. Go-to-market plan. Brochure site. Legal wrapper. Domain. Deployment. Each one a half-day of Googling, picking a tool, learning the tool, doing the thing, exporting it, putting it somewhere your future self can find it.</p><p>I compressed that whole first week into an hour. One prompt. Multi agent. Then twenty minutes of Stripe Atlas and a Claude Code session for the production site.</p><p>Here’s what I actually did.</p><h3>The Prompt</h3><p>I opened Claude Cowork. Started a new project in a new local folder lets name the folder “My Company”. Pasted this prompt:</p><pre>Hey Cowork, I&#39;m starting an AI research company called Archaeus<br>Research Lab. We research how the structure of training data<br>affects the emergence of capability in language models, with a<br>focus on relational and graph-encoded data structures.</pre><pre>I want you to:</pre><pre>1. Research the AI training methodology and applied AI research<br>   market. Identify the players, the white space, and where a<br>   small research lab can credibly compete.<br>2. Create a brand kit: SVG logo, wordmark, color palette,<br>   typography pairing.<br>3. Write a competitive landscape doc with named competitors<br>   and our differentiation.<br>4. Draft a GTM plan that fits a 2-person founding team with no<br>   outside funding.<br>5. Build a pitch deck following the Sequoia 10-12 slide<br>   framework, adapted for deep tech.<br>6. Make a web artifact mockup of the brochure site.</pre><pre>Enter plan mode. Ask me clarifying questions before you start.</pre><p>That’s the whole prompt. Three paragraphs. One company name. One hypothesis. One list.</p><p>The “enter plan mode and ask clarifying questions” is the part most people skip and shouldn’t. It forces the agent to think before it builds, and it gives you a chance to correct the framing before twenty minutes of work go in the wrong direction.</p><h3>What Came Back</h3><p>Cowork asked seven clarifying questions. Things like: who’s the target customer for the GTM plan, what’s the moat, what’s the funding posture, what’s the visual tone for the brand. I answered each one in a sentence or two. Twenty more lines of context.</p><p>Then it ran.</p><p>By the end of the hour, I had:</p><p>A research brief on the AI training methodology landscape with seven named competitors and a credible position for a two-person research lab to occupy.</p><p>A brand kit with an SVG logo, a wordmark in two configurations, a color palette built around dark midnight with electric cyan and violet accents, and a typography pairing that worked for both deck and web.</p><p>A competitive landscape doc that named the players honestly and articulated our differentiation in a paragraph I could actually use in a pitch.</p><p>A go-to-market plan scoped for a two-person team with no funding. Boutique consulting as the wedge. Research as the credibility engine. A clear sequence.</p><p>A 12-slide pitch deck following the Sequoia framework, adapted for deep tech, with our hypothesis, market, team, ask, and traction laid out cleanly.</p><p>A web artifact of the brochure site. Working. Live in the canvas. Looked like something a designer would charge $5K for.</p><p>One hour. One prompt. Feel free to check out the resulting site <a href="http://archaeus.ai/">Archaeus.ai</a></p><h3>The Twenty Minutes After</h3><p>The hour gives you a foundation. The next twenty minutes makes it real.</p><p>I went to Stripe Atlas and incorporated. Picked the C-corp option, gave them the company name, signed the documents. About fifteen minutes if you have your ID handy.</p><p>While that was processing, I opened Claude Code in the same local folder Cowork had been working in. The brand kit, the brochure mockup, the deck, all sat there as artifacts. I told Claude Code: <em>“Look at this folder. Build me the production landing page that matches the brochure mockup. Wire it to a GitHub repo with continuous deployment to Vercel.”</em></p><p>It read the folder. It built the site. It wired the repo. It set up the deploy. The first deploy failed because of a missing environment variable; it caught it, asked me for the value, deployed again. Live site by minute eighty.</p><p>Total elapsed time from “I should start this company” to “the company exists, has a brand, has a deck, has a website, and has legal wrapper”: about ninety minutes.</p><h3>What This Doesn’t Get You</h3><p>I want to be honest about what the hour does and doesn’t do, because most “I built a company in an afternoon” posts are subtly dishonest about the demarcation.</p><p>The hour gets you the foundation. It gets you everything that used to be the first week to month of starting a company. It does not get you a research paper. It does not get you NVIDIA Inception or a VC. It does not get you product-market fit. It does not get you a co-founder you trust with your life. Those took months and they took real work.</p><p>What the hour gets you is <em>velocity</em>. The thing it compresses is the bootstrap, not the company.</p><p>That’s actually the bigger story. There are more compression points like this in the early stages of a company than most founders have noticed yet. Foundation in an hour is one. Customer research, competitor intelligence, content velocity, hiring pipelines, ops infrastructure, the orchestration of multiple AI workstreams running in parallel while the founder focuses on judgment. Each one is a compression point. Each one collapses what used to take weeks into hours.</p><p>I’ll write that one separately. How to actually run a one-person AI research lab when the foundation is already laid and the real work begins. Different post.</p><h3>What You Can Steal Right Now</h3><p>The prompt at the top of this post works. Copy it. Replace the company description with yours. Run it through Claude Cowork in plan mode.</p><p>You’ll have your version of what I had at minute sixty.</p><p>A few things to keep in mind when you adapt it:</p><p>The “research the market” step matters. If you skip it, the brand and the deck and the GTM are built on a hypothesis the model invented. With it, they’re built on what’s actually happening in your space.</p><p>Specify the framework you want for the deck. The model will pick a default if you don’t, and the default is rarely what you want. Sequoia, Y Combinator, Pitch Anything — any of them. Just name one.</p><p>Plan mode and clarifying questions are non-negotiable. They turn a one-shot into a conversation. The conversation is where the quality is.</p><p>Use the same folder for Claude Code afterward. The artifacts Cowork generated become the context Claude Code uses to build the production version. Don’t waste that continuity by switching environments.</p><h3>The Real Unlock</h3><p>A year ago, starting a company meant a week of paperwork before you could focus on the company.</p><p>In 2026, the paperwork is an hour. The brand kit is an hour. The deck is an hour. The first version of the website is an hour. All of it. Combined. From one prompt and a clear hypothesis.</p><p>The bottleneck moved. It used to be assembly. Now it’s clarity. If you know what you’re building and why, the rest is an agent away.</p><p>If you don’t, no agent will save you.</p><p>That’s the real story.</p><p><em>If this hit something you’ve been wrestling with, give it a clap and follow. I publish weekly on building AI as an indie developer both inside organizations that weren’t built for it yet, and as a serial founder building AI native startups.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3abffdfad3a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I’d Roll Out Claude Code to Everyone (Not Just Your Engineers)]]></title>
            <link>https://medium.com/@timbiondollo/how-id-roll-out-claude-code-to-everyone-not-just-your-engineers-0449d9d18550?source=rss-63a1bdd30ff8------2</link>
            <guid isPermaLink="false">https://medium.com/p/0449d9d18550</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[enterprise-ai]]></category>
            <category><![CDATA[ai-thought-leadership]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[anthropic-claude]]></category>
            <dc:creator><![CDATA[Timothy Biondollo]]></dc:creator>
            <pubDate>Wed, 29 Apr 2026 17:27:14 GMT</pubDate>
            <atom:updated>2026-04-29T17:27:14.731Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jiZj9zC40Qp9ISIXlAo4tA.png" /></figure><p>Picture two people having the same week.</p><p>One’s a backend engineer. Day one with Claude Code. He runs it from a blank terminal, no shared anything, no idea what permission mode his security team would actually approve. He spends three days re-explaining his stack to the model in every session. By Friday he’s productive. Maybe.</p><p>The other one’s a marketer in the building next door. Same Claude Code. Same blank terminal. Same lack of any internal anything. By Friday she’s quietly given up because nobody told her she could even use it that way.</p><p>Both of them work for the same company. Both got the same Slack announcement about “AI tooling now available.” Both are now part of the rollout failure rate that nobody’s tracking yet.</p><p>There are excellent rollout playbooks out there for engineering teams. The platform-team posts. The phased-deployment guides. They’re real and they’re good, and if you’re shipping Claude Code to fifty engineers next month, go read them.</p><p>This isn’t that post. This is the one nobody’s writing yet.</p><h3>The convergence nobody’s planning for</h3><p>Claude Code stopped being an engineer-only tool a while ago. Most enterprise rollouts haven’t caught up to the fact.</p><p>Marketers are using it against their content stack. Sales ops uses it for CRM workflows. Finance uses it for spreadsheet automation. PMs use it to generate specs against their own design systems. The “command-line” framing scared off non-technical users in 2024. By 2026, half the people running Claude Code in any reasonably-sized company are not engineers. They’re just getting it to work without any of the support an engineer would.</p><p>So when you roll Claude Code out, you don’t have one user population. You have at least four or five, with completely different stacks underneath them.</p><p>That’s the thing the engineer-only playbooks miss. They assume the harness is the same for everyone because the <em>tool</em> is the same. The tool is the same. The harness can’t be.</p><h3>Why one harness for everyone fails</h3><p>A failure mode I’ve watched up close.</p><p>A central team builds a company-wide harness. They’re an engineering platform team, so the harness reflects an engineering platform team’s worldview. The setup assumes a Java service. The skills are for backend tasks. The hooks block anything that doesn’t look like a Maven build.</p><p>It auto-installs into every new Claude project across the company.</p><p>The frontend team complains first. Then the data team. Then a marketer who tried to use it for a content task wonders why every command keeps prompting her about Spring Boot. Six months later, half the company has disabled the harness and gone back to a blank terminal. The other half is in a Slack thread arguing about whose harness is the real harness.</p><p>That’s not a tool problem. That’s a <em>team</em> problem. The harness is fine for the people it was built for. Nobody in that central team was close enough to the people <em>not</em> in their stack to know what those people needed.</p><p>You can’t fix this by writing a more universal harness. There is no universal harness. A marketer’s stack is not an engineer’s stack and pretending otherwise just gives both of them a worse harness.</p><p>You fix it by changing the team’s job.</p><h3>The harness team’s actual job is running a pipeline</h3><p>Here’s where most companies get the team wrong. They think the harness team’s job is to <em>ship skills</em>. So they hire a few skilled people, those people get buried in a queue of skill requests, and the queue grows faster than they can ship. Six months in, the team is the bottleneck.</p><p>The harness team’s actual job is to <em>run a self-serve pipeline</em>. The pipeline ships the skills. The team runs the pipeline.</p><p>I’ve been running a manual version of this for a while at small scale. It works. The pieces are surprisingly simple.</p><p><strong>The intake.</strong> Anyone in the company can request a skill. They fill out a short form: what problem does this solve, who’s the user, what does the user say to trigger it, what’s the output, what context does the model need that it doesn’t have, where does that context live, what could go wrong, who QAs it. Twelve questions, maybe. Most people can do it in fifteen minutes.</p><p><strong>The request queue.</strong> Every intake row drops into a shared sheet. The queue is visible. You can see what’s been requested, what’s in progress, what shipped.</p><p><strong>The context folder.</strong> This is the one most people skip and then wonder why their skills are mediocre. The requester drops a folder of context into Google Drive. Brand guidelines. Past examples. Frameworks. Pricing docs. Whatever the model needs to do this job well. The skill doesn’t get built without it. No context, no skill.</p><p><strong>The orchestration agent.</strong> Today this is me, opening Claude Code in a folder with the context loaded, running my skill-builder skill, and letting it work. Tomorrow it should be a service that picks up new intake rows, downloads the context folder, kicks off Claude Code with the skill-builder skill, runs the QA gates, and packages the result. The orchestration is already automated. The only manual step is <em>me</em>.</p><p><strong>The distribution.</strong> When a skill is built, it ships into the company’s plugin marketplace. Anyone in the org can install it with one command.</p><p>That’s the pipeline. Five pieces. The harness team’s job is making sure every one of those pieces stays running.</p><h3>Living Skills are the magic</h3><p>Here’s the part that turns this from clever-but-still-fragile into actually self-serve.</p><p>Most skills bundle their context inside themselves. The brand voice doc, the framework, the pricing — all baked into the skill at build time. When the brand voice changes, somebody has to rebuild the skill. The harness team is back in the loop.</p><p>A Living Skill works differently. The skill points at a Google Doc the requester maintains. Every time someone uses the skill, it fetches that doc fresh. The marketer updates the brand voice doc on a Tuesday afternoon and every Claude session in the company that uses the marketing-voice skill picks up the change Tuesday evening. No rebuild. No re-deploy. No ticket.</p><p>The harness team is fully out of the loop on context updates. The requester owns their own context. The skill stays current automatically.</p><p>This is the part that makes the pipeline scale. Without Living Skills, the harness team eventually drowns in update requests. With Living Skills, ninety percent of skills update themselves the moment the requester updates their doc.</p><p>I’ve authored this kind of thing in real environments. I’ve also watched it get filed in a Slack channel and forgotten. So consider this the version I’d write if someone with authority was actually going to ship it.</p><h3>The harness is the equalizer</h3><p>A good harness is the equalizer between technical and non-technical work.</p><p>A marketer with the right skills ships at developer speed on marketing problems. A developer with the right skills ships faster on dev problems. The harness is what makes Claude Code valuable for <em>the function</em>. Without it, both people are starting from a blank terminal, which favors the engineer.</p><p>With it, the field actually levels.</p><h3>The gap</h3><p>There’s a gap most companies haven’t named yet. It sits between “we distribute Claude Code” and “we run a self-serve skill pipeline.”</p><p>The first one is procurement. You buy seats. People install it. Done.</p><p>The second one is a small team running a pipeline that lets the rest of the company build the skills they need without waiting on anyone.</p><p>Most companies are going to do the first thing in 2026 and call it a rollout. The ones that do the second are going to compound their advantage every quarter while everyone else is still arguing about whose harness is the real harness.</p><p>That’s the gap. That’s the work.</p><p><em>If this hit something you’ve been wrestling with, give it a clap and follow. I publish weekly on building AI inside organizations that weren’t built for it yet.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0449d9d18550" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>