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

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

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

На главную

Your coding agent can run commands, use tools, and touch your entire codebase And most of you have ZERO controls on it Harden AIF fixes that Local security model reviews every tool call in context and stops the unnecessary or risky ones before they execute Runs fully local Repo... show more

Hasan Toor

437,595 subscribers

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

Anya Rossi• Live Now

Private livecam show

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

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

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

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

Claude just solved one of AI coding’s biggest problems. 🤯 It can now turn your entire codebase into: → an interactive architecture map for humans → a memory system for AI agents So the next coding agent instantly understands your APIs, components, auth, DB flows, and dependencies. No more dropping AI into a random repo with zero context. Your codebase can literally explain itself now.

Claude just solved one of AI coding’s biggest problems. 🤯 It can now turn your entire codebase into: → an interactive architecture map for humans → a memory system for AI agents So the next coding agent instantly understands your APIs, components, auth, DB flows, and dependencies. No more dropping AI into a random repo with zero context. Your codebase can literally explain itself now.

Radha Tripathi

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

🤯 THIS FEELS ILLEGAL AND I LOVE IT. I found a personal AI assistant that actually runs on your computer 24/7 and gets smarter the more you use it. It is called Mercury. 100% FREE. Think of it like having a smart assistant who never forgets anything. Here is what it does: ↳ Remembers everything about you ↳ Asks before doing anything risky It will not run commands or touch your files without permission. You stay in control always. ↳ You can message it from anywhere ↳ Has 31 tools built in ↳ Protects your AI credits One command to install: npx @cosmicstack/mercury-agent 100% OpenSource. Works on Mac, Windows, and Linux.

🤯 THIS FEELS ILLEGAL AND I LOVE IT. I found a personal AI assistant that actually runs on your computer 24/7 and gets smarter the more you use it. It is called Mercury. 100% FREE. Think of it like having a smart assistant who never forgets anything. Here is what it does: ↳ Remembers everything about you ↳ Asks before doing anything risky It will not run commands or touch your files without permission. You stay in control always. ↳ You can message it from anywhere ↳ Has 31 tools built in ↳ Protects your AI credits One command to install: npx @cosmicstack/mercury-agent 100% OpenSource. Works on Mac, Windows, and Linux.

Kanika

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

I still think Hermes agent is the most slept-on AI tool of 2026. For literally $6/mo, you can launch multiple subagents that work for you 24/7. Most people don't know you can do this, but it's a complete game-changer. Instead of one Hermes assistant doing everything sequentially, you run specialized agents in parallel, each with its own job, its own context, and its own memory. Practical example: → Research agent: scans your watchlist and competitors overnight, delivers a morning brief → Content agent: drafts and schedules your posts based on what's trending in your niche → Ops agent: manages your inbox, flags anything urgent, drafts replies for your review All three can run simultaneously and improve over time. How to start: 1. Install Hermes Terminal command: curl -fsSL | bash (can also download desktop) 2. Prompting Simply tell Hermes directly: "I want to run separate subagents for [task 1], [task 2], and [task 3]. Set them up to run independently and report back to me." For the cheapest setup, you can use a $4/month VPS with Hostinger, plug in DeepSeek V4 Flash as your default model. There isn't another AI tool with this much value in 2026. Hermes is still so underrated.

I still think Hermes agent is the most slept-on AI tool of 2026. For literally $6/mo, you can launch multiple subagents that work for you 24/7. Most people don't know you can do this, but it's a complete game-changer. Instead of one Hermes assistant doing everything sequentially, you run specialized agents in parallel, each with its own job, its own context, and its own memory. Practical example: → Research agent: scans your watchlist and competitors overnight, delivers a morning brief → Content agent: drafts and schedules your posts based on what's trending in your niche → Ops agent: manages your inbox, flags anything urgent, drafts replies for your review All three can run simultaneously and improve over time. How to start: 1. Install Hermes Terminal command: curl -fsSL | bash (can also download desktop) 2. Prompting Simply tell Hermes directly: "I want to run separate subagents for [task 1], [task 2], and [task 3]. Set them up to run independently and report back to me." For the cheapest setup, you can use a $4/month VPS with Hostinger, plug in DeepSeek V4 Flash as your default model. There isn't another AI tool with this much value in 2026. Hermes is still so underrated.

Miles Deutscher

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

if you use claude code, this will save you real money. the problem: every time you make an edit, your ai rereads the whole codebase to figure out what changed. tens of thousands of tokens, every turn, for context it already had. this repo fixes it. it’s called code review graph, and it just maps your entire codebase: every file, every function, every connection laid out so you can see the actual shape of your project how to set up (2 min): 1. pip install code-review-graph 2. code-review-graph install - auto-configures Claude Code, Cursor, Codex, Gemini CLI + more 3. code-review-graph build change one function, and it traces exactly what that touches... every caller, every dependent file, every test. your ai only reads what's affected, not the whole repo. and the savings are wild. a task that used to burn ~100,000 tokens (about a dollar) now runs closer to a penny.

if you use claude code, this will save you real money. the problem: every time you make an edit, your ai rereads the whole codebase to figure out what changed. tens of thousands of tokens, every turn, for context it already had. this repo fixes it. it’s called code review graph, and it just maps your entire codebase: every file, every function, every connection laid out so you can see the actual shape of your project how to set up (2 min): 1. pip install code-review-graph 2. code-review-graph install - auto-configures Claude Code, Cursor, Codex, Gemini CLI + more 3. code-review-graph build change one function, and it traces exactly what that touches... every caller, every dependent file, every test. your ai only reads what's affected, not the whole repo. and the savings are wild. a task that used to burn ~100,000 tokens (about a dollar) now runs closer to a penny.

Alvaro Cintas

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

Alright, now that we know *what* an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Alright, now that we know what an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Google AI

22,487 просмотров • 9 месяцев назад

▣ Introducing Endless: infinite inference (kinda). An experimental harness to milk every ounce out of your Codex subscription. Since Codex can let an in-progress turn keep going even after your usage hits 100%, why not put that to the test? Endless starts one Codex turn and gives the agent a wait_for_user_input tool. Once it finishes a task, it calls that tool and waits. Your next message becomes the tool result, keeping the entire session inside the same turn. It runs through Codex’s own app server using your existing ChatGPT login. Native tools, automatic compaction, context tracking, and quota tracking still work as usual. ⚠️ NOTE: I CAN’T CONFIRM THAT YOU WON’T GET BANNED OR PUNISHED FOR USING THIS TOOL. USE IT AT YOUR OWN RISK.

▣ Introducing Endless: infinite inference (kinda). An experimental harness to milk every ounce out of your Codex subscription. Since Codex can let an in-progress turn keep going even after your usage hits 100%, why not put that to the test? Endless starts one Codex turn and gives the agent a wait_for_user_input tool. Once it finishes a task, it calls that tool and waits. Your next message becomes the tool result, keeping the entire session inside the same turn. It runs through Codex’s own app server using your existing ChatGPT login. Native tools, automatic compaction, context tracking, and quota tracking still work as usual. ⚠️ NOTE: I CAN’T CONFIRM THAT YOU WON’T GET BANNED OR PUNISHED FOR USING THIS TOOL. USE IT AT YOUR OWN RISK.

maria

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

holy sh*t xai basically built an app store for grok bot instead of hard-coding every workflow, this repo lets you keep adding new capabilities to grok through plugins and reusable integrations [official xai marketplace - 200+ stars] 1/ add new tools without rebuilding the agent 2/ plug in reusable workflows and commands 3/ extend grok with external services and dev tooling the interesting part is that grok bot stops being one fixed assistant and turns into something you can keep upgrading around your own workflow this is probably the repo to study if you want to build on top of grok instead of just prompting it

holy sh*t xai basically built an app store for grok bot instead of hard-coding every workflow, this repo lets you keep adding new capabilities to grok through plugins and reusable integrations [official xai marketplace - 200+ stars] 1/ add new tools without rebuilding the agent 2/ plug in reusable workflows and commands 3/ extend grok with external services and dev tooling the interesting part is that grok bot stops being one fixed assistant and turns into something you can keep upgrading around your own workflow this is probably the repo to study if you want to build on top of grok instead of just prompting it

Gipp 🦅

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

let me save you 3 hours of head scratching. if you're running local models like Qwen3.5-35B-A3B through Claude Code via llama.cpp's Anthropic endpoint, the chain will break every 3 to 5 minutes. tool call fails. flow stops. you reprompt. it recovers. 2 minutes later it stops again. the model is fine. the harness chokes on local inference latency. switch to OpenCode. same localhost endpoint. same model. same GPU. the chain doesn't break. the tradeoff: OpenCode sometimes loops. the model forgets what it already read and repeats the same tool call. but a loop you can interrupt. a broken chain kills your momentum and you start over. watch both side by side. proprietary agent vs open source agent. same 3B model. different failure modes. pick your poison.

let me save you 3 hours of head scratching. if you're running local models like Qwen3.5-35B-A3B through Claude Code via llama.cpp's Anthropic endpoint, the chain will break every 3 to 5 minutes. tool call fails. flow stops. you reprompt. it recovers. 2 minutes later it stops again. the model is fine. the harness chokes on local inference latency. switch to OpenCode. same localhost endpoint. same model. same GPU. the chain doesn't break. the tradeoff: OpenCode sometimes loops. the model forgets what it already read and repeats the same tool call. but a loop you can interrupt. a broken chain kills your momentum and you start over. watch both side by side. proprietary agent vs open source agent. same 3B model. different failure modes. pick your poison.

Sudo su

72,554 просмотров • 6 месяцев назад

CODEX SKILL THAT STOPS WASTING YOUR CODEX USAGE! I made a Codex skill that gives every task a clear budget before it starts. Choose Saver, Balanced, Full Power, or define your own limits. It reduces: → unnecessary repository scans → repeated commands and huge logs → speculative refactors → redundant web research → unnecessary subagents → endless retry loops It still runs the essential checks needed for a trustworthy result. If the budget isn’t enough, it creates a Markdown checkpoint you can open in Codex and resume later. It doesn’t increase your account limits. It helps you use them better. Install: npx --yes codex-budget-mode@latest 100% open source. Repo in bio.

CODEX SKILL THAT STOPS WASTING YOUR CODEX USAGE! I made a Codex skill that gives every task a clear budget before it starts. Choose Saver, Balanced, Full Power, or define your own limits. It reduces: → unnecessary repository scans → repeated commands and huge logs → speculative refactors → redundant web research → unnecessary subagents → endless retry loops It still runs the essential checks needed for a trustworthy result. If the budget isn’t enough, it creates a Markdown checkpoint you can open in Codex and resume later. It doesn’t increase your account limits. It helps you use them better. Install: npx --yes codex-budget-mode@latest 100% open source. Repo in bio.

Kappaemme

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

Your Claude Code setup is probably bloated and you don't even know it. Every MCP server you add loads its full tool list into your context window the second your session starts. Stack too many and you're burning context before you type a word. So the move was never "add more." It's "add the right ones." Anthropic dropped an official plugin that does exactly that. It scans your actual codebase and tells you what's worth adding across all five layers: → hooks → skills → MCP servers → subagents → slash commands React project? It suggests Playwright. Auth code? It flags a security reviewer. It's read-only. Touches nothing. Just hands you the blueprint. The plugin isn't the edge. Knowing it exists is. /plugin install claude-code-setup@claude-plugins-official Steal this before everyone does.

Your Claude Code setup is probably bloated and you don't even know it. Every MCP server you add loads its full tool list into your context window the second your session starts. Stack too many and you're burning context before you type a word. So the move was never "add more." It's "add the right ones." Anthropic dropped an official plugin that does exactly that. It scans your actual codebase and tells you what's worth adding across all five layers: → hooks → skills → MCP servers → subagents → slash commands React project? It suggests Playwright. Auth code? It flags a security reviewer. It's read-only. Touches nothing. Just hands you the blueprint. The plugin isn't the edge. Knowing it exists is. /plugin install claude-code-setup@claude-plugins-official Steal this before everyone does.

Evan Luthra

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

SpaceXai just made grok 4.5 FREE in your coding agent starting today it's xAI's new coding model. 500k context. built for long agent sessions. no card. what you get for $0: -83.3% on terminal-bench 2.1 -64.7% on swe-bench pro - 4.2x more efficient than Opus 4.8 -500k context for big repos -$2/M in, $6/M out once it goes paid what this replaces: -Claude Opus 4.8: $15/M in, $75/M out -SuperGrok: $30-50/mo all for $0 how to set it up (2 min): >curl -fsSL | bash > grok → localhost:8000/v1 > point hermes / aider / opencode / cline to it > model: grok-4.5 Or API key at - base url Works in Hermes, Aider, OpenCode, Cline, Claude Code, and any OpenAI-compatible tool. Important: Free for a limited time. EU waits till mid-July. Rate limits apply. bookmark this before the free window closes

SpaceXai just made grok 4.5 FREE in your coding agent starting today it's xAI's new coding model. 500k context. built for long agent sessions. no card. what you get for $0: -83.3% on terminal-bench 2.1 -64.7% on swe-bench pro - 4.2x more efficient than Opus 4.8 -500k context for big repos -$2/M in, $6/M out once it goes paid what this replaces: -Claude Opus 4.8: $15/M in, $75/M out -SuperGrok: $30-50/mo all for $0 how to set it up (2 min): >curl -fsSL | bash > grok → localhost:8000/v1 > point hermes / aider / opencode / cline to it > model: grok-4.5 Or API key at - base url Works in Hermes, Aider, OpenCode, Cline, Claude Code, and any OpenAI-compatible tool. Important: Free for a limited time. EU waits till mid-July. Rate limits apply. bookmark this before the free window closes

painn

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

this Adaptive agent uses GPT's new image model to run your entire creative + marketing team, on autopilot. here's how any business can replace their whole marketing op with it: - generates fresh on-brand creatives for every platform, daily - writes and schedules the content across every channel - replies to every comment the second it drops - DMs every lead and turns cold interest into booked clients - boosts paid ads from your best-performing organic posts - doubles down on the creatives that win, kills the ones that don't - tracks performance + adjusts strategy automatically, 24/7 every step from brand → booked client is fully automated. reply "AGENT" + RT and I'll send you the full guide so you can set it up too

Chris

72,944 просмотров • 4 месяцев назад

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.

Akshay 🚀

52,426 просмотров • 6 месяцев назад

Introducing fx, a tiny, open, native coding agent from Vercel Labs. Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it. fx is built on three principles: 1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?" 2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes. 3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP. Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms. You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic. fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X ( or file issues ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑

Introducing fx, a tiny, open, native coding agent from Vercel Labs. Originally an internal tool, fx is a harness and CLI written in Zig, optimized for research and embedding in larger systems. Today, we're open sourcing it. fx is built on three principles: 1. Fast. A single native binary, no runtime to install. It cold starts in 10µs and does no unnecessary work or I/O before accepting input. fx is the answer to "how fast can a coding agent be?" 2. Light. The 6.3MiB binary uses single-digit megabytes of memory at baseline, made for instant installation and embedding in resource-constrained environments and agent sandboxes. 3. Open. Apache-2.0, model and provider agnostic, suitable for local and cloud inference. Its small core extends through skills, plugins, and MCP. Minimalism is an obsession throughout the entire harness: system prompt, tools, features, binary. The goal was to keep context usage and time to first token low, and make fx optimal for model benchmarking, sandboxing, evals, and gyms. You can use fx directly or embed it as infrastructure. The CLI feels more like a Unix shell than an IDE in the terminal: it preserves scroll history, produces minimal output, and uses complex TUI rendering very, very sparingly. Programmatically, 𝚏𝚡 𝚊𝚜𝚔 --𝚓𝚜𝚘𝚗 gives structured output, 𝚏𝚡 𝚊𝚌𝚙 connects to editors and other clients, and WebAssembly can even run the whole thing inside the browser (see: Privacy is a design constraint: no product telemetry, sessions and usage stay local, and no source code or prompts are shared with any endpoint other than inference. With local inference and auto-updates off, fx is fully hermetic. fx is experimental. Use at your own risk and expect frequent changes. Chat with us on X ( or file issues ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑

Vercel Developers

956,014 просмотров • 24 дней назад

you don't need to re-explain your codebase's architecture to your agent every session. most tools stop at telling you what broke. sentrux is a real-time architectural sensor, it watches your codebase as a live treemap and turns file structure and dependencies into one continuous quality score. the loop is simple: codebase > agent scans structure and dependencies > sentrux scores 5 root cause metrics into one signal > agent sees exactly where risk concentrates > next session starts from a live map instead of a blind grep the binary carries zero built-in language knowledge, all 52 languages live in plugin.toml and tags.scm query files, so a new language needs zero rust code. small catch: it only scores the structure, it won't tell you why the cycle happened, that part's still on you. built pure Rust with no runtime dependencies, specifically so it could sit as one binary between an agent and a codebase without adding friction.

you don't need to re-explain your codebase's architecture to your agent every session. most tools stop at telling you what broke. sentrux is a real-time architectural sensor, it watches your codebase as a live treemap and turns file structure and dependencies into one continuous quality score. the loop is simple: codebase > agent scans structure and dependencies > sentrux scores 5 root cause metrics into one signal > agent sees exactly where risk concentrates > next session starts from a live map instead of a blind grep the binary carries zero built-in language knowledge, all 52 languages live in plugin.toml and tags.scm query files, so a new language needs zero rust code. small catch: it only scores the structure, it won't tell you why the cycle happened, that part's still on you. built pure Rust with no runtime dependencies, specifically so it could sit as one binary between an agent and a codebase without adding friction.

Simplifying AI

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

Unlimited-OCR is a 3B parameter model that parses entire 100-page PDFs in one shot — no page chunking, no lost context. +⁠32K context window, reads the whole document in a single pass +⁠93% on standard parsing benchmarks, +6 over baseline +⁠Under 0.11 error rate past page 40 — where every other OCR tool falls apart ⁠+Multilingual out of the box, runs locally via Transformers, Ollama, llama.cpp, Docker +⁠Textract, Google Vision, and Azure Doc Intelligence charge $1.50–$15 per 1,000 pages 1.9M downloads on HuggingFace and most people have never heard of it. This runs on your machine. For free. Forever. Model link:

Unlimited-OCR is a 3B parameter model that parses entire 100-page PDFs in one shot — no page chunking, no lost context. +⁠32K context window, reads the whole document in a single pass +⁠93% on standard parsing benchmarks, +6 over baseline +⁠Under 0.11 error rate past page 40 — where every other OCR tool falls apart ⁠+Multilingual out of the box, runs locally via Transformers, Ollama, llama.cpp, Docker +⁠Textract, Google Vision, and Azure Doc Intelligence charge $1.50–$15 per 1,000 pages 1.9M downloads on HuggingFace and most people have never heard of it. This runs on your machine. For free. Forever. Model link:

0xMarioNawfal

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

an agent is four parts in a loop. you own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.

an agent is four parts in a loop. you own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.

Hanako

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

this is the worst local ai will ever be. it only gets better from here. if you are not expanding your mind with these small models you are missing what's happening right now 99 percent tool call success rate. when steered well with the right skills and a framework like hermes agent the node becomes a cognition layer. not a chatbot. not a toy. an extension of how you think. i was cranking this node at 35 to 50 tok/s all day on personal experiments and now after all the work is done qwen 3.5 9B is iterating on its own code. the game it created. fixing its own bugs autonomously. and the part you should probably not miss is that all of this is happening on a RTX 3060. not an H100. not an A100. the card most of you have sitting in a drawer right now. if you just open that drawer and put that intelligence to work every tensor core on that card should be running for you. your work. your experiments. your thinking. you all have it but because nobody told you what this hardware can actually do in 2026 you never tried. the day it unlocks is the day you test your workload, understand the tradeoffs, debug the loops, and then decide if you need to scale the hardware. there is no point buying 3 mac studios when things done well you can squeeze a similar level of intelligence from 9B compared to 70B. but only when you create the right environment for your model through the right harness. and let me tell you i have tried claude code as a local harness. i have tried opencode. i have tried various others. somehow i landed on hermes agent and never left. there is something magical going on at Nous Research. the tool call parsers, the skills system, the way it handles small models natively. nothing else comes close for local inference. own your cognition. your AI. your agent. your prompts. your experiments. why give them away for free. those are who you are and they don't belong on someone else's servers being monitored. just give it a shot with your existing hardware. you run into a problem the community will help you. and if you are migrating from openclaw to hermes i will personally help you make the switch.

this is the worst local ai will ever be. it only gets better from here. if you are not expanding your mind with these small models you are missing what's happening right now 99 percent tool call success rate. when steered well with the right skills and a framework like hermes agent the node becomes a cognition layer. not a chatbot. not a toy. an extension of how you think. i was cranking this node at 35 to 50 tok/s all day on personal experiments and now after all the work is done qwen 3.5 9B is iterating on its own code. the game it created. fixing its own bugs autonomously. and the part you should probably not miss is that all of this is happening on a RTX 3060. not an H100. not an A100. the card most of you have sitting in a drawer right now. if you just open that drawer and put that intelligence to work every tensor core on that card should be running for you. your work. your experiments. your thinking. you all have it but because nobody told you what this hardware can actually do in 2026 you never tried. the day it unlocks is the day you test your workload, understand the tradeoffs, debug the loops, and then decide if you need to scale the hardware. there is no point buying 3 mac studios when things done well you can squeeze a similar level of intelligence from 9B compared to 70B. but only when you create the right environment for your model through the right harness. and let me tell you i have tried claude code as a local harness. i have tried opencode. i have tried various others. somehow i landed on hermes agent and never left. there is something magical going on at Nous Research. the tool call parsers, the skills system, the way it handles small models natively. nothing else comes close for local inference. own your cognition. your AI. your agent. your prompts. your experiments. why give them away for free. those are who you are and they don't belong on someone else's servers being monitored. just give it a shot with your existing hardware. you run into a problem the community will help you. and if you are migrating from openclaw to hermes i will personally help you make the switch.

Sudo su

58,717 просмотров • 5 месяцев назад

Polymarket Agents repo is cheating code for real life If you've been thinking AI agents are cool, but what do they actually do? this Polymarket repo is the clearest answer I've seen This Polymarket repo basically hands you a mini AI hedge fund where Claude calls the shots. It uses RAG to read the news and snipe mispriced odds 24/7, handling all the messy API work so you don't have to. Your agent could literally be catching alpha while you sleep - don't miss out on this. How you'd use it in plain English: > Pick a market (or let the agent scan for opportunities). > Feed the agent context (news, social chatter, historical notes) and let the LLM decide what matters. > Turn that into a concrete trade decision and execution loop - automated Bookmark post so you don't lose the alpha

Polymarket Agents repo is cheating code for real life If you've been thinking AI agents are cool, but what do they actually do? this Polymarket repo is the clearest answer I've seen This Polymarket repo basically hands you a mini AI hedge fund where Claude calls the shots. It uses RAG to read the news and snipe mispriced odds 24/7, handling all the messy API work so you don't have to. Your agent could literally be catching alpha while you sleep - don't miss out on this. How you'd use it in plain English: > Pick a market (or let the agent scan for opportunities). > Feed the agent context (news, social chatter, historical notes) and let the LLM decide what matters. > Turn that into a concrete trade decision and execution loop - automated Bookmark post so you don't lose the alpha

BuBBliK

16,876 просмотров • 7 месяцев назад

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.

Rohan Paul

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