Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

ANOLISA (Alibaba Cloud Linux 4 Agentic Edition) is an agent-first operating system designed for AI Agents. Tokenless is its context-efficiency layer — stripping redundant tool outputs at the OS level before they hit the model. No framework changes. Tested with Claude Code — same workflow, fewer tokens. How it... show more

Alibaba Cloud

1,194,739 subscribers

16,443 görüntüleme • 24 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Most discussions around Claude Code focus on model quality or capability. But when you actually use it, the friction shows up earlier, more at the system level than the model itself. Token limits get the blame, but a lot of it comes from inefficient sessions: repeated context, extra tool calls, and small loops that quietly stack up. So it starts to feel less like “is the model good enough?” and more like “is the workflow slowing it down?” That’s where WozCode comes in. It helps streamline sessions, less repetition, smarter batching of tool calls, and tighter context usage so you can actually get more work done within the same limits. Woz just launched on Product Hunt. If Claude Code felt a bit restrictive before, it’s worth trying again with a cleaner workflow setup. Same model. Smoother execution. Upvote here:

Most discussions around Claude Code focus on model quality or capability. But when you actually use it, the friction shows up earlier, more at the system level than the model itself. Token limits get the blame, but a lot of it comes from inefficient sessions: repeated context, extra tool calls, and small loops that quietly stack up. So it starts to feel less like “is the model good enough?” and more like “is the workflow slowing it down?” That’s where WozCode comes in. It helps streamline sessions, less repetition, smarter batching of tool calls, and tighter context usage so you can actually get more work done within the same limits. Woz just launched on Product Hunt. If Claude Code felt a bit restrictive before, it’s worth trying again with a cleaner workflow setup. Same model. Smoother execution. Upvote here:

Parul Gautam

15,079 görüntüleme • 4 ay önce

Agent Zero crushed Codex by 2.6× on token efficiency! We gave both agents the same task on the same local model (Qwen3.6 27B): build a retro Q*bert arcade game. Each agent wrote and rewrote it across iterations, adding enemies and a HUD. Outputs: • Agent Zero: 239K tokens, 53 min • Codex: 627K tokens, 51 min Both agents built a working Q*bert, but GitLawb 's Agent Zero is the cleaner build, with crisper textures and hops that land where they should. Codex refills the context window with its whole history every turn, so the model loses the thread and hallucinates code it never wrote. Agent Zero sends only what's new, so it keeps more of the window open and makes fewer mistakes. Run agents on local AI models in Atomic Chat!

Agent Zero crushed Codex by 2.6× on token efficiency! We gave both agents the same task on the same local model (Qwen3.6 27B): build a retro Qbert arcade game. Each agent wrote and rewrote it across iterations, adding enemies and a HUD. Outputs: • Agent Zero: 239K tokens, 53 min • Codex: 627K tokens, 51 min Both agents built a working Qbert, but GitLawb 's Agent Zero is the cleaner build, with crisper textures and hops that land where they should. Codex refills the context window with its whole history every turn, so the model loses the thread and hallucinates code it never wrote. Agent Zero sends only what's new, so it keeps more of the window open and makes fewer mistakes. Run agents on local AI models in Atomic Chat!

atomic.chat

320,187 görüntüleme • 1 ay önce

Claude Science just CHANGED how AI is used in research Anthropic didn't launch a new model they launched an AI-native scientific workspace Claude Science lets researchers: > analyze hundreds of papers at once > run Python, R & Jupyter notebooks > work with genomics, proteomics & molecular data > generate figures, charts & publication-ready outputs > keep a full reproducible audit trail this isn't about making the LLM smarter it's about building the workflow around it first we got Claude Code for developers now we have Claude Science for researchers the AI race is shifting it's no longer just who has the best model it's who builds the best AI operating system for every profession coding was first science is next

Claude Science just CHANGED how AI is used in research Anthropic didn't launch a new model they launched an AI-native scientific workspace Claude Science lets researchers: > analyze hundreds of papers at once > run Python, R & Jupyter notebooks > work with genomics, proteomics & molecular data > generate figures, charts & publication-ready outputs > keep a full reproducible audit trail this isn't about making the LLM smarter it's about building the workflow around it first we got Claude Code for developers now we have Claude Science for researchers the AI race is shifting it's no longer just who has the best model it's who builds the best AI operating system for every profession coding was first science is next

hammertime

19,976 görüntüleme • 2 ay önce

I cant believe this guy just made a permanent solution to context bloat and open sourced it all! when we tested this tool (Context+) for solving an issue on the OpenCode repository, the agent using this tool used ~6.5k fewer tokens, found the code and fixed it in half the time! the results were surprising: 6 to 10k tokens saved per prompt, completed task in ~2 minutes while the agent running without the tool took ~4 mins for the same and got stuck in loops bro built an entire beast by using all the modern tools that we could think of: undo trees, semantic search by meaning (by haskellforall), advanced refactoring, blast radius, advanced file context trees, restore points... i can keep going on semantic code search and context trees are the future of agentic coding and this tool proves it the feature i loved the most is semantic search and how it gets things done 2x faster with least possible tokens it makes an agent that actually knows what it’s doing and not just guessing, it makes meaning from your code similar to RAG. if you aren't optimizing your context, you are just burning money the developer says this tool is still under development, it can have unexpected behavior and the docs need updates but the video shows the reality of how fast it can be github: get here:

I cant believe this guy just made a permanent solution to context bloat and open sourced it all! when we tested this tool (Context+) for solving an issue on the OpenCode repository, the agent using this tool used ~6.5k fewer tokens, found the code and fixed it in half the time! the results were surprising: 6 to 10k tokens saved per prompt, completed task in ~2 minutes while the agent running without the tool took ~4 mins for the same and got stuck in loops bro built an entire beast by using all the modern tools that we could think of: undo trees, semantic search by meaning (by haskellforall), advanced refactoring, blast radius, advanced file context trees, restore points... i can keep going on semantic code search and context trees are the future of agentic coding and this tool proves it the feature i loved the most is semantic search and how it gets things done 2x faster with least possible tokens it makes an agent that actually knows what it’s doing and not just guessing, it makes meaning from your code similar to RAG. if you aren't optimizing your context, you are just burning money the developer says this tool is still under development, it can have unexpected behavior and the docs need updates but the video shows the reality of how fast it can be github: get here:

forloop

226,271 görüntüleme • 6 ay önce

HERMES AGENT NOW RUNS ON AN 8GB LAPTOP GPU JUST AS EASILY AS IT RUNS ON A 128GB MINI PC Nous Research shipped the official Hermes Agent Desktop App this week. Someone pointed it at a local llama server running on an RTX 4060 with 16GB system RAM. The integration took two minutes The model behind it: Gemma 4 26B MoE, QAT quantized, running on 8GB of VRAM. A 60k token prompt held a stable 20 tokens a second, flat, no slowdown as context grew. The flags were nothing exotic, just -cmoe -c 248000 on llama.cpp What that 8GB setup does out of the box: reads and patches its own code, runs it in a terminal, debugs errors, manages GitHub repos, spawns sub-agents for parallel work. Browses the web with vision to debug a UI. Schedules cron jobs in plain language. Connects to Notion, Google Workspace, Linear, and Obsidian to manage tasks on its own That's the same agent layer running on a Minisforum MS-S1 MAX with 128GB of unified memory, 96GB of it to the GPU, holding a 120B model at 56 tokens a second instead of a 26B model at 20. Same software, same tool execution, same zero API key. The only thing that changes between an $800 laptop and a $2,000 mini PC is how big a model you can afford to run underneath it The barrier to running a real autonomous agent locally didn't just drop. It dropped all the way down to hardware most people already own

HERMES AGENT NOW RUNS ON AN 8GB LAPTOP GPU JUST AS EASILY AS IT RUNS ON A 128GB MINI PC Nous Research shipped the official Hermes Agent Desktop App this week. Someone pointed it at a local llama server running on an RTX 4060 with 16GB system RAM. The integration took two minutes The model behind it: Gemma 4 26B MoE, QAT quantized, running on 8GB of VRAM. A 60k token prompt held a stable 20 tokens a second, flat, no slowdown as context grew. The flags were nothing exotic, just -cmoe -c 248000 on llama.cpp What that 8GB setup does out of the box: reads and patches its own code, runs it in a terminal, debugs errors, manages GitHub repos, spawns sub-agents for parallel work. Browses the web with vision to debug a UI. Schedules cron jobs in plain language. Connects to Notion, Google Workspace, Linear, and Obsidian to manage tasks on its own That's the same agent layer running on a Minisforum MS-S1 MAX with 128GB of unified memory, 96GB of it to the GPU, holding a 120B model at 56 tokens a second instead of a 26B model at 20. Same software, same tool execution, same zero API key. The only thing that changes between an $800 laptop and a $2,000 mini PC is how big a model you can afford to run underneath it The barrier to running a real autonomous agent locally didn't just drop. It dropped all the way down to hardware most people already own

NO1ennn

40,079 görüntüleme • 2 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.

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 • 29 gün önce

Alibaba just dropped a free AI that codes like a $150/hr developer. And it runs on your laptop. Qwen 3 Coder Next has 80 billion parameters but only uses 3 billion at a time. So you get massive model power with tiny model speed. The real kicker? It handles 256,000 tokens of context. That's your entire codebase. Every file. All at once. People are building 2D games in seconds. Full IDE integrations that write, test, and fix code automatically. Custom business tools without hiring devs. It works with OpenClaw, Claude Code, and every major coding tool. No complicated setup. Just download and go. Completely open source. Zero API queues. You own it. Your competitors are using this right now.

Alibaba just dropped a free AI that codes like a $150/hr developer. And it runs on your laptop. Qwen 3 Coder Next has 80 billion parameters but only uses 3 billion at a time. So you get massive model power with tiny model speed. The real kicker? It handles 256,000 tokens of context. That's your entire codebase. Every file. All at once. People are building 2D games in seconds. Full IDE integrations that write, test, and fix code automatically. Custom business tools without hiring devs. It works with OpenClaw, Claude Code, and every major coding tool. No complicated setup. Just download and go. Completely open source. Zero API queues. You own it. Your competitors are using this right now.

Julian Goldie SEO

30,284 görüntüleme • 7 ay önce

Okay, this is the first AI content setup I've seen that actually closes the loop. Sabrina Ramonov (founder of Blotato) runs all her content solo, and her Claude agent is pulling 41M cross-platform views in 30 days. She went 0 to 3M followers in 2 years on $0 ads. Most AI content tools stop at "here's your draft." You still grade it, schedule it, and publish it by hand. Here's her full setup: → connect Claude to Blotato → install 7 free Claude skills (open sourced, no email gate) → write, grade, and schedule your first post from the same agent The skills do the real work: content-coach, post-writer, post-grader, viral-hooks, repurpose, brand-brief, post-scheduler. What sold me: it's built for agents. Blotato ships an LLM-readable API spec, so Claude Code, Codex, or Hermes can run the whole thing end to end. She breaks down the exact system in the piece. Worth the full read. (clip attached is a Claude Code agent-workflow talk worth watching alongside this.)

Prajwal Tomar

142,173 görüntüleme • 1 ay önce

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

13,598 görüntüleme • 3 ay önce

over the labor day weekend i built out an app to analyze my twitter mutuals, using my Hyperspace agentic-os prototype. this is likely the most powerful agentic-os setup every assembled. this goes beyond a single model, or agent, or data source or a single smart CLI tool. this goes beyond hardware, or cloud or distributed networks. it is all of it, combined. the LLM OS is here, Andrej Karpathy. and this combined environment enabled me to build an app I craved for all these years, without writing a single line of code, saving me 150 hours of development work effort. i now have a deep understanding of my twitter mutuals here - and to construct the app - my agentic-os utilized multiple models including Grok Code, GPT-OSS-120B running locally, Qwen2.5 Coder and Google's Nano Banana, multiple orchestrators include Claude Code, 24 AI agents, several MCPs, and specific data from my Twitter archive which I plugged in and other data which it researched, analyzed and aggregated into helping me understand my network here. consider again: the absolute best work from all the top AI firms - all of it, in one actually-useful-integrated-environment. RT if you want this as well. any feature requests ? eg show when a mutual is in the same city in the future.. will DM with access.. this is madness, but it is here 🤖🔥

over the labor day weekend i built out an app to analyze my twitter mutuals, using my Hyperspace agentic-os prototype. this is likely the most powerful agentic-os setup every assembled. this goes beyond a single model, or agent, or data source or a single smart CLI tool. this goes beyond hardware, or cloud or distributed networks. it is all of it, combined. the LLM OS is here, Andrej Karpathy. and this combined environment enabled me to build an app I craved for all these years, without writing a single line of code, saving me 150 hours of development work effort. i now have a deep understanding of my twitter mutuals here - and to construct the app - my agentic-os utilized multiple models including Grok Code, GPT-OSS-120B running locally, Qwen2.5 Coder and Google's Nano Banana, multiple orchestrators include Claude Code, 24 AI agents, several MCPs, and specific data from my Twitter archive which I plugged in and other data which it researched, analyzed and aggregated into helping me understand my network here. consider again: the absolute best work from all the top AI firms - all of it, in one actually-useful-integrated-environment. RT if you want this as well. any feature requests ? eg show when a mutual is in the same city in the future.. will DM with access.. this is madness, but it is here 🤖🔥

Varun

22,220 görüntüleme • 1 yıl önce

I cut Fable 5 token usage 2.5x with just one change! - Before: 5.5 M tokens · 7 errors · $8.94 - After: 2.3 M tokens · 0 errors · $4.17 The final build was the same for both, but the path the agent took wildly differed. In both runs, the agent started with the same thing, i.e., it understood the backend before building anything, like: - Permission policies - Available storage buckets - Auth providers configured - How edge functions are deployed The first run used Firebase, which was built for a human dev using a dashboard. While the dev can read the above state by clicking through tabs, an agent has no dashboard. So it gathered the same info through API calls. And there's no single Firebase call that returned this info. The agent required to query multiple times, and each query over-returned. For instance, when the agent asked how sign-in is configured, Firebase also returned the entire auth surface and every method it supported. This was far more context than what it needed. And it repeated across every part of the backend it inspected. Some states (like which auth providers are active) weren't queryable at all. I provided it myself. Otherwise, the agent would have guessed. Errors further compounded the token usage. When a dev sees "permission denied," they can look at the console and figure out whether it's a rule, a path, or an unauthenticated request. Firebase returned the same string to the agent as well, and it had none of that surrounding context to debug. So it guessed again, picked the most likely cause, and rewrote code, utilizing more tokens. This Firebase setup cost me 5.5M tokens and 7 manual interventions during errors on a full-stack RAG app. But I brought that down to 2.3M tokens and 0 manual interventions by using InsForge as the backend context engineering layer (open-source and self-hostable via Docker). It provides the same primitives as Supabase/Firebase, but structures the entire information layer for agents, instead of dashboards. In one CLI call that consumed ~500 tokens, the agent saw the full backend topology before writing a single line of code. This included auth, database, storage, edge functions, model gateway, micro VMs, and deployment. Also, instead of loading the entire product surface into context on every task, four narrowly scoped skills activated only when relevant to keep cognitive load minimal. And to ensure efficient retries if needed, every CLI operation returned structured JSON with meaningful exit codes, so the agent never guessed what to do next. Here's the InsForge GitHub Repo: (don't forget to star it ⭐) The video below depicts the final build, comparing Firebase and InsForge. To dive deeper, I recently published a full walkthrough building the same RAG app on both backends and inspected them end-to-end. Read it below.

I cut Fable 5 token usage 2.5x with just one change! - Before: 5.5 M tokens · 7 errors · $8.94 - After: 2.3 M tokens · 0 errors · $4.17 The final build was the same for both, but the path the agent took wildly differed. In both runs, the agent started with the same thing, i.e., it understood the backend before building anything, like: - Permission policies - Available storage buckets - Auth providers configured - How edge functions are deployed The first run used Firebase, which was built for a human dev using a dashboard. While the dev can read the above state by clicking through tabs, an agent has no dashboard. So it gathered the same info through API calls. And there's no single Firebase call that returned this info. The agent required to query multiple times, and each query over-returned. For instance, when the agent asked how sign-in is configured, Firebase also returned the entire auth surface and every method it supported. This was far more context than what it needed. And it repeated across every part of the backend it inspected. Some states (like which auth providers are active) weren't queryable at all. I provided it myself. Otherwise, the agent would have guessed. Errors further compounded the token usage. When a dev sees "permission denied," they can look at the console and figure out whether it's a rule, a path, or an unauthenticated request. Firebase returned the same string to the agent as well, and it had none of that surrounding context to debug. So it guessed again, picked the most likely cause, and rewrote code, utilizing more tokens. This Firebase setup cost me 5.5M tokens and 7 manual interventions during errors on a full-stack RAG app. But I brought that down to 2.3M tokens and 0 manual interventions by using InsForge as the backend context engineering layer (open-source and self-hostable via Docker). It provides the same primitives as Supabase/Firebase, but structures the entire information layer for agents, instead of dashboards. In one CLI call that consumed ~500 tokens, the agent saw the full backend topology before writing a single line of code. This included auth, database, storage, edge functions, model gateway, micro VMs, and deployment. Also, instead of loading the entire product surface into context on every task, four narrowly scoped skills activated only when relevant to keep cognitive load minimal. And to ensure efficient retries if needed, every CLI operation returned structured JSON with meaningful exit codes, so the agent never guessed what to do next. Here's the InsForge GitHub Repo: (don't forget to star it ⭐) The video below depicts the final build, comparing Firebase and InsForge. To dive deeper, I recently published a full walkthrough building the same RAG app on both backends and inspected them end-to-end. Read it below.

Avi Chawla

113,219 görüntüleme • 3 ay önce

i been running Qwen3.5-35B-A3B UD-Q4_K_XL through Claude Code since llama.cpp merged the Anthropic endpoint. configured it in minutes. everything was great. projects grew from single scripts to multifile systems with 8 modules and 3,000+ lines. then the chains started breaking. 3 to 5 minutes of pure autonomy and suddenly it stops. tool call fails. reprompt. it recovers. 2 minutes later it stops again. the model is fine. the harness is the bottleneck. saw a comment suggesting OpenCode. installed it. pointed it at the same localhost endpoint running the same model on the same GPU. the game is different. instead of stopping on a bad tool call it just keeps going. on wrong read it adjusts. if file not found it retries. the flow is unbroken. i watched it plan a refactor across 8 files, read every module, and start building without a single pause. in Claude Code that same task would have stopped 4 times. the tradeoff is sometimes it loops. same tool call repeated because the model loses track of what it already read. but here is the thing. i choose loops over pauses. a loop you can interrupt and redirect. a broken chain stops the flow and you have to reprompt to get it moving again. someone is solving this at the core level and i have a feeling it is the open source community. the fact that i can run this level of autonomous coding intelligence on a single consumer GPU with 24gb VRAM at 112 tokens per second. respect to the chinese labs. respect to the open source builders making this possible.

i been running Qwen3.5-35B-A3B UD-Q4_K_XL through Claude Code since llama.cpp merged the Anthropic endpoint. configured it in minutes. everything was great. projects grew from single scripts to multifile systems with 8 modules and 3,000+ lines. then the chains started breaking. 3 to 5 minutes of pure autonomy and suddenly it stops. tool call fails. reprompt. it recovers. 2 minutes later it stops again. the model is fine. the harness is the bottleneck. saw a comment suggesting OpenCode. installed it. pointed it at the same localhost endpoint running the same model on the same GPU. the game is different. instead of stopping on a bad tool call it just keeps going. on wrong read it adjusts. if file not found it retries. the flow is unbroken. i watched it plan a refactor across 8 files, read every module, and start building without a single pause. in Claude Code that same task would have stopped 4 times. the tradeoff is sometimes it loops. same tool call repeated because the model loses track of what it already read. but here is the thing. i choose loops over pauses. a loop you can interrupt and redirect. a broken chain stops the flow and you have to reprompt to get it moving again. someone is solving this at the core level and i have a feeling it is the open source community. the fact that i can run this level of autonomous coding intelligence on a single consumer GPU with 24gb VRAM at 112 tokens per second. respect to the chinese labs. respect to the open source builders making this possible.

Sudo su

67,104 görüntüleme • 6 ay önce

single RTX 3090. 24 GB VRAM. Qwen3.5-35B-A3B. 4-bit quant, 113 tokens per second at full 262K context harnessing Claude Code locally with no API, no subscription, no proxy. told it what it is. 30 Mamba2 layers, 10 attention, 256 experts, 8 active per token. said "build something that shows off what you can do." it visualized its own architecture. interactive. tokens flowing through layers. 256 experts lighting up on routing. served in the browser from the same GPU running inference. single prompt. then i said level up. 3D. Three.js. separate files. flythrough camera. clickable layers. it planned first, scaffolded 6 files, hit one API bug, fixed it itself, then optimized for smooth framerate. two iterations to a working 3D neural network explorer. llama.cpp just merged a native Anthropic endpoint. Claude Code points at localhost. the whole setup is two commands. no LiteLLM. no proxy config. the open source models coming out of china right now are genuinely changing what's possible on consumer hardware. respect to the Qwen team. this is acceleration.

single RTX 3090. 24 GB VRAM. Qwen3.5-35B-A3B. 4-bit quant, 113 tokens per second at full 262K context harnessing Claude Code locally with no API, no subscription, no proxy. told it what it is. 30 Mamba2 layers, 10 attention, 256 experts, 8 active per token. said "build something that shows off what you can do." it visualized its own architecture. interactive. tokens flowing through layers. 256 experts lighting up on routing. served in the browser from the same GPU running inference. single prompt. then i said level up. 3D. Three.js. separate files. flythrough camera. clickable layers. it planned first, scaffolded 6 files, hit one API bug, fixed it itself, then optimized for smooth framerate. two iterations to a working 3D neural network explorer. llama.cpp just merged a native Anthropic endpoint. Claude Code points at localhost. the whole setup is two commands. no LiteLLM. no proxy config. the open source models coming out of china right now are genuinely changing what's possible on consumer hardware. respect to the Qwen team. this is acceleration.

Sudo su

110,206 görüntüleme • 6 ay önce

MIT PhD student Alex Zhang reveals the scaling result where a model trained on short tasks generalizes to problems 100x longer for free: "If you're very clever about the design of your harness or how you use the language model, you can almost get scaling gains for free." "If you train a model naively, there's no tricks. It's just the same way you train a model on these RL environments. You just roll it out, and then you just get some reward." "If you train it on only short tasks, like only tasks that are 10,000 tokens long, and then you were to run it on a similar domain, but at a million tokens, or 10 million tokens, or 100,000 tokens, it generalizes really, really well. If you look at it compared to even the base transformer, you get way better generalization properties." "When the model uses an RLM (Recursive Language Model) after it's trained on these short tasks, it will see some kind of trajectory of actions that it does. Between these two problems of different lengths, the RLM learns to see them as almost the same problem." "Token for token, they're almost the same. You can describe it in code. In one code setting, maybe the for loop is a little bigger, but it's the same kind of code and it derives the constants from the data. There's no hard coding, so they literally look the same." alex zhang

MIT PhD student Alex Zhang reveals the scaling result where a model trained on short tasks generalizes to problems 100x longer for free: "If you're very clever about the design of your harness or how you use the language model, you can almost get scaling gains for free." "If you train a model naively, there's no tricks. It's just the same way you train a model on these RL environments. You just roll it out, and then you just get some reward." "If you train it on only short tasks, like only tasks that are 10,000 tokens long, and then you were to run it on a similar domain, but at a million tokens, or 10 million tokens, or 100,000 tokens, it generalizes really, really well. If you look at it compared to even the base transformer, you get way better generalization properties." "When the model uses an RLM (Recursive Language Model) after it's trained on these short tasks, it will see some kind of trajectory of actions that it does. Between these two problems of different lengths, the RLM learns to see them as almost the same problem." "Token for token, they're almost the same. You can describe it in code. In one code setting, maybe the for loop is a little bigger, but it's the same kind of code and it derives the constants from the data. There's no hard coding, so they literally look the same." alex zhang

MTS

100,519 görüntüleme • 1 ay önce

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base

Malte Ubl

125,326 görüntüleme • 8 ay ö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

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

GREG ISENBERG

194,171 görüntüleme • 5 ay önce

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

THIS GUY SPENT 5 MINUTES SETTING UP A $20 CLAUDE WORKSPACE AND TURNED 30 MINUTES OF DAILY PROMPT CHAOS INTO A SYSTEM Most people open Claude, type 1 messy prompt, rewrite it 10 times, get the same generic answer and call the model “bad.” He opens Claude Cowork, adds the project rules, past context, working files, examples, decisions and a clean place for the model to remember what it is doing. Same Claude. Same $20 tool. Completely different output. The funny part is there is no magic prompt here. No secret template. No “10x Claude” trick. Just the boring layer Karpathy keeps pointing at: context, memory and structure before output. A setup like this can save 30 minutes a day, which is 15 hours a month. If you use Claude for client work at $50 to $100/hour, that is $750 to $1,500/month in time you stop burning on repeated prompts. The model is real. The output is real. The edge is in not making Claude start from zero every single time.

Gipp 🦅

14,871 görüntüleme • 3 ay önce

I got tired of explaining myself to AI every single day. Same context. Same workflow. Same instructions. Copy-pasted into every new session like it’s 2022. So I tried Panofy. Uploaded my own scripts and documents to train an agent — then gave it a single instruction. 🔥 It ran the task. Got it right. First time. No prompt loops. No setup. It just… knew. The thing that surprised me most? It actually improves the more you use it. Learns from mistakes. Builds memory. Adapts to how you think. Fewer tokens, better results. I’ve used a lot of AI tools. This one made me feel like I finally own mine. Panofy isn’t just another tool — it’s the best AI agent for expert-level tasks. If you’re serious about building with AI, this is worth trying. Sign up and get 10,000 free credits + 7-day Panofy Plus free trial 👉 #AI #AIAgents #Productivity

I got tired of explaining myself to AI every single day. Same context. Same workflow. Same instructions. Copy-pasted into every new session like it’s 2022. So I tried Panofy. Uploaded my own scripts and documents to train an agent — then gave it a single instruction. 🔥 It ran the task. Got it right. First time. No prompt loops. No setup. It just… knew. The thing that surprised me most? It actually improves the more you use it. Learns from mistakes. Builds memory. Adapts to how you think. Fewer tokens, better results. I’ve used a lot of AI tools. This one made me feel like I finally own mine. Panofy isn’t just another tool — it’s the best AI agent for expert-level tasks. If you’re serious about building with AI, this is worth trying. Sign up and get 10,000 free credits + 7-day Panofy Plus free trial 👉 #AI #AIAgents #Productivity

Aryan Rakib

33,551 görüntüleme • 4 ay önce

10 GitHub repos with ⭐ 450k+ combined stars that stop your agent from wasting tokens 1. caveman 98k⭐ - makes your AI agent talk like a caveman. Same answers, 65% fewer output tokens. 2. rtk 76k⭐ - CLI proxy that filters git/test/docker output before it hits your context. Up to 90% less bash noise. 3. mem0 63k⭐ - memory layer for AI agents. Stops your agent from re-explaining the same context every session. 4. context7 60.7k⭐ - pulls exact, up-to-date docs into context instead of your agent guessing and burning tokens on retries. 5. aider 48k⭐ - builds a map of your repo instead of loading the whole codebase into context. 6. code-review-graph 30k⭐ - graphs your codebase so your agent reads 2-3 files instead of the whole repo. Up to 376x fewer tokens per question. 7. serena 28k⭐ - gives agents symbol-level code access instead of reading full files line by line. 8. repomix 28k⭐ - compresses your entire repo into an AI-friendly format. ~70% token reduction. 9. ccusage 18k⭐ - shows you exactly where your Claude Code sessions are burning tokens. 10. GPTCache 8k⭐ - semantic cache for LLM calls. Stop paying twice for the same question. Save this before your next agent session burns through your subscription 👇

10 GitHub repos with ⭐ 450k+ combined stars that stop your agent from wasting tokens 1. caveman 98k⭐ - makes your AI agent talk like a caveman. Same answers, 65% fewer output tokens. 2. rtk 76k⭐ - CLI proxy that filters git/test/docker output before it hits your context. Up to 90% less bash noise. 3. mem0 63k⭐ - memory layer for AI agents. Stops your agent from re-explaining the same context every session. 4. context7 60.7k⭐ - pulls exact, up-to-date docs into context instead of your agent guessing and burning tokens on retries. 5. aider 48k⭐ - builds a map of your repo instead of loading the whole codebase into context. 6. code-review-graph 30k⭐ - graphs your codebase so your agent reads 2-3 files instead of the whole repo. Up to 376x fewer tokens per question. 7. serena 28k⭐ - gives agents symbol-level code access instead of reading full files line by line. 8. repomix 28k⭐ - compresses your entire repo into an AI-friendly format. ~70% token reduction. 9. ccusage 18k⭐ - shows you exactly where your Claude Code sessions are burning tokens. 10. GPTCache 8k⭐ - semantic cache for LLM calls. Stop paying twice for the same question. Save this before your next agent session burns through your subscription 👇

unicode

66,891 görüntüleme • 28 gün önce