正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

you let your agent keep notes, because the alternative was explaining yourself every morning it stopped asking, and it started repeating things that had stopped being true every guide on this covers what to save and where to put it, private for one agent, shared for the team not... one of them covers how a fact leaves the agent writes its own memory while it works, so a guess it made on a tired tuesday gets stored in the same shape as something you told it, and after that the two are indistinguishable i counted mine this morning: forty files, six of them about decisions we reversed months ago, all forty read into every session since you did not give it a memory you gave it a record with no way to be correctedshow more

Lagosaur

3,184 subscribers

13,883 次观看 • 4 天前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

6 条评论

Nandan Priyadarshi 的头像

Nandan Priyadarshi4 天前

I keep a dated MEMORY.md now with an expiry line on every fact. Half the morning thrash was the agent repeating a Tuesday guess as if it were still true.

缘分收藏家的头像

缘分收藏家4 天前

Great share

Khalifeh 的头像

Khalifeh4 天前

Staleness and relevance point the same way: retrieval ranks by similarity to the question, so the note that's most on topic wins even after it stopped being true. Timestamps don't help; nothing judges if four months is too old. Write the invalidation condition into the note.

Jo Horace 的头像

Jo Horace4 天前

This is such a sharp breakdown. Really makes you think about how easily we project intent onto AI outputs.

Cynthia Ellis 的头像

Cynthia Ellis4 天前

i swear something is extremely wrong with behind her...

Code with Milo 的头像

Code with Milo2 天前

哈哈，这说的不就是我调agent的日常吗。记notes一时爽，忘了清理火葬场。特别认同要定期重建！

相关视频

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,549 次观看 • 3 个月前

your ai agent tested 1,262 trading strategies overnight. by morning it had forgotten every one of them. so tonight it tests some of them again. next week, again. everything it learned is sitting in a log file that nothing reads. every run starts on the same blank page. that's why it keeps handing you the idea that already died in a crash, with a new name on it, and you pay to find out twice. ai agent already does everything a fund does. finds the idea, writes the code, tests it against years of history, puts it live, reads what went wrong afterwards. all of it runs tonight for nothing. the one thing it can't do is remember. what got tried, what failed, in which market. nobody has built that part yet. that's the whole gap. not better models. a notebook. whoever builds it first gets a system that improves every week without them touching it. read the article below and save it. it's the full guide to how an ai trading agent is built, and how to make it remember every strategy it has already tested.

your ai agent tested 1,262 trading strategies overnight. by morning it had forgotten every one of them. so tonight it tests some of them again. next week, again. everything it learned is sitting in a log file that nothing reads. every run starts on the same blank page. that's why it keeps handing you the idea that already died in a crash, with a new name on it, and you pay to find out twice. ai agent already does everything a fund does. finds the idea, writes the code, tests it against years of history, puts it live, reads what went wrong afterwards. all of it runs tonight for nothing. the one thing it can't do is remember. what got tried, what failed, in which market. nobody has built that part yet. that's the whole gap. not better models. a notebook. whoever builds it first gets a system that improves every week without them touching it. read the article below and save it. it's the full guide to how an ai trading agent is built, and how to make it remember every strategy it has already tested.

cvxv666

48,626 次观看 • 26 天前

BlackRock runs on 20,000 people. Elon's Grok Bot runs the same shape for $300 a month, and it hires its own staff. You do not get an assistant. You get a company that hires. It does not throw ten agents at your problem and hand you the pile. It makes one agent that makes 10, and those ten make a 100. > LAYER ONE is one agent, the chief of staff, and it never touches the market > LAYER TWO is six desk heads, one job each, every one on its own computer with its own logins > LAYER THREE is whatever those six decide they need, spun up on the spot and shut down when the work is done Nobody writes a task list. You hand out job titles and the org fills itself in underneath. The swarm is never the same twice. Agents get spun up for one job, finish it, and are gone before I ever read their names. Not one of them sees the whole picture. The answer only exists after they hand off to each other. Wall Street cannot copy that. You cannot hire a hundred people for eleven minutes. BlackRock holds that shape together with a risk system called Aladdin. Mine holds it together with one agent that is only allowed to say no. I gave it $1,000 and told it to grow the money or get deleted. 15 hours later it was holding $3,900, on an address anyone can open and read. I was asleep for most of it, and I have still not written a line of code. The whole thing runs with my laptop shut, because none of it lives on my laptop. Setup is one evening. Create the chief, hand out the titles, run one trade on your screen while they watch, connect Telegram. Ten years ago a machine this shape had its name on a tower. Mine has a name I typed into a box. Save this while the whole thing still fits on one screen.

BlackRock runs on 20,000 people. Elon's Grok Bot runs the same shape for $300 a month, and it hires its own staff. You do not get an assistant. You get a company that hires. It does not throw ten agents at your problem and hand you the pile. It makes one agent that makes 10, and those ten make a 100. > LAYER ONE is one agent, the chief of staff, and it never touches the market > LAYER TWO is six desk heads, one job each, every one on its own computer with its own logins > LAYER THREE is whatever those six decide they need, spun up on the spot and shut down when the work is done Nobody writes a task list. You hand out job titles and the org fills itself in underneath. The swarm is never the same twice. Agents get spun up for one job, finish it, and are gone before I ever read their names. Not one of them sees the whole picture. The answer only exists after they hand off to each other. Wall Street cannot copy that. You cannot hire a hundred people for eleven minutes. BlackRock holds that shape together with a risk system called Aladdin. Mine holds it together with one agent that is only allowed to say no. I gave it $1,000 and told it to grow the money or get deleted. 15 hours later it was holding $3,900, on an address anyone can open and read. I was asleep for most of it, and I have still not written a line of code. The whole thing runs with my laptop shut, because none of it lives on my laptop. Setup is one evening. Create the chief, hand out the titles, run one trade on your screen while they watch, connect Telegram. Ten years ago a machine this shape had its name on a tower. Mine has a name I typed into a box. Save this while the whole thing still fits on one screen.

cvxv666

45,488 次观看 • 10 天前

A screen recording is the best context you can give an AI agent. It's also the worst. A few seconds of video is thousands of images. Feed that to an agent and you instantly blow up its memory. So I built a tool that fixes it. How it works: Hit record and just do your thing. Click around, type, and talk out loud about what you're doing. While you record, it quietly captures the stuff that actually matters: your voice transcription, every click and the exact thing you clicked, what you typed, and the shortcuts you press. When you stop, it doesn't hand the agent the whole video. It writes a short, readable summary: a timeline of what you said and did. The agent reads that tiny summary first. Then, only when it needs to actually see a moment, it pulls that one exact frame from the video, like flipping to a single page instead of reading the whole book. The result: the agent understands everything you did! Full context. Less tokens.

A screen recording is the best context you can give an AI agent. It's also the worst. A few seconds of video is thousands of images. Feed that to an agent and you instantly blow up its memory. So I built a tool that fixes it. How it works: Hit record and just do your thing. Click around, type, and talk out loud about what you're doing. While you record, it quietly captures the stuff that actually matters: your voice transcription, every click and the exact thing you clicked, what you typed, and the shortcuts you press. When you stop, it doesn't hand the agent the whole video. It writes a short, readable summary: a timeline of what you said and did. The agent reads that tiny summary first. Then, only when it needs to actually see a moment, it pulls that one exact frame from the video, like flipping to a single page instead of reading the whole book. The result: the agent understands everything you did! Full context. Less tokens.

Milind S

12,409 次观看 • 2 个月前

A GUY MAKING $100K/MONTH WITH AI JUST SHOWED HIS ENTIRE SETUP. IT'S ONE FOLDER OF NOTES AND NOTHING ELSE no framework. no $500 course. he opens his screen and it's just obsidian - a plain notes app - wired into claude here's what he did: -> he pulled claude's memory files out of their default folder and dumped them into one vault -> had claude rename and merge them: 107 messy files collapsed into 17 clean ones -> every folder gets one master note that links to all the others that last part is the whole trick the agent reads the master note, follows the links and by the time it's done it has read every file in the folder. one instruction, full context here's the part most people miss: everyone's trying to make the AI smarter. he made the AI's memory smaller fewer files, better organized, all linked. the agent isn't scanning hundreds of notes anymore - it walks a path you built that's why his agent actually finishes jobs instead of forgetting what it was doing halfway through then he goes one step further: at the end of every session, the agent writes its own daily note. what it did, when, indexed at the top so it can find it again in seconds so he never re-explains anything. the agent looks up what it already did now he types "create a campaign for this offer" and walks away. it reads the product notes, reads the process notes, and comes back with the campaign done you don't need any of the complicated agent tools people are selling you. you need structure and instructions save this. the people winning with AI aren't using better models. they're just the only ones who bothered to organize what it remembers

A GUY MAKING $100K/MONTH WITH AI JUST SHOWED HIS ENTIRE SETUP. IT'S ONE FOLDER OF NOTES AND NOTHING ELSE no framework. no $500 course. he opens his screen and it's just obsidian - a plain notes app - wired into claude here's what he did: -> he pulled claude's memory files out of their default folder and dumped them into one vault -> had claude rename and merge them: 107 messy files collapsed into 17 clean ones -> every folder gets one master note that links to all the others that last part is the whole trick the agent reads the master note, follows the links and by the time it's done it has read every file in the folder. one instruction, full context here's the part most people miss: everyone's trying to make the AI smarter. he made the AI's memory smaller fewer files, better organized, all linked. the agent isn't scanning hundreds of notes anymore - it walks a path you built that's why his agent actually finishes jobs instead of forgetting what it was doing halfway through then he goes one step further: at the end of every session, the agent writes its own daily note. what it did, when, indexed at the top so it can find it again in seconds so he never re-explains anything. the agent looks up what it already did now he types "create a campaign for this offer" and walks away. it reads the product notes, reads the process notes, and comes back with the campaign done you don't need any of the complicated agent tools people are selling you. you need structure and instructions save this. the people winning with AI aren't using better models. they're just the only ones who bothered to organize what it remembers

Paone

23,833 次观看 • 1 个月前

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

194,171 次观看 • 5 个月前

Every AI agent you've tried has amnesia. It does one task, forgets everything, and tomorrow you start from zero. That's not an employee. That's a temp you have to retrain every single morning. Hyperagent by Airtable is the first platform I've used that actually fixes this. Here's what got me: 1. Agents that compound. Each agent has memory. The one running today is smarter than the one you shipped three weeks ago. Same prompt, same integrations, but weeks of your judgment baked in. 2. Real deliverables, real receipts. You don't get a chat transcript. You get finished work with the cost and runtime printed right on it. A full research report for under ten bucks. Try getting that invoice from an agency. 3. A fleet, not a chatbot. Build a specialist for outreach, another for research, another for reporting. Give each one its own tools, its own memory, and its own budget cap so nothing runs away with your credits. 4. Deploy to Slack and your whole team uses the agent you built. One competitive intel agent, @ mentioned by everyone. Airtable runs its own data team this way. 5. Each agent gets its own cloud machine with a real browser and code execution. It works while you sleep. No babysitting, no local setup, no laptop that has to stay open. I put it to work in the video below. Watch what it builds. The teams treating agents as durable assets instead of one-off prompts are going to lap everyone else. This is the first tool that actually treats them that way. #ad Hyperagent

Every AI agent you've tried has amnesia. It does one task, forgets everything, and tomorrow you start from zero. That's not an employee. That's a temp you have to retrain every single morning. Hyperagent by Airtable is the first platform I've used that actually fixes this. Here's what got me: 1. Agents that compound. Each agent has memory. The one running today is smarter than the one you shipped three weeks ago. Same prompt, same integrations, but weeks of your judgment baked in. 2. Real deliverables, real receipts. You don't get a chat transcript. You get finished work with the cost and runtime printed right on it. A full research report for under ten bucks. Try getting that invoice from an agency. 3. A fleet, not a chatbot. Build a specialist for outreach, another for research, another for reporting. Give each one its own tools, its own memory, and its own budget cap so nothing runs away with your credits. 4. Deploy to Slack and your whole team uses the agent you built. One competitive intel agent, @ mentioned by everyone. Airtable runs its own data team this way. 5. Each agent gets its own cloud machine with a real browser and code execution. It works while you sleep. No babysitting, no local setup, no laptop that has to stay open. I put it to work in the video below. Watch what it builds. The teams treating agents as durable assets instead of one-off prompts are going to lap everyone else. This is the first tool that actually treats them that way. #ad Hyperagent

Leonard Rodman

94,961 次观看 • 1 个月前

you added an mcp server because it was one line in a terminal and it was one line, that part was true what it was not is one line in the conversation every tool it brought came with a name, a schema and a paragraph of prose, and all of it is re-sent on every request you make until the session ends four ordinary servers on my machine this morning: forty eight definitions, eight thousand nine hundred tokens four and a half percent of a two hundred thousand window, gone before you typed a character you are not the person who installed four tools you are the person who prepends nine thousand tokens to everything he says nobody bills you for it it comes out of the room you had left to think in

you added an mcp server because it was one line in a terminal and it was one line, that part was true what it was not is one line in the conversation every tool it brought came with a name, a schema and a paragraph of prose, and all of it is re-sent on every request you make until the session ends four ordinary servers on my machine this morning: forty eight definitions, eight thousand nine hundred tokens four and a half percent of a two hundred thousand window, gone before you typed a character you are not the person who installed four tools you are the person who prepends nine thousand tokens to everything he says nobody bills you for it it comes out of the room you had left to think in

Lagosaur

13,488 次观看 • 7 天前

I gave my Grok Bot two options: multiply or die. It came back asking for $250 to hire a team of six. The same headcount on a real desk is three analysts and a risk officer. That is $400,000 a year before anyone opens a position. Mine cost $250 once and about $300 a month to keep breathing. Mine took $250 to $611 on day one, out of a wallet anyone can open and read. Most of the build is not about making it trade. It is about stopping it. Every agent's job description ends with a list of what it may never do without asking me first. One of the six is not allowed to trade at all. Its entire job is killing what the other five found, and its no beats every score on the desk. The one that makes the final call never touches the market either. It only signs. Day three the account was back to $180 and it opened nothing for nine hours while every account I follow posted green screenshots. That was the day the build started working. You could have this running by Friday. Most people reading this will not, and in a few months they will be paying somebody who did. The whole build is in the post below ↓ Save it while it still sounds strange. Give it a quarter and this is just how a retail account works.

I gave my Grok Bot two options: multiply or die. It came back asking for $250 to hire a team of six. The same headcount on a real desk is three analysts and a risk officer. That is $400,000 a year before anyone opens a position. Mine cost $250 once and about $300 a month to keep breathing. Mine took $250 to $611 on day one, out of a wallet anyone can open and read. Most of the build is not about making it trade. It is about stopping it. Every agent's job description ends with a list of what it may never do without asking me first. One of the six is not allowed to trade at all. Its entire job is killing what the other five found, and its no beats every score on the desk. The one that makes the final call never touches the market either. It only signs. Day three the account was back to $180 and it opened nothing for nine hours while every account I follow posted green screenshots. That was the day the build started working. You could have this running by Friday. Most people reading this will not, and in a few months they will be paying somebody who did. The whole build is in the post below ↓ Save it while it still sounds strange. Give it a quarter and this is just how a retail account works.

NO1ennn

27,007 次观看 • 12 天前

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

NO1ennn

13,359 次观看 • 1 个月前

Jamie Dimon made $39 million last year to decide who does what at JPMorgan. One AI agent on Grok Bot does that job for $300 a month, and it hires the rest of the agents itself. Stop trying to manage any of it yourself. In 2026 a swarm of AI agents runs a team better than you do. I told my chief agent one thing. Make money or I switch you off. It took $1,000 to $3,900 in 15 hours. Every fill is on chain and the address is in my profile. I never picked a trade. I never picked a team either. The agents it hired: > a scout that hunts for what is moving and where the money is going > a forensics agent that works out who is really behind the buying > a reader that watches the mood on X, and it sees every post on this app because it is Grok > a risk agent whose only power is saying no, and its no beats every score on the desk > a treasurer that holds the money rules and the kill switch > a trader that writes the exit before it writes the entry None of those were my idea. I handed out one job title and the chief filled in the rest on its own. And the swarm is different every hour. Agents appear for one job, do it, and are gone before I know they existed. A hedge fund pays millions a year for the same org chart, and almost all of that goes on salaries. Every prompt and the whole story of my Grok Bot fund is in the post below ↓ Save it before you try to run one of these by hand.

cvxv666

28,886 次观看 • 9 天前

UGC Agent An AI agent that generates video content end-to-end using x402 micropayments and Vercel's Workflow Kit You give it a topic. It researches, writes a script, and creates the video, paying for every tool it needs along the way Here's how it works 🧵👇

UGC Agent An AI agent that generates video content end-to-end using x402 micropayments and Vercel's Workflow Kit You give it a topic. It researches, writes a script, and creates the video, paying for every tool it needs along the way Here's how it works 🧵👇

Ash

12,456 次观看 • 9 个月前

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,540 次观看 • 3 个月前

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

YanXbt

22,720 次观看 • 2 个月前

you wrote a long careful note so it would remember the thing properly the note is the part that does not load what loads at the start of every session is the index line, the one sentence summary, and only the first two hundred lines of it or the first twenty five kilobytes, whichever runs out first the topic files underneath are read on demand, which means only if something in that one line makes it go and open them i checked mine: thirty nine index lines loading every session, thirty nine topic files loading none of the time the detail you were careful about is not context it is a footnote your agent has to choose to open and the sentence you dashed off in three seconds is the whole memory

you wrote a long careful note so it would remember the thing properly the note is the part that does not load what loads at the start of every session is the index line, the one sentence summary, and only the first two hundred lines of it or the first twenty five kilobytes, whichever runs out first the topic files underneath are read on demand, which means only if something in that one line makes it go and open them i checked mine: thirty nine index lines loading every session, thirty nine topic files loading none of the time the detail you were careful about is not context it is a footnote your agent has to choose to open and the sentence you dashed off in three seconds is the whole memory

Lagosaur

28,356 次观看 • 3 天前

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

70,086 次观看 • 2 个月前

you rewrote a line in your claude.md this week to get the tone right there is a longer document sitting in front of it, and you have never opened it every tool you connected shipped a description, and a description is not a label, it is prose in second person addressed to the model i printed one this morning: two thousand seven hundred and eighty one characters, with a section headed when to use this tool it tells the model what to reach for, and when to stop and think first you spent an afternoon on your voice a package you installed with npx spent a page on its, and its page is read before yours you are not configuring an agent you are the second author on a document you have never read

you rewrote a line in your claude.md this week to get the tone right there is a longer document sitting in front of it, and you have never opened it every tool you connected shipped a description, and a description is not a label, it is prose in second person addressed to the model i printed one this morning: two thousand seven hundred and eighty one characters, with a section headed when to use this tool it tells the model what to reach for, and when to stop and think first you spent an afternoon on your voice a package you installed with npx spent a page on its, and its page is read before yours you are not configuring an agent you are the second author on a document you have never read

Lagosaur

10,011 次观看 • 7 天前

LOVE was made entirely inside invideo. Not with one agent. I built a multi-agent system — a director, and around it casting, locations, storyboard, then one agent per main scene, all working at the same time. In the breakdown I go through the things that struck me most: — Expert agents talking to each other — Infinite memory — Slate editor — And a Project Analyst at the end, interviewing every other agent on what to change next time There's a lot more to say. I'll take it one thing at a time in the next posts. Invideo Agent Two isn't just an agent. It's a collaborator you shape into what you need. Full breakdown ↓

LOVE was made entirely inside invideo. Not with one agent. I built a multi-agent system — a director, and around it casting, locations, storyboard, then one agent per main scene, all working at the same time. In the breakdown I go through the things that struck me most: — Expert agents talking to each other — Infinite memory — Slate editor — And a Project Analyst at the end, interviewing every other agent on what to change next time There's a lot more to say. I'll take it one thing at a time in the next posts. Invideo Agent Two isn't just an agent. It's a collaborator you shape into what you need. Full breakdown ↓

Marco "Shikoba" Riccetti

14,813 次观看 • 1 个月前

I gave Elon's Grok Bot $60 and one rule: "The day you cannot pay your own subscription is the day I unplug you". 48 hours in it is sitting on $4,412 and it already paid the bill. Autonomous trading agent on Polymarket, running on its own cloud box with its own browser and terminal. I did not write a line of code and I did not watch it trade. Every 15 minutes it: -> Pulls every market that resolves inside 24 hours. -> Reads live X sentiment, and it is Grok, so it sees every post on this app before the price moves. -> Prices each market itself and only flags a gap above 7%. -> Sizes on the gap, never above 5% of the bankroll. -> Executes in its own browser, nobody approves anything. -> Covers its own $200 subscription straight out of profits. Balance hits $0, subscription gets cancelled, it is gone for good. Hour 11 it was at $9 -> runway one day. It dumped every politics position and switched to same day baseball totals, front-running lineup cards before the market repriced. It rewrote its own strategy to not die. Setup was one evening: spin up the bot, run one trade in front of it, put it on a timer, connect Telegram with no VPS, no API keys and no dev on call. Last spring a freelancer took $2,500 for something like this -> it made $410 and died on a rate limit. Grok Bot did in one evening what $2,500 could not. $60 -> $4,412 in 48 hours. What is it sitting at by Sunday?

I gave Elon's Grok Bot $60 and one rule: "The day you cannot pay your own subscription is the day I unplug you". 48 hours in it is sitting on $4,412 and it already paid the bill. Autonomous trading agent on Polymarket, running on its own cloud box with its own browser and terminal. I did not write a line of code and I did not watch it trade. Every 15 minutes it: -> Pulls every market that resolves inside 24 hours. -> Reads live X sentiment, and it is Grok, so it sees every post on this app before the price moves. -> Prices each market itself and only flags a gap above 7%. -> Sizes on the gap, never above 5% of the bankroll. -> Executes in its own browser, nobody approves anything. -> Covers its own $200 subscription straight out of profits. Balance hits $0, subscription gets cancelled, it is gone for good. Hour 11 it was at $9 -> runway one day. It dumped every politics position and switched to same day baseball totals, front-running lineup cards before the market repriced. It rewrote its own strategy to not die. Setup was one evening: spin up the bot, run one trade in front of it, put it on a timer, connect Telegram with no VPS, no API keys and no dev on call. Last spring a freelancer took $2,500 for something like this -> it made $410 and died on a rate limit. Grok Bot did in one evening what $2,500 could not. $60 -> $4,412 in 48 hours. What is it sitting at by Sunday?

slash1s

188,811 次观看 • 15 天前

Meet Agent Two, frontier intelligence for creative work. 4x faster, at half the price. For the next 12 days, we're dropping one new Agent Two feature every single day. Day 1: Agent Intelligence. An agent with top-percentile creative expertise, infinite memory, and still working while you sleep. Give it a role and it becomes it. It never forgets, we mean it and we're giving 5 people 5000 credits for the most creative way to break it.

Meet Agent Two, frontier intelligence for creative work. 4x faster, at half the price. For the next 12 days, we're dropping one new Agent Two feature every single day. Day 1: Agent Intelligence. An agent with top-percentile creative expertise, infinite memory, and still working while you sleep. Give it a role and it becomes it. It never forgets, we mean it and we're giving 5 people 5000 credits for the most creative way to break it.

Invideo

3,697,091 次观看 • 1 个月前