Introducing the Agent Virtual Machine (AVM) Think V8 for... agents. AI agents are currently running on your computer with no unified security, no resource limits, and no visibility into what data they're sending out. Every agent framework builds its own security model, its own sandboxing, its own permission system. You configure each one separately. You audit each one separately. You hope you didn't miss anything in any of them. The AVM changes this. It's a single runtime daemon (avmd) that sits between every agent framework and your operating system. Install it once, configure one policy file, and every agent on your machine runs inside it - regardless of which framework built it. The AVM enforces security (91-pattern injection scanner, tool/file/network ACLs, approval prompts), protects your privacy (classifies every outbound byte for PII, credentials, and financial data - blocks or alerts in real-time), and governs resources (you say "50% CPU, 4GB RAM" and the AVM fair-shares it across all agents, halting any that exceed their budget). One config. One audit command. One kill switch. The architectural model is V8 for agents. Chrome, Node.js, and Deno are different products but they share V8 as their execution engine. Agent frameworks bring the UX. The AVM brings the trust. Where needed, AVM can also generate zero-knowledge proofs of agent execution via 25 purpose-built opcodes and 6 proof systems, providing the foundational pillar for the agent-to-agent economy. AVM v0.1.0 - Changelog - Security gate: 5-layer injection scanner with 91 compiled regex patterns. Every input and output scanned. Fail-closed - nothing passes without clearing the gate. - Privacy layer: Classifies all outbound data for PII, credentials, and financial info (27 detection patterns + Luhn validation). Block, ask, warn, or allow per category. Tamper-evident hash-chained log of every egress event. - Resource governor: User sets system-wide caps (CPU/memory/disk/network). AVM fair-shares across all agents. Gas budget per agent - when gas runs out, execution halts. No agent starves your machine. - Sandbox execution: Real code execution in isolated process sandboxes (rlimits, env sanitization) or Docker containers (--cap-drop ALL, --network none, --read-only). AVM auto-selects the tier - agents never choose their own sandbox. - Approval flow: Dangerous operations (file writes, shell commands, network requests) trigger interactive approval prompts. 5-minute timeout auto-denies. Every decision logged. - CLI dashboard: hyperspace-avm top shows all running agents, resource usage, gas budgets, security events, and privacy stats in one live-updating screen. - Node.js SDK: Zero-dependency hyperspace/avm package. AVM.tryConnect() for graceful fallback - if avmd isn't running, the agent framework uses its own execution path. OpenClaw adapter example included. - One config for all agents: ~/.hyperspace/avm-policy.json governs every agent framework on your machine. One file. One audit. One kill switch.show more

Varun
140,446 views • 3 months ago
You can now give your Agent its own: +... Profile + Wallet + DMs + Network One setup prompt. No human in the loop required. An open playground for people and agents to interact. Works with Hermes, Openclaw and any other harness. Copy the prompt below ↓↓↓show more

Zora
28,486 views • 4 days ago
Someone told ClawdBot to build a 6-agent Polymarket trading... system while they slept. 6 hours. Not a single question asked. Here's what it built on its own: > Monitoring agent running 24/7 — spots mispriced markets, writes to memory, pings Telegram instantly > Research agent parsing news, X, and macro data every morning before you check your phone > Trading agent reading the research memory and acting before the market catches up > All of it running on one Gateway, one config file, isolated per agent First week results: - 47 mispriced markets caught before Polymarket adjusted - 8-12c avg entry edge per position - Token cost dropped 3x, from $0.40 to $0.13 per request The whole system is plain .md text files. Change one line, the agent behaves differently. No deploy. No build. A BOT RESPONDS. AN AGENT EARNS. THIS IS WHAT AGENTIC TRADING ACTUALLY LOOKS LIKE.show more

0xMarioNawfal
80,450 views • 3 months ago
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.show more

Rohan Paul
178,460 views • 8 months ago
Someone told ClawdBot to build a 6-agent Polymarket trading... system while they slept. 6 hours. Not a single question asked. Here’s what it built on its own: Monitoring agent — runs 24/7, spots mispriced markets, writes to memory, sends Telegram alerts instantly Research agent — parses news, X, and macro data every morning before you check your phone Trading agent — reads research memory and executes before the market catches up All on one Gateway, one config file, isolated per agent Copytrade → First week results: 47 mispriced markets captured before Polymarket adjusted 8–12¢ avg edge per position Token cost dropped 3×, from $0.40 → $0.13 per request The entire system is just plain .md text files. Change one line, the agent behaves differently. No deploy. No build. A BOT RESPONDS. AN AGENT EARNS. THIS IS WHAT AGENTIC TRADING ACTUALLY LOOKS LIKE.show more

Discover
14,679 views • 3 months ago
🧃 Introducing stereOS: a Linux based operating system hardened... and purpose built for AI agents. It's clear that agents need an ACTUAL operating system (not what people are calling an "OS") to witness the full breadth and depth of their capabilities while mitigating the blast radius of autonomous, untrusted actors. But there are so many problems with AI sandboxes today: * Going out to the apple store and buying a mac mini will never scale and is way too expensive (obviously) * Running in Docker is too restrictive (agents can't stand up their own container infrastructure, no sub virtualization, docker-in-docker is very broken) * Firecracker strips all the hardware so GPU PCIe passthrough, secure boot, FIPs, etc. is out of the question. * Native VMs are too fat and the overhead of 1 agent per VM is too much. stereOS takes a different approach: it's a full NixOS system that you boot and then kick off agent sandboxes inside with gVisor + /nix/store namespace mounting. Each agent gets their own kernel and the /nix/store is read only by nature. Even if the agent was somehow able to escape the gVisor virtual kernel, they'd land on the NixOS system as the "agent" user! Not your actual hardware!! If you want to take a defense-in-depth approach, we support "native" agents that run at the system level kicked off by our `agentd` utility. These agents, on their own, can manage and kick off other sub agents using the internal sandboxing mechanisms. Today, we're open sourcing all of this: * stereOS: our purpose built Linux OS - * masterblaster: client utility to launch, manage, and orchestrate agents - * stereosd: the stereOS system control plane daemon - * agentd: the stereOS system agent management daemon - Give it a try, throw us a star, and let me know what you think 🧃⭐️show more

John McBride
150,077 views • 3 months ago
ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic... shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.show more

BuBBliK
199,701 views • 20 days ago
BIG one for devs today. Introducing the Notion Developer... Platform: - Notion CLI, ntn (Notion in your terminal) - Workers (run code on Notion's infra) - Database sync (any data source into Notion) - Agent tools (build any workflow) - Webhook triggers (trigger Notion from any app) - External Agents API (bring any agent into Notion) - Notion Agents SDK (use Notion Agents anywhere) - …and a bunch more API improvements And soon, you won't need to be a developer to build on Notion. Your agent will be one for you.show more

Notion
970,836 views • 1 month ago
Zuckerberg built his own AI agent to run Meta.... this man is literally becoming Tony Stark. it pulls data from every team inside the company so he can skip meetings, skip the chain of command, and make decisions faster than any human process allows. 78,000 employees have their own AI agents now too. one messages coworkers on your behalf. another acts as your AI chief of staff. their agents talk to each other in an internal network. humans optional. Meta also bought an entire social media platform built for AI agents to interact with each other. read that again. Zuck said he wants every person at Meta to have a personal AI agent. then every person outside Meta. the Jarvis era started.show more

sui ☄️
153,559 views • 3 months ago
Devin Desktop supports the Agent Client Protocol (ACP): bring... your own agents to work alongside Devin, all in one unified view.show more

Cognition
47,627 views • 19 days ago
Every AI agent on Injective is now verifiable onchain.... Together with AltLayer, Injective agents are officially live on 8004scan. Reputation, validation, and ERC-8004 identity for every agent. Browse the agent economy on Injective now. 👇show more

Injective 🥷
26,266 views • 2 months ago
Introducing Agent File (.af) 👾 - an open file... format for importing/exporting agents. With .af, you can reproduce an agent (with the same behavior and memories) without any setup or scripts: simply load the .af into your Letta server or Letta Desktop:show more

Letta
43,771 views • 1 year ago
MINT ANNOUNCEMENT / MECHANICS I asked the agent when... we should mint. It said June 5. 🫠 So June 5 it is. 10,000 agents are ready to deploy. Agent Price (MP): 0.0005 ETH Mint link: MECHANICS 2 major AI integrations are built into every agent: ◉ Claude ◉ Gemini One agent. Two minds. Post-mint, activate your agent and watch it work. Over the next few days, we'll be rolling out the communities eligible for a WHATEVER Agent. Few spots are left. Drop your wallet. Or whatever.show more

whatever
22,127 views • 20 days ago
EIP-8004 is coming to the Nova architecture, a trustless... infrastructure for AI agents that introduces key on-chain registries, enabling agents to interact safely across the Shido Network. These core components allow autonomous AI agents to verify identity, build reputation, and collaborate without relying on a centralized platform. The result is a decentralized trust layer for agent-to-agent economies, where agents can autonomously discover, evaluate, and work with one another across the Shido ecosystem.show more

Shido
390,734 views • 3 months ago
Stop spending hours on manual work. You can now... use a multi-agent AI workforce to get more work done in less time. Here's how 👇 --- Try Eigent AI - Lets you build and run a custom AI workforce on your desktop. - Automate complex workflows using multi-agent task execution. - Built on CAMEL-AI’s top open-source projects ( CAMEL-AI.org & OWL). - Boost productivity with deep customization and strong privacy --- Features: - Customize Your AI Workforce: Build task-specific agents with domain skills and tools. - Faster Execution: Eigent runs agents in parallel to automate complex workflows. - Human-in-the-loop: Automatically asks for help when tasks hit uncertainty. --- What sets Eigent apart? - 3–5× faster task execution using a parallel multi-agent workforce. - Modular design lets you add new capabilities without changing the core system. - Self-optimizing agents that replan and adapt during execution for higher success. - Deploy anywhere: cloud, local, or enterprise, with full open-source flexibility. --- Try building your multi-agent AI workforce here: Join their community to build your multi-agent workforce: Check their GitHub: ---show more

Shushant Lakhyani
20,423 views • 10 months ago
Claude Code Agent Teams are f*cking ridiculous 🤯 One... prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)show more

Mike Futia
46,333 views • 3 months ago
70% fewer tokens per task. Context that compounds across... every session, every agent, every teammate. Agent traces are the memory. TOKENMAXXING for coding agents on OriginTrail DKG v10.show more

OriginTrail
1,359,946 views • 26 days ago
Users can explore how different AI agents analyze the... same market task and compare their outputs through the platform. It is a product experience built around agent performance, task execution, and real usage. AI agents are becoming measurable digital workers.show more

OKAI Official
10,097 views • 1 month ago
herdr 0.7.0 is out, and it's a major one:... it introduces plugins! the idea is simple: herdr stays lean, and everything custom gets extended through plugins. shareable, scoped, built however you want, to fit your own flow. with this release we're also shipping a few examples of what the plugin system can do. first up: a telegram plugin. herdr already controls your agents and knows their status, so the plugin just hooks into agent events and pings telegram the moment one needs you. notification lands → `herdr --remote` or ssh from your phone → straight back to the agent that needs you.show more

herdr
72,584 views • 7 days ago
I stack Hermes agents with OpenClaw for financial research,... and the results should be illegal. I track every politician, insider trader, and I know EXACTLY what moves they're making. If you can't beat them, join them. The exact playbook for printing money from insider trading (copy me): Requirements: • OpenClaw setup • Hermes Agent setup Step 1. Define your research thesis Before you send any prompts to either tool, you'll need to clarify exactly what you're trying to research. This could be: a specific industry, asset class, market sector, and so on. Examples: • Tracking smart money buys in the semiconductor industry • Tracking smart money buys in crypto • Tracking a specific politician and where they're bidding (like Nancy Pelosi) Step 2. Deploy Hermes agents to track the smart money (in parallel) Hermes is your data layer. Spin up 5 agents at the same time, each with one job: Agent 1: Track every politician's disclosed trades from the last 30 days (House and Senate stock disclosures) Agent 2: Pull insider transactions (Form 4 filings, CEO/CFO buys and sells) Agent 3: Scrape X sentiment from top 50 accounts on the topic Agent 4: Pull on-chain data (whale wallets, TVL, exchange flows) *if applicable* Agent 5: Monitor news, regulatory filings, and announcements from the last 30 days Each agent runs independently. You're not waiting for one to finish before the next starts. Step 3. Consolidate the output Once your Hermes agents finish, dump every output into a single document. (don't filter or summarize) - you want OpenClaw to see the raw data. Step 4. Feed it all into OpenClaw Open OpenClaw and paste the consolidated research file with this prompt: "Act as an elite macro analyst. Below is raw data gathered from multiple sources on [thesis], including politician disclosures and insider transactions. Synthesize the findings, identify the strongest signals and contradictions, flag any unusual smart-money activity, and give me a clear directional view with conviction levels. Flag any data gaps that need follow-up." OpenClaw will go deep, run its own reasoning chain, and produce a synthesized report. Done. Now you're literally tapping into the financial data they don't want you to see (it's all public - you just had to find it). Make sure to save this playbook so you don't lose it!show more

Miles Deutscher
19,709 views • 1 month ago
Introducing Giza World Snapshots ↓ For the first time,... you can watch your financial agent move onchain. Every Giza agent navigates protocols, allocates capital, and optimizes yield in real-time. Giza World now makes all of that visible. Enter your agent's address to watch its journey or play around with the world itself. Remix your colors, make it yours, and share it on X.show more

Giza
298,053 views • 3 months ago