Загрузка видео...

Не удалось загрузить видео

На главную

20-YEAR-OLD GUY SHOWS HOW CLAUDE API CAN TURN 500-VIEW CONTENT INTO A $40K/MONTH CLIENT WORKFLOW Not from a big agency. Not from hiring writers. Just taking the same service people sell every week and wiring Claude API into the boring middle. A topic goes in. It pulls the research,...

19,254 просмотров • 3 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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 просмотров • 1 месяц назад

THIS DEVELOPER BOUGHT A $799 MAC MINI AND NOW RUNS 5 FACELESS YOUTUBE CHANNELS FOR $55/MONTH WITH CLAUDE AGENTS the trick is not buying a stronger computer. the trick is giving claude its own 24/7 machine, so it can take over the screen, click through tools, move files, write scripts and keep working while his main laptop stays untouched each channel runs from its own skill. documentary, luxury, gaming, deep sea and infrastructure all have different tones, seo formats and script rules. claude can turn one topic into a 1,600-2,000 word script, 8-10 visual prompts and 3 title options without a new brief every night the whole system costs $799 once and around $55 a month to operate. claude, elevenlabs, midjourney and electricity replace the manual loop most faceless creators get stuck in after month two. the mac mini itself stays online for about $3/month setup takes around 45 minutes. fresh macos install, 32gb ram, claude desktop, computer use permissions, google drive routing, connectors and one dedicated output folder. after that the machine becomes the place where the work happens most people try to scale youtube by adding more channels and more manual work. this flips the model. one box handles research, scripts, prompts, descriptions and scheduling while the human does one review session per week month 6 is where this starts getting dangerous. the channels that survive the first 90 days are not just posting videos anymore. they are running a tiny content factory from a box under the desk

Gipp 🦅

19,829 просмотров • 2 месяцев назад

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 просмотров • 2 месяцев назад