正在加载视频...

视频加载失败

MOST PEOPLE USE CLAUDE CODE LIKE CHATGPT WITH A TERMINAL That is why they only get 30% of the value. They paste a task, wait for an answer, then keep explaining the same rules again when the context gets messy. The real power starts when you stop treating it...

15,347 次观看 • 4 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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 次观看 • 4 个月前

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 次观看 • 4 个月前

Why your AI gets dumber the longer you chat (context rot): the one Claude Code file, plus one habit, that fixes it How context rot works: 1. Everything in your chat sits in the AI's working memory, the context window: every message, every file it opened, every answer it gave. The model reads through all of it before every reply. 2. Anthropic, the company behind Claude, says the more tokens you pile into the context window, the worse the model gets at recalling any one thing in it. They call it an attention budget, and every new token spends a little of it. 3. When the window fills up, Claude Code compacts: it replaces the conversation with a summary. If a rule only lived in the chat, it can get lost in that summary. The fix is one file, CLAUDE.md, plus one habit. 4. CLAUDE.md is a plain text file in your project folder. Claude Code reads it at the start of every session, and after compaction it re-reads it from the file. Think of it as a sign bolted above the whiteboard: wipe the board all you want, the sign stays. 5. How to create a CLAUDE.md: open Claude Code in your project folder and type /init. It writes a first draft. Then add what it can't guess: who you are, who the client is, and your rules ("never change a headline without asking", "prices come from column D of the Google Sheet", "dates are day, month, year"). 6. Keep CLAUDE.md short. Anthropic's Claude Code guide says to aim for under 200 lines, because a bloated file gets ignored too. For every line, ask: would it make a mistake without this? If not, cut it. The other half of the fix is how you work: 7. One job, one session. Type /clear when you switch jobs: the board's wiped, and the sign (CLAUDE.md) is still up. 8. If you've corrected the AI twice on the same thing, skip round three in capitals. Clear it, put the rule in CLAUDE.md, and start again. This is context engineering for people who don't code: an AI assistant that remembers your business rules, your clients and your formats, for client work, reports, content, spreadsheets and proposals, whether you're a freelancer, an agency or a small business. #claudecode #aiagents #contextengineering #learnai

Professor Glitch

12,900 次观看 • 1 个月前

Grok Bot + Kimi K3 can be turned into something bigger than an agent: an AI operating system the formula: AI OS = Router + Reasoning + Memory + Tools + Loops + Verification not one giant assistant. six layers that keep work moving without you step 1 -> Grok Bot becomes the operator. you give it the goal, it breaks the goal into jobs, assigns priorities and decides what part of the system should act next. step 2 -> Kimi K3 becomes the reasoning core. hard research, synthesis, long context and planning move here instead of forcing every task through the same model. step 3 -> externalize memory. store goals, decisions, failed attempts, artifacts and current state outside the chat. close the session, come back tomorrow, and the system still knows where it is. step 4 -> connect tools: search, code, files, APIs, docs and data. reasoning decides what should happen. tools actually make it happen. step 5 -> add the loop engine: plan -> execute -> inspect -> update memory -> retry. the loop can wait for new information, rerun a failed task, hand work to another agent or stop when the goal is complete. step 6 -> verify before output. tests, source checks, constraints and explicit completion rules decide whether the system ships the result or sends it back into the loop. that's the difference between an AI assistant and an AI operating system. an assistant waits for your next message. an operating system carries state, routes work and keeps moving. Grok Bot handles orchestration, Kimi K3 handles deeper reasoning, memory keeps the state alive, tools execute, the loop keeps the system running, verification decides when it is actually done. build one reliable loop and you have an agent. connect reasoning, memory, tools and multiple loops around it and you start building infrastructure. the full Grok Bot + Kimi K3 AI OS breakdown is below ↓

Alex

13,312 次观看 • 2 个月前

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

378,296 次观看 • 8 个月前

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

201,127 次观看 • 2 年前

How to create AI employees — start to finish, everything included The complete build of an AI employee, start to finish — the whole path in under four minutes. The agent underneath — every AI employee starts as an agent: a brain (the AI model), tools (real connections into your email, calendar, spreadsheets so it acts instead of only talking), and a loop (it works the job, checks itself, and keeps going until it's done). Feed the brain context and it works on YOUR business. The four upgrades that make it an employee — memory (corrections get written down and read back before every job — explain a thing once and it stays explained), permanent context (your world lives with it and changes as your business changes), skills (your way of doing a job, taught once, followed every time), and a schedule (an agent runs when you call it — an employee clocks in on its own, seven in the morning, inbox already sorted). The build tool — an AI coding assistant: Claude Code or Codex. That class of tool IS the agent machinery — it navigates your context, picks its next move, loops until the job is done, and carries memory between runs. You set it up in plain English, and when a piece you need exists nowhere, it writes that piece itself. The full assembly — pick one job, give it context, wire the tools, teach the skill, add memory, set the schedule. One rule built in: high-stakes moves wait for your yes; everything else runs around the clock. The ceiling — one employee becomes a pattern, patterns become a team, and the team becomes a department passing work to each other. This video is the skeleton of my entire curriculum — every step is a full course, taught from zero, step by step, about four months front to back. It's all inside my community. #aiemployee #aiagent #aiautomation

Professor Glitch

12,600 次观看 • 2 个月前