Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

HE TURNED A $599 MAC MINI INTO A CLAUDE SECOND BRAIN USING OBSIDIAN, PYTHON AND A FEW ALWAYS-ON LOOPS not a fancy SaaS dashboard. not another chat tab. a tiny box on a desk that can pull lectures, transcribe audio, read articles, clean notes and write everything into a...

65,142 Aufrufe • vor 1 Monat •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 Aufrufe • vor 1 Monat

One guy keeps a farm of Mac minis on his desk and says each $600 box brings him $2,000 a month while he sleeps. AND THE HARDWARE ACTUALLY WORKS. But the number is not even the interesting part. The broken part is HOW: his AI no longer sits in a chat window. It sees the screen, moves the mouse itself, types and clicks the interface like a human at a computer. That is it. While most people still run AI in a chat and ask it for text, he sat Claude down right at the computer and put it to work with its hands. He automated not a single task but the workplace itself. How it actually works: on every Mac mini Claude runs with computer use turned on and the official Claude API docs spell it out: screenshot capture, mouse control, keyboard input, desktop automation. The agent opens the browser and the apps itself and runs the boring routine on a schedule: pulls leads, fills the CRM, checks orders, runs QA on the site. One box, one quiet worker that does not sleep and does not ask for a salary. His math is simple: a Mac mini is $600 once, Claude Max is $200 a month, and a live white-collar worker on the same routine costs a business $4,000 and up. So he rents out each node to a client as an AI worker for about $2,000 and 6 Mac minis come out to around $12,000 a month with costs a bit over $1,000 on subscriptions. But the $12,000 is his projection not a revenue dashboard: the video has no client, no task log, no working automation at all. The real asset here is not the stack of hardware but the one repeatable process the agent actually closes. Because a Mac mini on its own earns nothing. The money shows up exactly where the boring browser routine used to be done by hand for a salary and now you can hand it to an agent for the price of a subscription. Computer use is still in beta, almost nobody builds a service on it and the demand for cheap GUI routine is huge. The window is open for literally the next few months. Most people will watch this, laugh at the "$600 AI worker" and close it. And the ones who actually put an agent on one boring task and grind it into a repeat will ride this wave while it is still empty. Would you sit an AI right at your own computer on the boring routine or are you still clicking through it by hand?

Sorven

11,948 Aufrufe • vor 1 Monat