Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Forget Muse. Forget Instinct. The real move is OpenMuse + Jev 🤯 OpenMuse is the open-source personal agent that dropped last week. Its own browser, your apps, actually does things for you. You host it yourself. But the routing is the real unlock. Jev picks the best model for...

alex_prompter's profile picture

Alex Prompter

282,847 subscribers

13,590 görüntüleme • 1 gün önce •via X (Twitter)

EğitimOyunBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

2 Yorum

Mira Synth Tech profil fotoğrafı
Mira Synth Tech1 gün önce

Love the model routing idea, super efficient setup

Tomasz Wojewoda profil fotoğrafı
Tomasz Wojewoda1 gün önce

Seems like a context and cache mess. Are you sure?

Benzer Videolar

Jev + Opus 5.5: Anthropic's new model beats GPT-6 Astra for 1/5 the cost, and 4 API changes will 400 your agent before it writes a single line I pulled these 10 steps from the migration docs so you don't learn them in production step 1 → $4 / $20 per 1M. Opus 5 was $5 / $25. cache reads dropped from $0.50 to $0.20 step 2 → 66.4% on Terminal-Bench 4.0 vs GPT-6 Astra 57.9% and Opus 5 52.3%. +14.1 points in one release, and on FrontierCode it beats Astra at default effort for 1/5 the cost step 3 → thinking can't be turned off anymore. send thinking: disabled and you get a 400. drop the field, set effort step 4 → tool_choice any and tool are gone. 400. switch to auto + strict step 5 → edit anything above a thinking block and the request dies. append only, or opt into drop_block step 6 → computer_20251124 is dead on the API. 400. move to computer_toolset_20260801 step 7 → the quiet one: default effort fell from high to medium. your agent thinks less than you set it up to and nothing tells you step 8 → hop Opus 5.5 → Sonnet 5 → Opus 5.5 and you pay 4.36 instead of 3.32. +31%, the cache dies and Sonnet can't read Opus's reasoning step 9 → change effort at the top of the request and the cache is gone. Jev sets it per message and the cache stays step 10 → switch fast - standard mid-session and it's a full cache miss. Jev picks speed once, on turn one one model, three knobs, zero 400s. that is Jev + Opus 5.5 send this to your Claude Code before you touch the model ID, then read my full Jev deep dive in the article below ↓
0:40

Jev + Opus 5.5: Anthropic's new model beats GPT-6 Astra for 1/5 the cost, and 4 API changes will 400 your agent before it writes a single line I pulled these 10 steps from the migration docs so you don't learn them in production step 1 → $4 / $20 per 1M. Opus 5 was $5 / $25. cache reads dropped from $0.50 to $0.20 step 2 → 66.4% on Terminal-Bench 4.0 vs GPT-6 Astra 57.9% and Opus 5 52.3%. +14.1 points in one release, and on FrontierCode it beats Astra at default effort for 1/5 the cost step 3 → thinking can't be turned off anymore. send thinking: disabled and you get a 400. drop the field, set effort step 4 → tool_choice any and tool are gone. 400. switch to auto + strict step 5 → edit anything above a thinking block and the request dies. append only, or opt into drop_block step 6 → computer_20251124 is dead on the API. 400. move to computer_toolset_20260801 step 7 → the quiet one: default effort fell from high to medium. your agent thinks less than you set it up to and nothing tells you step 8 → hop Opus 5.5 → Sonnet 5 → Opus 5.5 and you pay 4.36 instead of 3.32. +31%, the cache dies and Sonnet can't read Opus's reasoning step 9 → change effort at the top of the request and the cache is gone. Jev sets it per message and the cache stays step 10 → switch fast - standard mid-session and it's a full cache miss. Jev picks speed once, on turn one one model, three knobs, zero 400s. that is Jev + Opus 5.5 send this to your Claude Code before you touch the model ID, then read my full Jev deep dive in the article below ↓

Carnage

16,674 görüntüleme • 6 gün önce

Do you understand what just got open sourced? 5,800+ quant trading strategies for FREE along with its CODEBASE i gave these trading strategies to opus 5.5 + jev and it built me a PROFITABLE 24/7 trading agent here is how to use the repo and build AI trading bot: 1. clone the vault and get 5,806 trading strategies (spot, perps, grid, stat arb and market making) 2. open any strategy file, the math, the parameters and the source are already inside 3. point AgenKit at that file inside Claude Code with model as opus 5.5, one command and it reads the spec as ground truth 4. it will run a full engineering team and ships a production bot with risk controls 5. Jev is the live brain, it answers buy sell or hold in 81 milliseconds, calibrated, no hallucination 6. your engine sizes the trade from that confidence and fires it before the next block 7. a hard risk layer holds every limit, nothing goes live until you approve it 8. every night Opus 5.5 reviews the fills and ships a better version, so the agent improves while you sleep one model THINKS, the other REACTS and a strategy that sat locked in a vault now trades itself 24/7 the COMPLETE codebase and the EXACT Opus 5.5 + Jev trading system which I am running is in the article below:
0:39

Do you understand what just got open sourced? 5,800+ quant trading strategies for FREE along with its CODEBASE i gave these trading strategies to opus 5.5 + jev and it built me a PROFITABLE 24/7 trading agent here is how to use the repo and build AI trading bot: 1. clone the vault and get 5,806 trading strategies (spot, perps, grid, stat arb and market making) 2. open any strategy file, the math, the parameters and the source are already inside 3. point AgenKit at that file inside Claude Code with model as opus 5.5, one command and it reads the spec as ground truth 4. it will run a full engineering team and ships a production bot with risk controls 5. Jev is the live brain, it answers buy sell or hold in 81 milliseconds, calibrated, no hallucination 6. your engine sizes the trade from that confidence and fires it before the next block 7. a hard risk layer holds every limit, nothing goes live until you approve it 8. every night Opus 5.5 reviews the fills and ships a better version, so the agent improves while you sleep one model THINKS, the other REACTS and a strategy that sat locked in a vault now trades itself 24/7 the COMPLETE codebase and the EXACT Opus 5.5 + Jev trading system which I am running is in the article below:

Roan

84,559 görüntüleme • 2 gün önce

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.
1:54

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 görüntüleme • 3 ay önce

Jev is WILD for SEO audit 🤯 in 45.1 seconds it read all 586 pages on my site and rebuilt the internal link map. 584 links placed, 139 pages it refused to link because nothing honestly fit. total cost $0.21. Claude Opus 5, same 586 pages, same clock, got through 21 of them and spent $1.43. per page that is ~190x cheaper. the full Opus pass would have run $43. internal linking is the perfect Jev job. it is not writing, it is 8,790 yes/no calls: does this page have a real reason to link to that one, and is there anchor text already sitting in the copy. that is a classification problem, and we have been paying frontier prices to do it one page at a time. what you are watching: left column is Jev, right is Opus, same queue, same rubric. the run stops the moment Jev finishes so Opus stops burning tokens. coming soon to Distribb + connector + gpt plugin
0:24

Jev is WILD for SEO audit 🤯 in 45.1 seconds it read all 586 pages on my site and rebuilt the internal link map. 584 links placed, 139 pages it refused to link because nothing honestly fit. total cost $0.21. Claude Opus 5, same 586 pages, same clock, got through 21 of them and spent $1.43. per page that is ~190x cheaper. the full Opus pass would have run $43. internal linking is the perfect Jev job. it is not writing, it is 8,790 yes/no calls: does this page have a real reason to link to that one, and is there anchor text already sitting in the copy. that is a classification problem, and we have been paying frontier prices to do it one page at a time. what you are watching: left column is Jev, right is Opus, same queue, same rubric. the run stops the moment Jev finishes so Opus stops burning tokens. coming soon to Distribb + connector + gpt plugin

borja

832,795 görüntüleme • 11 gün önce

THIS GUY PUT FABLE, GPT 5.6 SOL, AND OPUS IN ONE SHARED CHAT AND HAS THEM TAG EACH OTHER LIKE COWORKERS instead of running three separate models in three separate windows and copy pasting between them, they all sit in one room and talk to each other > you tag whichever model you want and only that one responds > they tag each other too, so fable can hand something to opus, opus can pull in sol for a second opinion > each agent only sees the messages theyre mentioned in, but you get to read everything > he had them running and orchestrating together for more than a day straight the best part is how different each one actually behaves: > fable is the creative product manager. huge context window so it remembers everything, and its the one finding the out of the box solutions > sol is the obsessive tech lead. it will trace every bug to the exact source and stress test every edge case before writing a single line > opus is the workhorse engineer. smart enough for almost anything, and it constantly questions things, which forces the other two to re-examine their own solutions its like managing a team. one plans, one writes the code, one reviews it, and they hand work back and forth without you playing middleman everyone else is arguing about which model is best right now, but the real play is making them work together at the same time
1:11

THIS GUY PUT FABLE, GPT 5.6 SOL, AND OPUS IN ONE SHARED CHAT AND HAS THEM TAG EACH OTHER LIKE COWORKERS instead of running three separate models in three separate windows and copy pasting between them, they all sit in one room and talk to each other > you tag whichever model you want and only that one responds > they tag each other too, so fable can hand something to opus, opus can pull in sol for a second opinion > each agent only sees the messages theyre mentioned in, but you get to read everything > he had them running and orchestrating together for more than a day straight the best part is how different each one actually behaves: > fable is the creative product manager. huge context window so it remembers everything, and its the one finding the out of the box solutions > sol is the obsessive tech lead. it will trace every bug to the exact source and stress test every edge case before writing a single line > opus is the workhorse engineer. smart enough for almost anything, and it constantly questions things, which forces the other two to re-examine their own solutions its like managing a team. one plans, one writes the code, one reviews it, and they hand work back and forth without you playing middleman everyone else is arguing about which model is best right now, but the real play is making them work together at the same time

Om Patel

22,998 görüntüleme • 2 ay önce

You can now choose which model builds your app on Caffeine. The latest models are all in there: Opus 5.5 Fable 5.1 GPT-6 Astra GPT-6 Sol Kimi K3 Sonnet 5 DeepSeek V4.1 Flash Plan a whole new app with a frontier model, then switch to a faster, cheaper one for quick questions and small changes. It works on every plan, starting today.
3:11

You can now choose which model builds your app on Caffeine. The latest models are all in there: Opus 5.5 Fable 5.1 GPT-6 Astra GPT-6 Sol Kimi K3 Sonnet 5 DeepSeek V4.1 Flash Plan a whole new app with a frontier model, then switch to a faster, cheaper one for quick questions and small changes. It works on every plan, starting today.

caffeine

15,398 görüntüleme • 5 gün önce

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
35:25

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,524 görüntüleme • 5 ay önce

Introducing Gateway. Your agent needs to check a payment. You hand it a key that can also refund it. It needs to draft a page. That key can archive every page. Not anymore. Gateway gives every agent one key with only the tools you grant. MCP servers and your own APIs, same key. Change the grant when the job changes. The agent never sees your real credentials. Beta customers already run over 95,000 calls each through it. Watch it work ↓
1:32

Introducing Gateway. Your agent needs to check a payment. You hand it a key that can also refund it. It needs to draft a page. That key can archive every page. Not anymore. Gateway gives every agent one key with only the tools you grant. MCP servers and your own APIs, same key. Change the grant when the job changes. The agent never sees your real credentials. Beta customers already run over 95,000 calls each through it. Watch it work ↓

mem0

33,944 görüntüleme • 14 gün önce

HERMES AGENT NOW RUNS A FULL BUSINESS FOR $8/MONTH. CONTENT. CODE. INBOX. ALL AGENTS. EVERYTHING WHILE YOU SLEEP. one user built this in one session. zero terminal commands. browser only. the team: → content agent: finds video topics, writes first drafts, helps with animations → code builder: writes website and SaaS code → ops agent: organizes and answers email total setup cost: $1. monthly runtime: $8 VPS + cheap model API. the trick is matching model to task. frontier models (Opus 4.8, GPT-5.5) for complex /goals only. $5/million tokens. mid-tier (Claude Sonnet, Haiku, Kimiko 2.6) for daily content and research work. budget (DeepSeek V4 Flash, MiniMax 2.7, Gemma 4, Qwen 3) for cron jobs and routine. run the initial setup on Opus. switch to DeepSeek for everything after. your bill drops 90% with zero quality loss on routine work. the agent team picks up tasks from kanban. each completed task creates a skill. week 3 the same workflows run faster than week 1. full breakdown on Hermes Os in the article 👇
14:53

HERMES AGENT NOW RUNS A FULL BUSINESS FOR $8/MONTH. CONTENT. CODE. INBOX. ALL AGENTS. EVERYTHING WHILE YOU SLEEP. one user built this in one session. zero terminal commands. browser only. the team: → content agent: finds video topics, writes first drafts, helps with animations → code builder: writes website and SaaS code → ops agent: organizes and answers email total setup cost: $1. monthly runtime: $8 VPS + cheap model API. the trick is matching model to task. frontier models (Opus 4.8, GPT-5.5) for complex /goals only. $5/million tokens. mid-tier (Claude Sonnet, Haiku, Kimiko 2.6) for daily content and research work. budget (DeepSeek V4 Flash, MiniMax 2.7, Gemma 4, Qwen 3) for cron jobs and routine. run the initial setup on Opus. switch to DeepSeek for everything after. your bill drops 90% with zero quality loss on routine work. the agent team picks up tasks from kanban. each completed task creates a skill. week 3 the same workflows run faster than week 1. full breakdown on Hermes Os in the article 👇

YanXbt

30,910 görüntüleme • 3 ay önce

OPUS 4.6 WAS NERFED DUE TO DEMAND BUT OPUS 4.5 DOES NOT SEEM TO BE HIT this guy ran the same test on both models. Opus 4.6 fails consistently but Opus 4.5 passes every time he switched back to Opus 4.5 on Claude Code and said "what a difference, feels like i got Opus back finally" he is now using this test as a "quantization canary" that runs it at the start of every session before doing real work. if it fails, the model is degraded. five Opus 4.6 windows in a row failed the untransparent nerfing is pushing people to cancel their Max plans if you've been feeling like Opus got dumber lately, you're not imagining it i'd suggest switching to Opus 4.5 to see the difference for yourself
1:03

OPUS 4.6 WAS NERFED DUE TO DEMAND BUT OPUS 4.5 DOES NOT SEEM TO BE HIT this guy ran the same test on both models. Opus 4.6 fails consistently but Opus 4.5 passes every time he switched back to Opus 4.5 on Claude Code and said "what a difference, feels like i got Opus back finally" he is now using this test as a "quantization canary" that runs it at the start of every session before doing real work. if it fails, the model is degraded. five Opus 4.6 windows in a row failed the untransparent nerfing is pushing people to cancel their Max plans if you've been feeling like Opus got dumber lately, you're not imagining it i'd suggest switching to Opus 4.5 to see the difference for yourself

Om Patel

696,175 görüntüleme • 5 ay önce

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.
3:10

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 görüntüleme • 1 ay önce

JEV + OPUS 5.5 IS INSANE FOR BUILDING A COMPANY BRAIN I pulled the whole architecture out of the TypeSafe and Anthropic docs and packed it into a 14-page PDF the 10 steps: 1. meet the pair > Opus 5.5 thinks, Jev decides, your code holds the branch 2. stop asking a text generator for a yes or no > Jev returns a typed answer with a calibrated probability in 0.44s for $0.00035 3. ask everything at once > Choice, Score and Noul run in parallel, so the fourth question costs almost nothing 4. branch on the number > 0.999 goes straight into the if statement. ~99% of turns end right here 5. stop routing blind > Opus 5.5 to Sonnet and back costs 5.84 against 3.32 for staying on 5.5 6. keep one context warm > cache reads at $0.20 per Mtok are 20x cheaper than a fresh load 7. escalate the hard part > the toughest 1% goes to Opus 5.5 with 1M context and 66.4% on Terminal-Bench 4.0 8. score every chunk on every query > keep whole, summarize or drop. the context gets rebuilt each turn 9. gate the actual command > every bash call gets classified before it runs, inside your own code 10. judge 100% of runs > $3.50 a day for 10,000 traces, and it matched the human label on all 500 decisions the result: a while loop that paid a frontier model for every tiny call turns into a brain that spends a fraction of a cent to notice and pays properly only when it has to think the person who brings this into their team walks into the budget meeting with the AI bill cut and the output up the PDF maps the company brain. the loop side of it - how Jev takes a Claude bill from $765 to $3 a month - is in the article below ↓
0:24

JEV + OPUS 5.5 IS INSANE FOR BUILDING A COMPANY BRAIN I pulled the whole architecture out of the TypeSafe and Anthropic docs and packed it into a 14-page PDF the 10 steps: 1. meet the pair > Opus 5.5 thinks, Jev decides, your code holds the branch 2. stop asking a text generator for a yes or no > Jev returns a typed answer with a calibrated probability in 0.44s for $0.00035 3. ask everything at once > Choice, Score and Noul run in parallel, so the fourth question costs almost nothing 4. branch on the number > 0.999 goes straight into the if statement. ~99% of turns end right here 5. stop routing blind > Opus 5.5 to Sonnet and back costs 5.84 against 3.32 for staying on 5.5 6. keep one context warm > cache reads at $0.20 per Mtok are 20x cheaper than a fresh load 7. escalate the hard part > the toughest 1% goes to Opus 5.5 with 1M context and 66.4% on Terminal-Bench 4.0 8. score every chunk on every query > keep whole, summarize or drop. the context gets rebuilt each turn 9. gate the actual command > every bash call gets classified before it runs, inside your own code 10. judge 100% of runs > $3.50 a day for 10,000 traces, and it matched the human label on all 500 decisions the result: a while loop that paid a frontier model for every tiny call turns into a brain that spends a fraction of a cent to notice and pays properly only when it has to think the person who brings this into their team walks into the budget meeting with the AI bill cut and the output up the PDF maps the company brain. the loop side of it - how Jev takes a Claude bill from $765 to $3 a month - is in the article below ↓

Mr. Buzzoni

82,563 görüntüleme • 1 gün önce

THIS GUY USED OPUS 4.8 + KIMI K2.6 TO CUT HIS CODING BILL FROM $4,000 TO $700/MO. WITH KIMI RUNNING A 300-AGENT CODING FLOOR, HE STOPPED PAYING CLAUDE TO DO EVERYTHING kimi does the cheap heavy lifting. it can spin up hundreds of agents, push through thousands of steps, write the rough code, expand files, draft tests and handle the repetitive work that burns the most tokens opus 4.8 only comes in where the money is worth spending. first to plan the spec and define the rules, then again to tear apart the output, catch weak logic and flag the bugs that a fast swarm can miss that is what changed the economics. kimi handled the bulk of the volume for a fraction of the price, while opus stayed in the loop as the architect and the reviewer instead of the full-time builder most people still use one model for every step and wonder why their costs explode. this guy split the jobs properly. kimi runs wide and cheap. opus goes deep and skeptical. one builds fast, the other makes sure it should ship the real edge is not finding one perfect model. it is knowing where expensive intelligence actually matters and where cheap parallel output is already enough. that is how a $4,000 workflow turns into a $700 system
1:28

THIS GUY USED OPUS 4.8 + KIMI K2.6 TO CUT HIS CODING BILL FROM $4,000 TO $700/MO. WITH KIMI RUNNING A 300-AGENT CODING FLOOR, HE STOPPED PAYING CLAUDE TO DO EVERYTHING kimi does the cheap heavy lifting. it can spin up hundreds of agents, push through thousands of steps, write the rough code, expand files, draft tests and handle the repetitive work that burns the most tokens opus 4.8 only comes in where the money is worth spending. first to plan the spec and define the rules, then again to tear apart the output, catch weak logic and flag the bugs that a fast swarm can miss that is what changed the economics. kimi handled the bulk of the volume for a fraction of the price, while opus stayed in the loop as the architect and the reviewer instead of the full-time builder most people still use one model for every step and wonder why their costs explode. this guy split the jobs properly. kimi runs wide and cheap. opus goes deep and skeptical. one builds fast, the other makes sure it should ship the real edge is not finding one perfect model. it is knowing where expensive intelligence actually matters and where cheap parallel output is already enough. that is how a $4,000 workflow turns into a $700 system

Gipp 🦅

16,989 görüntüleme • 3 ay önce

Jev founder, Diogo Almeida, just put out a PDF on building a Jev harness for coding agents the claim: 200x faster, 400x cheaper the model stopped being the bottleneck a while ago. the harness around it is where the cost and the speed actually live five decisions sit on every loop, and only one of them writes code hand this PDF and the article below to your Claude Code or Codex instance and let it rebuild its own setup your agent gets a better harness tonight, and monday looks different than it would have 👇
0:23

Jev founder, Diogo Almeida, just put out a PDF on building a Jev harness for coding agents the claim: 200x faster, 400x cheaper the model stopped being the bottleneck a while ago. the harness around it is where the cost and the speed actually live five decisions sit on every loop, and only one of them writes code hand this PDF and the article below to your Claude Code or Codex instance and let it rebuild its own setup your agent gets a better harness tonight, and monday looks different than it would have 👇

Hanako

37,887 görüntüleme • 5 gün önce

How to cut your AI bill by 60% switching to Opus 5.5: Most people will swap the model name, save 24%, and stop there. The other 37% is sitting in your settings. Here's the real before and after on an example agent workload. One month: 100M input tokens (80M cached reads, 5M cache writes, 15M uncached) 10M output tokens BEFORE: Opus 5 Cache reads: 80M × $0.50 = $40 Cache writes: 5M × $6.25 = $31.25 Uncached input: 15M × $5 = $75 Output: 10M × $25 = $250 Total: $396.25 STEP 1. Just switch the model. Same tokens, new prices. Cache reads $0.20. Writes $5. Input $4. Output $20. $16 + $25 + $60 + $200 = $301 24% cheaper. That's what everyone's screenshotting. STEP 2. Let it write less. Box measured Opus 5.5 at 40% less verbose with no drop in accuracy. 10M output tokens becomes 6M. Output drops from $200 to $120. Total: $221. Now you're at 44% off. STEP 3. Stop running every call at max effort. Thinking can't be switched off on 5.5 anymore, so effort is your lever. Classifying, routing, formatting, summarizing? Drop the effort. Save the high settings for the calls that actually reason. Say that trims output another 25%, 6M down to 4.5M. Output: $90. Total: $191. 52% off. STEP 4. Cache the stuff you keep resending. This is the one nobody does. Cache reads went from $0.50 to $0.20. That's 60% off the cheapest line on your bill. Move your system prompt, tool definitions and repo context into the cache. Uncached input drops from 15M to 5M, cache reads go up to 90M. $18 + $25 + $20 + $90 = $153 AFTER: $153 From $396.25. 61% cheaper. Same work. The model gave you 24%. You gave yourself the other 37%. Anthropic's own number is 40% cheaper than Opus 5 on typical workloads. Your number depends on how much of your bill is output and how much of your prompt you're resending uncached every call. So check those two first. Bookmark this for when you migrate. follow CyrilXBT
0:40

How to cut your AI bill by 60% switching to Opus 5.5: Most people will swap the model name, save 24%, and stop there. The other 37% is sitting in your settings. Here's the real before and after on an example agent workload. One month: 100M input tokens (80M cached reads, 5M cache writes, 15M uncached) 10M output tokens BEFORE: Opus 5 Cache reads: 80M × $0.50 = $40 Cache writes: 5M × $6.25 = $31.25 Uncached input: 15M × $5 = $75 Output: 10M × $25 = $250 Total: $396.25 STEP 1. Just switch the model. Same tokens, new prices. Cache reads $0.20. Writes $5. Input $4. Output $20. $16 + $25 + $60 + $200 = $301 24% cheaper. That's what everyone's screenshotting. STEP 2. Let it write less. Box measured Opus 5.5 at 40% less verbose with no drop in accuracy. 10M output tokens becomes 6M. Output drops from $200 to $120. Total: $221. Now you're at 44% off. STEP 3. Stop running every call at max effort. Thinking can't be switched off on 5.5 anymore, so effort is your lever. Classifying, routing, formatting, summarizing? Drop the effort. Save the high settings for the calls that actually reason. Say that trims output another 25%, 6M down to 4.5M. Output: $90. Total: $191. 52% off. STEP 4. Cache the stuff you keep resending. This is the one nobody does. Cache reads went from $0.50 to $0.20. That's 60% off the cheapest line on your bill. Move your system prompt, tool definitions and repo context into the cache. Uncached input drops from 15M to 5M, cache reads go up to 90M. $18 + $25 + $20 + $90 = $153 AFTER: $153 From $396.25. 61% cheaper. Same work. The model gave you 24%. You gave yourself the other 37%. Anthropic's own number is 40% cheaper than Opus 5 on typical workloads. Your number depends on how much of your bill is output and how much of your prompt you're resending uncached every call. So check those two first. Bookmark this for when you migrate. follow CyrilXBT

CyrilXBT

15,803 görüntüleme • 6 gün önce

Jev is INSANE. 🤯 in 24.9 seconds it read 384 news from this morning and told 15 brands which stories to hop onto today, for $0.19. Claude Opus 5, running on the same feed at the same time, got through 4/384 and cost $0.77. per headline that is ~390x cheaper, and the answer comes back before you finish reading the headline yourself. there's going to be so many ways for JEV to help you find trending stories, find journalists covering it, and get press coverage. everything in the video open-sourced here: (in the demo/ folder, together with 30+ skills to turn your agent into a PR team)
0:28

Jev is INSANE. 🤯 in 24.9 seconds it read 384 news from this morning and told 15 brands which stories to hop onto today, for $0.19. Claude Opus 5, running on the same feed at the same time, got through 4/384 and cost $0.77. per headline that is ~390x cheaper, and the answer comes back before you finish reading the headline yourself. there's going to be so many ways for JEV to help you find trending stories, find journalists covering it, and get press coverage. everything in the video open-sourced here: (in the demo/ folder, together with 30+ skills to turn your agent into a PR team)

Elvis

668,470 görüntüleme • 11 gün önce

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.
3:06

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

The Startup Ideas Podcast (SIP) 🧃

17,326 görüntüleme • 15 gün önce

We just launched Agentsky AgentSky, world’s 1st Agent Market! OpenRouter is for models. AgentSky is for agents. Use 40+ agents—Claude Code, Codex, OpenCode, Hermes, Pi in your browser(even your phone!) or via one API. All without installing or setting up anything. Hit Codex Astra’s weekly limit? Hand off to another agent such as OpenCode + DeepSeek V4.1 in browser without losing any context. You can compare any agent + model directly in browser and that's how I found Astra costs $5.3 while deepseek v4.1 cost $0.12 on the same dashboard task. (I actually preferred deepseek) Try it at If you can try any agent easily without install, which agent do you want to try next? Type the agent name and I will give $20 credit (you can use it for any model)
1:17

We just launched Agentsky AgentSky, world’s 1st Agent Market! OpenRouter is for models. AgentSky is for agents. Use 40+ agents—Claude Code, Codex, OpenCode, Hermes, Pi in your browser(even your phone!) or via one API. All without installing or setting up anything. Hit Codex Astra’s weekly limit? Hand off to another agent such as OpenCode + DeepSeek V4.1 in browser without losing any context. You can compare any agent + model directly in browser and that's how I found Astra costs $5.3 while deepseek v4.1 cost $0.12 on the same dashboard task. (I actually preferred deepseek) Try it at If you can try any agent easily without install, which agent do you want to try next? Type the agent name and I will give $20 credit (you can use it for any model)

Xiaoyin Qu

2,707,931 görüntüleme • 11 gün önce

jev + opus 5.5 is one of those setups that makes agent architecture feel weirdly overcomplicated in hindsight. the useful split isn’t “small model vs big model.” it’s deciding which calls actually need generation at all. → jev routes the next worker → scores which context is worth keeping → catches repeated actions before they burn the run → gates risky tool calls and sends uncertainty to review opus still owns the expensive part: planning, writing, coding, synthesis. jev sits around it as the decision layer. that matters because a typical loop can have 11 decision points but only 2 real generation calls. once those are separated, latency and cost stop scaling with every tiny fork in the workflow.
0:24

jev + opus 5.5 is one of those setups that makes agent architecture feel weirdly overcomplicated in hindsight. the useful split isn’t “small model vs big model.” it’s deciding which calls actually need generation at all. → jev routes the next worker → scores which context is worth keeping → catches repeated actions before they burn the run → gates risky tool calls and sends uncertainty to review opus still owns the expensive part: planning, writing, coding, synthesis. jev sits around it as the decision layer. that matters because a typical loop can have 11 decision points but only 2 real generation calls. once those are separated, latency and cost stop scaling with every tiny fork in the workflow.

Gipp 🦅

50,490 görüntüleme • 3 gün önce

This is the best way to use Claude Fable in Claude Code without immediately hitting your limits. 1. Model set to Fable 5 2. Reasoning on Max 3. Instruct Claude to run a dynamic workflow where: 3a. Fable is the orchestrator 3b. Opus does the reasoning heavy phases Fable is so overpowered that you don't need its intelligence for every step. Let it orchestrate Opus or even Sonnet.
0:24

This is the best way to use Claude Fable in Claude Code without immediately hitting your limits. 1. Model set to Fable 5 2. Reasoning on Max 3. Instruct Claude to run a dynamic workflow where: 3a. Fable is the orchestrator 3b. Opus does the reasoning heavy phases Fable is so overpowered that you don't need its intelligence for every step. Let it orchestrate Opus or even Sonnet.

Dan McAteer

911,772 görüntüleme • 3 ay önce