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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

Context vs. Graphs, clearly explained! context engineering is great, but it has a ceiling: you can make one window perfect. there is still only one of it. every technique on that layer is rationing the same scarce thing. compact, retrieve less, delete, defer. all of it is deciding what... to drop. Graph engineering fixes this by moving the decision up a layer: not what goes in the window, but how many windows there are and what each one is for. you need both. here's how it works: ↳ inside a window: context engineering. what loads, in what order, what gets compacted ↳ between windows: the graph. how many lanes, what each one is allowed to see, what comes back Prompts → Context → Harness → Loops → Graphs each lane gets a clean window, nothing in one competes with anything in another, and your main thread stops filling up. the trick is being selective about what comes back. a subagent reads six thousand tokens of files and hands you a four hundred token summary. that ratio is the whole point. send back the raw material instead and you have moved the problem, not solved it. one thing to know before you scale it. not everything survives compaction equally, and almost nobody knows the table. ↳ the project-root rules file and auto memory are re-injected from disk. they come back intact ↳ path-scoped rules and nested rules files live in message history. they get summarized away and do not return until a matching file is read again so a rule that genuinely must persist cannot be path-scoped. move it to the root and pay the always-loaded cost, or accept that it is advisory in any long session. and the one that eats whole nights: shared context makes parallel agents converge. four auditors on one window produce one opinion with three echoes. you paid four times for it. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓show more

Hanako

15,703 subscribers

36,819 просмотров • 13 дней назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

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

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

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

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

Agents vs. Graphs, clearly explained! spawning more agents is great, but it has a ceiling nobody says out loud: five agents is a count. a graph is a shape. only one of them changes the answer. point five agents at the same pile with the same window and they converge. the first one writes a finding, the rest read it, and all five reports centre on the same thing. you paid five times for one opinion with four echoes. Graph engineering fixes this by moving the decision up a layer: not how many agents, but who is allowed to look at what. you need both. here's how it works: ↳ the count buys you throughput. five things happening instead of one ↳ the shape buys you coverage. five different things happening instead of the same one five times Prompts → Context → Harness → Agents → Graphs the node that does this is the splitter, and it decides more than any other node in the system. cut a repository by folder and four workers audit the same three files. cut it by blast radius and each one sees something the others cannot. the trick is being selective about what each lane is allowed to see. separate contexts are not a nice-to-have, they are the mechanism. if two agents are meant to produce different things, they must not share a window. if they are meant to produce the same thing, you did not need two agents. one thing to know before you scale it. a branch that throws does not reject the batch. it resolves to null, and that is the containment. which means your merge quietly receives a short list. ↳ filter the nulls before the merge, or one dead lane poisons the whole result ↳ never index a merge by position. eight good branches and one failure will shift everything by one, silently skip that and the run looks like it worked. the output is just missing a lane, and nothing errored. and the one that eats whole nights: multi-agent setups can use up to fifteen times the total tokens of a single chat, because every lane reloads its own core. you are trading total tokens for a clean main window. usually the right trade, always a choice. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Agents vs. Graphs, clearly explained! spawning more agents is great, but it has a ceiling nobody says out loud: five agents is a count. a graph is a shape. only one of them changes the answer. point five agents at the same pile with the same window and they converge. the first one writes a finding, the rest read it, and all five reports centre on the same thing. you paid five times for one opinion with four echoes. Graph engineering fixes this by moving the decision up a layer: not how many agents, but who is allowed to look at what. you need both. here's how it works: ↳ the count buys you throughput. five things happening instead of one ↳ the shape buys you coverage. five different things happening instead of the same one five times Prompts → Context → Harness → Agents → Graphs the node that does this is the splitter, and it decides more than any other node in the system. cut a repository by folder and four workers audit the same three files. cut it by blast radius and each one sees something the others cannot. the trick is being selective about what each lane is allowed to see. separate contexts are not a nice-to-have, they are the mechanism. if two agents are meant to produce different things, they must not share a window. if they are meant to produce the same thing, you did not need two agents. one thing to know before you scale it. a branch that throws does not reject the batch. it resolves to null, and that is the containment. which means your merge quietly receives a short list. ↳ filter the nulls before the merge, or one dead lane poisons the whole result ↳ never index a merge by position. eight good branches and one failure will shift everything by one, silently skip that and the run looks like it worked. the output is just missing a lane, and nothing errored. and the one that eats whole nights: multi-agent setups can use up to fifteen times the total tokens of a single chat, because every lane reloads its own core. you are trading total tokens for a clean main window. usually the right trade, always a choice. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

96,243 просмотров • 12 дней назад

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

73,867 просмотров • 15 дней назад

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

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

Andrej Karpathy: "Prompting is fading away. Delete everything else and keep the graph." in 68 minutes at Stanford he explains how to build one and why it is the layer everything ends up becoming LLMs → Prompts → Agents → Graphs everything before the graph is a step the graph is where the system stops being steps most people are still perfecting the thing that goes away first same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below

Andrej Karpathy: "Prompting is fading away. Delete everything else and keep the graph." in 68 minutes at Stanford he explains how to build one and why it is the layer everything ends up becoming LLMs → Prompts → Agents → Graphs everything before the graph is a step the graph is where the system stops being steps most people are still perfecting the thing that goes away first same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below

Hanako

127,756 просмотров • 12 дней назад

A million-token window solved the wrong problem, and Kimi K3 shipping one made that harder to see. 2.8T parameters, weights on your disk, an entire codebase in one prompt. Feels like memory. Isn't. Memory is what survives the session ending. A window is what survives the next token. Self-hosting sharpens it. Now you pay in GPU seconds, not API credits. Every re-read of the same history burns the same compute. Owning the weights didn't make the past free. Kimi Delta Attention cuts what long context costs. Cheaper repetition is still repetition. And a bigger window buys the one thing you don't want: room to keep everything. Nothing in a transcript is dated, ranked, or retired. Old and current load at identical weight. The fix runs beside the model, not inside it. Capture rejects, consolidation merges, decay forgets on schedule. Then a million tokens becomes headroom instead of a bill. You fill 5,000 and leave the rest empty. Look at what your longest thread reloads every run. Then ask how much of it earned the slot.

A million-token window solved the wrong problem, and Kimi K3 shipping one made that harder to see. 2.8T parameters, weights on your disk, an entire codebase in one prompt. Feels like memory. Isn't. Memory is what survives the session ending. A window is what survives the next token. Self-hosting sharpens it. Now you pay in GPU seconds, not API credits. Every re-read of the same history burns the same compute. Owning the weights didn't make the past free. Kimi Delta Attention cuts what long context costs. Cheaper repetition is still repetition. And a bigger window buys the one thing you don't want: room to keep everything. Nothing in a transcript is dated, ranked, or retired. Old and current load at identical weight. The fix runs beside the model, not inside it. Capture rejects, consolidation merges, decay forgets on schedule. Then a million tokens becomes headroom instead of a bill. You fill 5,000 and leave the rest empty. Look at what your longest thread reloads every run. Then ask how much of it earned the slot.

wast3

17,620 просмотров • 19 дней назад

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.

kocer

29,945 просмотров • 5 дней назад

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 просмотров • 3 месяцев назад

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

OpenAI CEO, Sam Altman: "You don't need to write prompts anymore. You need Loops and Graphs." In 38 minutes he explains why his own engineers stopped writing prompts, and what they build instead Prompts → Agents → Loops → Graphs a prompt buys you one answer a graph buys you the whole job, and you are not in it watch it today then save the full graph engineering guide below before everyone catches up ↓

OpenAI CEO, Sam Altman: "You don't need to write prompts anymore. You need Loops and Graphs." In 38 minutes he explains why his own engineers stopped writing prompts, and what they build instead Prompts → Agents → Loops → Graphs a prompt buys you one answer a graph buys you the whole job, and you are not in it watch it today then save the full graph engineering guide below before everyone catches up ↓

Hanako

17,768 просмотров • 7 дней назад

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

The Startup Ideas Podcast (SIP) 🧃

18,006 просмотров • 22 дней назад

“The Trump administration kept looking at a combination of three matters that needed to be addressed. The political, the security, and the economic while in some other people's minds it was just economic. You want a deal, you want money, you want minerals, please take it and save us from these troublemakers, even if it doesn't address the problem, depending on how they see it. So I'm sure that is what is still affecting, and maybe will affect, the implementation. Because what people had in mind is not necessarily 100% what they are getting. But in addressing any problem like this one, it's give and take. You don't get 100% what you want, because there are many parties concerned with the problem. Each one maybe gets a piece of what they wanted, another gets a piece of what they wanted, and together stability comes out of it. So for me, I think there is a chance.” President Kagame | #Kwibohora31

“The Trump administration kept looking at a combination of three matters that needed to be addressed. The political, the security, and the economic while in some other people's minds it was just economic. You want a deal, you want money, you want minerals, please take it and save us from these troublemakers, even if it doesn't address the problem, depending on how they see it. So I'm sure that is what is still affecting, and maybe will affect, the implementation. Because what people had in mind is not necessarily 100% what they are getting. But in addressing any problem like this one, it's give and take. You don't get 100% what you want, because there are many parties concerned with the problem. Each one maybe gets a piece of what they wanted, another gets a piece of what they wanted, and together stability comes out of it. So for me, I think there is a chance.” President Kagame | #Kwibohora31

Presidency | Rwanda

74,798 просмотров • 1 год назад

ANTHROPIC LEAKED A 4-AGENT SETUP THAT CUTS A CODEBASE AUDIT FROM 3 DAYS TO 20 MINUTES you point it at a repo and walk away - it comes back with what breaks, ranked, patches already tested. repo → map → 4 auditors → rank → fix → verify → report → back into the map the map cuts the repo by blast radius, not by folder - skip it and four agents audit the same three files and miss the one that ships broken. 4 auditors run in parallel with separate contexts - deps, secrets, dead code, hot paths, and none of them sees another's findings. rank is code, not an agent - sort by what breaks production, drop the duplicates, zero tokens. the fixer only opens patches for the top slice - a hundred findings nobody acts on is a report, not an audit. verify runs the suite on every patch and red goes back to the fixer - that patch only, never the whole batch. the back edge into the map is the whole trick - accepted findings become rules, so next week starts where this one ended. one human step in all of it: which fixes ship - 20 minutes instead of 3 days. save this and read the full graph engineering course below ↓

ANTHROPIC LEAKED A 4-AGENT SETUP THAT CUTS A CODEBASE AUDIT FROM 3 DAYS TO 20 MINUTES you point it at a repo and walk away - it comes back with what breaks, ranked, patches already tested. repo → map → 4 auditors → rank → fix → verify → report → back into the map the map cuts the repo by blast radius, not by folder - skip it and four agents audit the same three files and miss the one that ships broken. 4 auditors run in parallel with separate contexts - deps, secrets, dead code, hot paths, and none of them sees another's findings. rank is code, not an agent - sort by what breaks production, drop the duplicates, zero tokens. the fixer only opens patches for the top slice - a hundred findings nobody acts on is a report, not an audit. verify runs the suite on every patch and red goes back to the fixer - that patch only, never the whole batch. the back edge into the map is the whole trick - accepted findings become rules, so next week starts where this one ended. one human step in all of it: which fixes ship - 20 minutes instead of 3 days. save this and read the full graph engineering course below ↓

Hanako

137,040 просмотров • 20 дней назад

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

Hanako

58,753 просмотров • 21 дней назад

you might've heard about context engineering, but nobody has explained what it really is... that's why I made a full practical walkthrough on how to use it to make your AI outputs personalized and consistent in this walkthrough, I go over: – what context engineering actually is (without the jargon) – how to train AI on your own data and preferences – how to get outputs that sound like you wrote them (not generic AI) reply "context" and I'll DM it to you (must be following)

you might've heard about context engineering, but nobody has explained what it really is... that's why I made a full practical walkthrough on how to use it to make your AI outputs personalized and consistent in this walkthrough, I go over: – what context engineering actually is (without the jargon) – how to train AI on your own data and preferences – how to get outputs that sound like you wrote them (not generic AI) reply "context" and I'll DM it to you (must be following)

Tyler

20,018 просмотров • 1 год назад

Andrew Ng just released a 1-hour course on what comes after RAG. How to turn raw documents into agent memory: 00:00 - Why larger context windows are not enough 02:18 - Extract entities, relationships, and sources 14:31 - Coordinate specialized agents inside one graph 30:43 - Build it with Google ADK and Neo4j 47:25 - Turn knowledge graphs into persistent memory Most people are still learning RAG. Andrew Ng is already teaching the layer that comes after it. Documents → Entities → Relationships → Agents → Knowledge Graph More context is the old workflow. Persistent graphs are the new memory layer. This 1-hour watch is worth more than most paid GraphRAG courses. Bookmark and watch it today Then read the full graph engineering roadmap below

Andrew Ng just released a 1-hour course on what comes after RAG. How to turn raw documents into agent memory: 00:00 - Why larger context windows are not enough 02:18 - Extract entities, relationships, and sources 14:31 - Coordinate specialized agents inside one graph 30:43 - Build it with Google ADK and Neo4j 47:25 - Turn knowledge graphs into persistent memory Most people are still learning RAG. Andrew Ng is already teaching the layer that comes after it. Documents → Entities → Relationships → Agents → Knowledge Graph More context is the old workflow. Persistent graphs are the new memory layer. This 1-hour watch is worth more than most paid GraphRAG courses. Bookmark and watch it today Then read the full graph engineering roadmap below

Lunar

42,118 просмотров • 1 месяц назад

you read it and pictured yourself approving instead of watching approving what five agents, each on its own machine, handing work down the line, and what reaches you at the end is the last one's account of the four accounts before it the honest part of that piece says you do not own the harness that is the exact layer where a check on any of this would have to live a hundred and twenty a seat, three hundred at the top, about six times what you pay now you are not buying the work you are buying a shorter story about the work, told by the only party that watched it happen

you read it and pictured yourself approving instead of watching approving what five agents, each on its own machine, handing work down the line, and what reaches you at the end is the last one's account of the four accounts before it the honest part of that piece says you do not own the harness that is the exact layer where a check on any of this would have to live a hundred and twenty a seat, three hundred at the top, about six times what you pay now you are not buying the work you are buying a shorter story about the work, told by the only party that watched it happen

Lagosaur

22,401 просмотров • 9 дней назад

FOR THOSE WHO ARE CONFUSED… We experience TIME as a straight line, one moment after another, PAST TO PRESENT TO FUTURE. But that is only how it appears from inside the system. Beings in higher dimensions, what some call “ORACLES” OR “GODS,” do not experience time like this. They do not move through it. They observe it in its entirety. A closer analogy would be CHANNELS ON A SCREEN. What is playing on FOX and what is playing on CBS is not separate in existence, it is only separated by perspective. Both are happening at the same time, fully active, fully real. In the same way, what we call 1950 and what we call 2004 are not distant points moving away from each other. They are both present within the same total field of reality. From that level of awareness, nothing is being “waited on.” There is NO DELAY. There is only ACCESS. A shift of perception is all that is needed, like changing the channel. So if everything exists at once, then your FUTURE is not something that is coming toward you. It is something that already exists. The version of you 20 YEARS FROM NOW is already there. You have already CHOSEN THAT PATH, you have already GONE THROUGH WHAT COMES WITH IT, you have already LIVED THROUGH IT ALL. And what you are doing now is not creating it. You are MOVING THROUGH IT. Slowly remembering why you are there at all.

FOR THOSE WHO ARE CONFUSED… We experience TIME as a straight line, one moment after another, PAST TO PRESENT TO FUTURE. But that is only how it appears from inside the system. Beings in higher dimensions, what some call “ORACLES” OR “GODS,” do not experience time like this. They do not move through it. They observe it in its entirety. A closer analogy would be CHANNELS ON A SCREEN. What is playing on FOX and what is playing on CBS is not separate in existence, it is only separated by perspective. Both are happening at the same time, fully active, fully real. In the same way, what we call 1950 and what we call 2004 are not distant points moving away from each other. They are both present within the same total field of reality. From that level of awareness, nothing is being “waited on.” There is NO DELAY. There is only ACCESS. A shift of perception is all that is needed, like changing the channel. So if everything exists at once, then your FUTURE is not something that is coming toward you. It is something that already exists. The version of you 20 YEARS FROM NOW is already there. You have already CHOSEN THAT PATH, you have already GONE THROUGH WHAT COMES WITH IT, you have already LIVED THROUGH IT ALL. And what you are doing now is not creating it. You are MOVING THROUGH IT. Slowly remembering why you are there at all.

THE VOICE 🌹 🗣🎙🇺🇸🦅🌎⚓💜♠️CHRIST CONSCIOUSNESS

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

Google just dropped a 1-hour course on full AI engineering: from 1 agent to Loops and Graphs 7:02 - Build your first agent 13:34 - What agents can do 23:08 - Context engineering 32:56 - Graph engineering 54:11 - Full autonomous system One agent saves you an hour. A thousand replaces the team. Watch it, then read the full guide on loops and graphs below

Google just dropped a 1-hour course on full AI engineering: from 1 agent to Loops and Graphs 7:02 - Build your first agent 13:34 - What agents can do 23:08 - Context engineering 32:56 - Graph engineering 54:11 - Full autonomous system One agent saves you an hour. A thousand replaces the team. Watch it, then read the full guide on loops and graphs below

Mahax

39,647 просмотров • 16 дней назад

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

Your Claude has a tell, and almost nobody uses it. Make it start every reply with your name. One line in custom instructions, no code. The moment it stops saying your name, its context window is full. That is the exact point the output starts drifting, and you do not notice. Name stops? Start a fresh chat. It has killed about 90% of my “why has Claude gone weird” moments. Miners sent a canary down the pit to catch the gas they could not see. Same trick, for your context. Comment GUIDE and I’ll send you the exact canary setup.

Your Claude has a tell, and almost nobody uses it. Make it start every reply with your name. One line in custom instructions, no code. The moment it stops saying your name, its context window is full. That is the exact point the output starts drifting, and you do not notice. Name stops? Start a fresh chat. It has killed about 90% of my “why has Claude gone weird” moments. Miners sent a canary down the pit to catch the gas they could not see. Same trick, for your context. Comment GUIDE and I’ll send you the exact canary setup.

Charlie Hills

24,140 просмотров • 1 месяц назад