Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Another WTF moment. A developer just open-sourced a coding agent harness that boots 245x faster than Claude Code. It's called jcode. You launch it and the first frame renders in 14 milliseconds. Claude Code takes 3,436. One active session uses 27.8 MB of RAM. Claude Code uses 386.6. Run...

thisguyknowsai's profile picture

Brady Long

44,826 subscribers

209,751 Aufrufe • vor 3 Monaten •via X (Twitter)

Wissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

You can now review the code written by Claude Code, Codex, OpenCode, and more directly in Warp, and send inline comments straight to the agent. It's like a PR review without having to leave your terminal. Try it out!
0:19

You can now review the code written by Claude Code, Codex, OpenCode, and more directly in Warp, and send inline comments straight to the agent. It's like a PR review without having to leave your terminal. Try it out!

Warp

223,394 Aufrufe • vor 7 Monaten

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.
0:18

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.

BuBBliK

200,690 Aufrufe • vor 5 Monaten

Memory in AI Agent Harness. LLMs are stateless, so every bit of memory in an AI agent is something the harness saves to disk and loads back in when it needs it. most good agent harnesses split that memory into a few layers, let's look at each one of them: • context: what the model can see in the current session. when it gets close to full, the harness summarizes the older messages to make room. • notes: a progress file the agent keeps updating while it works, so if a session ends halfway the next one can read it and continue from there. • semantic: facts about you, your team and your project, like your preferences or which repo you work in. Hermes keeps these in MEMORY.md and USER.md. • procedural: how to do a specific job. when the agent figures out something hard, it writes it down as a skill and uses that skill the next time. • episodic: a log of every past session that the agent can search when it needs to remember what happened before. First two only last as long as the session or the task. Other three are persistent, so they're still there the next time you start the agent. save this for the next time someone asks how agents remember. follow Shubham Saboo for more on Agent Harness.
0:16

Memory in AI Agent Harness. LLMs are stateless, so every bit of memory in an AI agent is something the harness saves to disk and loads back in when it needs it. most good agent harnesses split that memory into a few layers, let's look at each one of them: • context: what the model can see in the current session. when it gets close to full, the harness summarizes the older messages to make room. • notes: a progress file the agent keeps updating while it works, so if a session ends halfway the next one can read it and continue from there. • semantic: facts about you, your team and your project, like your preferences or which repo you work in. Hermes keeps these in MEMORY.md and USER.md. • procedural: how to do a specific job. when the agent figures out something hard, it writes it down as a skill and uses that skill the next time. • episodic: a log of every past session that the agent can search when it needs to remember what happened before. First two only last as long as the session or the task. Other three are persistent, so they're still there the next time you start the agent. save this for the next time someone asks how agents remember. follow Shubham Saboo for more on Agent Harness.

Shubham Saboo

13,187 Aufrufe • vor 4 Tagen

Stop manually making flowcharts. Try this GitHub skill with Claude Code. I found an open-source tool that turns a plain description of a software system into a clean, interactive diagram. It's called Archify, and it has more than 66,000 stars on GitHub. You add it as a skill to an AI coding agent like Claude Code, Codex, Cursor, or OpenCode. Then you describe the system in the chat in one line. Archify turns that line into a single HTML file you can open, click through, and send to anyone. If you point your agent at an existing codebase, it reads the code and Archify maps how the pieces connect. I liked five things about it. 1. It makes five kinds of diagrams, including system maps and step-by-step workflows. 2. You can click any piece and trace what connects to it. 3. It checks the layout before it hands the diagram over, so arrows don't pile up and labels don't overlap. 4. It has dark and light themes and exports to PNG, SVG, or a short video. 5. You keep editing in plain chat, with requests like "add Redis" or "highlight the rollback path." You don't need a codebase to use it. A description in the chat is enough.
0:12

Stop manually making flowcharts. Try this GitHub skill with Claude Code. I found an open-source tool that turns a plain description of a software system into a clean, interactive diagram. It's called Archify, and it has more than 66,000 stars on GitHub. You add it as a skill to an AI coding agent like Claude Code, Codex, Cursor, or OpenCode. Then you describe the system in the chat in one line. Archify turns that line into a single HTML file you can open, click through, and send to anyone. If you point your agent at an existing codebase, it reads the code and Archify maps how the pieces connect. I liked five things about it. 1. It makes five kinds of diagrams, including system maps and step-by-step workflows. 2. You can click any piece and trace what connects to it. 3. It checks the layout before it hands the diagram over, so arrows don't pile up and labels don't overlap. 4. It has dark and light themes and exports to PNG, SVG, or a short video. 5. You keep editing in plain chat, with requests like "add Redis" or "highlight the rollback path." You don't need a codebase to use it. A description in the chat is enough.

Alex Veremeyenko

61,928 Aufrufe • vor 1 Monat

EVERYONE'S TRYING TO SOLVE AI TEAM MEMORY WITH SERVERS, VECTOR DATABASES, AND ORCHESTRATION PLATFORMS. THIS OPEN SOURCE TOOL DOES IT WITH ONE FOLDER IN YOUR REPO. Every dev on your team runs Claude Code. When one agent screws something up, the rest have no idea. They just repeat the mistake next week. It's called teamlore. When your agent gets corrected or breaks something, it writes a small lore file into a .lore/ folder. That file ships with your PR, gets reviewed like normal code, and after merge every teammate's agent automatically recalls it when they touch that part of the repo. No server. No datab No accounts. No SaaS bill. Just a folder in git. Which means code review catches bad lessons before they poison the team, git blame tells you when a rule was added and why, and the whole thing works offline. One command to install: npx teamlore init Companion command: npx teamlore scarmap. Turns your team's history of mistakes into a visual heat map of the codebase. Every red zone is a place your team has been burned before. Which means every red zone is a place your agents should slow down. Here's the wildest part. The teamlore repo's own .lore/ folder contains every mistake Claude made while building teamlore itself. Dogfooded end-to-end. You can literally open the folder and read the receipts. The author's public invitation: "Would love for someone to try and break it." Available on npm. Repo just launched. 100% open source. (link in the comments)
0:15

EVERYONE'S TRYING TO SOLVE AI TEAM MEMORY WITH SERVERS, VECTOR DATABASES, AND ORCHESTRATION PLATFORMS. THIS OPEN SOURCE TOOL DOES IT WITH ONE FOLDER IN YOUR REPO. Every dev on your team runs Claude Code. When one agent screws something up, the rest have no idea. They just repeat the mistake next week. It's called teamlore. When your agent gets corrected or breaks something, it writes a small lore file into a .lore/ folder. That file ships with your PR, gets reviewed like normal code, and after merge every teammate's agent automatically recalls it when they touch that part of the repo. No server. No datab No accounts. No SaaS bill. Just a folder in git. Which means code review catches bad lessons before they poison the team, git blame tells you when a rule was added and why, and the whole thing works offline. One command to install: npx teamlore init Companion command: npx teamlore scarmap. Turns your team's history of mistakes into a visual heat map of the codebase. Every red zone is a place your team has been burned before. Which means every red zone is a place your agents should slow down. Here's the wildest part. The teamlore repo's own .lore/ folder contains every mistake Claude made while building teamlore itself. Dogfooded end-to-end. You can literally open the folder and read the receipts. The author's public invitation: "Would love for someone to try and break it." Available on npm. Repo just launched. 100% open source. (link in the comments)

Harman

35,140 Aufrufe • vor 3 Monaten

motion designers are in serious danger, here is why an AI agent can now model a 3D scene in Blender, animate a website and render a finished MP4. you describe it, the agent builds it. three repos doing exactly that: -> HyperFrames: write HTML, get a video. made by HeyGen for AI agents. ask for a 10-second product intro with a fade-in title and background music, and the agent plans it, animates it and renders the MP4 -> MCP for Blender: connects Blender to Claude or any other model. the agent creates objects, builds scenes and edits them in real 3D while you watch -> GSAP skills: the official skills that teach coding agents to animate the web properly with GSAP. timelines, scroll effects, the stuff premium landing pages are made of the setup for HyperFrames in Claude Code is two lines: claude plugin marketplace add heygen-com/hyperframes claude plugin install hyperframes@hyperframes then just type /hyperframes:hyperframes and describe your video. the stack in one line: Blender for the 3D, GSAP for the motion, HyperFrames for the final render. bookmark this before your next client asks for a promo video.
0:19

motion designers are in serious danger, here is why an AI agent can now model a 3D scene in Blender, animate a website and render a finished MP4. you describe it, the agent builds it. three repos doing exactly that: -> HyperFrames: write HTML, get a video. made by HeyGen for AI agents. ask for a 10-second product intro with a fade-in title and background music, and the agent plans it, animates it and renders the MP4 -> MCP for Blender: connects Blender to Claude or any other model. the agent creates objects, builds scenes and edits them in real 3D while you watch -> GSAP skills: the official skills that teach coding agents to animate the web properly with GSAP. timelines, scroll effects, the stuff premium landing pages are made of the setup for HyperFrames in Claude Code is two lines: claude plugin marketplace add heygen-com/hyperframes claude plugin install hyperframes@hyperframes then just type /hyperframes:hyperframes and describe your video. the stack in one line: Blender for the 3D, GSAP for the motion, HyperFrames for the final render. bookmark this before your next client asks for a promo video.

kiosa

63,233 Aufrufe • vor 22 Tagen

EXCUSE ME?? IQuest raised a 320B model from its very first token, then gave it over a million exams with three proctors on every single one the exams are real executable containers. one check runs while the environment gets prepped, one while the code executes, and a full trajectory audit after. if the model tries to peek at hidden tests, it gets flagged, so every pass it learns from is earned it's called IQuest-Q1, an open model built to live in your terminal → 15B active out of 320B, only 8 of 256 experts per token → 29T training tokens, context stretched 32K → 128K → 512K → SFT, RL in real environments, then multi-teacher distillation (MOPD) → runs inside Claude Code, Codex and other agent scaffolds my favorite speed trick: an MTP layer gets reused as a drafter that guesses the next tokens, and the main model checks them. long sessions get way cheaper on the same parameter budget the team calls this an early release. a first model with training this strict makes me want to see the second one try it:
0:12

EXCUSE ME?? IQuest raised a 320B model from its very first token, then gave it over a million exams with three proctors on every single one the exams are real executable containers. one check runs while the environment gets prepped, one while the code executes, and a full trajectory audit after. if the model tries to peek at hidden tests, it gets flagged, so every pass it learns from is earned it's called IQuest-Q1, an open model built to live in your terminal → 15B active out of 320B, only 8 of 256 experts per token → 29T training tokens, context stretched 32K → 128K → 512K → SFT, RL in real environments, then multi-teacher distillation (MOPD) → runs inside Claude Code, Codex and other agent scaffolds my favorite speed trick: an MTP layer gets reused as a drafter that guesses the next tokens, and the main model checks them. long sessions get way cheaper on the same parameter budget the team calls this an early release. a first model with training this strict makes me want to see the second one try it:

Nelly;

92,433 Aufrufe • vor 11 Tagen

It is becoming f*cking dangerous: the NSA's own reverse-engineering tool now plugs straight into Claude Code - Ghidra has 94k stars, and GhidraMCP lets your agent read a compiled program instead of guessing what it does Install Ghidra 12.1.4 from ghidra-sre,org (free, released by the NSA) Download the GhidraMCP release and add it in File -> Install Extensions Restart Ghidra and switch on GhidraMCPPlugin in File -> Configure -> Developer Connect it: claude mcp add ghidra -- uvx --from git+ ghidra-mcp Open a binary you're allowed to analyze and let Ghidra run its analysis Ask Claude what a function does: it decompiles it, renames the variables and explains it in plain English Ask for the map: every function, import, string and cross-reference, and where the interesting code lives The decompiling runs in Ghidra on your machine, Claude just drives it Malware samples, old firmware, your own builds: your agent reads the program itself, not the docs about it Find the repo in the reply below
0:20

It is becoming f*cking dangerous: the NSA's own reverse-engineering tool now plugs straight into Claude Code - Ghidra has 94k stars, and GhidraMCP lets your agent read a compiled program instead of guessing what it does Install Ghidra 12.1.4 from ghidra-sre,org (free, released by the NSA) Download the GhidraMCP release and add it in File -> Install Extensions Restart Ghidra and switch on GhidraMCPPlugin in File -> Configure -> Developer Connect it: claude mcp add ghidra -- uvx --from git+ ghidra-mcp Open a binary you're allowed to analyze and let Ghidra run its analysis Ask Claude what a function does: it decompiles it, renames the variables and explains it in plain English Ask for the map: every function, import, string and cross-reference, and where the interesting code lives The decompiling runs in Ghidra on your machine, Claude just drives it Malware samples, old firmware, your own builds: your agent reads the program itself, not the docs about it Find the repo in the reply below

Archive

16,420 Aufrufe • vor 14 Tagen

No coding. No data leaks. Just your agent, live on-chain. Build a private AI agent or app in the Vibe Code Challenge: Agent Edition. 175,000 $COTI in prizes Agent Skills, MCP, and Messaging SDK Works with Claude, OpenAI, Hermes, Manus Build it to win it. Enter now!
0:16

No coding. No data leaks. Just your agent, live on-chain. Build a private AI agent or app in the Vibe Code Challenge: Agent Edition. 175,000 $COTI in prizes Agent Skills, MCP, and Messaging SDK Works with Claude, OpenAI, Hermes, Manus Build it to win it. Enter now!

COTI Foundation

3,182,647 Aufrufe • vor 4 Monaten

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.
0:11

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 Aufrufe • vor 3 Monaten

i don't f*cking understand why this isn't popular yet someone has created a memory system that uses 90% fewer tokens while still finding all the expected symbols it builds a local graph of source symbols and their relationships. architecture, decisions and handoffs live as Git-tracked Markdown. a note can point to the code behind it, so a code change can flag that knowledge for review the loop: scan the repo → map the code → write the why → anchor notes to symbols → retrieve a task-sized slice → review drift → commit to Git → continue in the next session in the author's small, one-repo test, graph retrieval returned 10.74× less context than grep top-3 while finding every expected symbol across six tasks the useful part is the connection between memory and evidence. the repo carries what the agent learned, and the code gives you a way to check whether that knowledge still holds save this, then build a second brain for your company⭣
0:15

i don't f*cking understand why this isn't popular yet someone has created a memory system that uses 90% fewer tokens while still finding all the expected symbols it builds a local graph of source symbols and their relationships. architecture, decisions and handoffs live as Git-tracked Markdown. a note can point to the code behind it, so a code change can flag that knowledge for review the loop: scan the repo → map the code → write the why → anchor notes to symbols → retrieve a task-sized slice → review drift → commit to Git → continue in the next session in the author's small, one-repo test, graph retrieval returned 10.74× less context than grep top-3 while finding every expected symbol across six tasks the useful part is the connection between memory and evidence. the repo carries what the agent learned, and the code gives you a way to check whether that knowledge still holds save this, then build a second brain for your company⭣

beamnxw ./

33,354 Aufrufe • vor 1 Monat

Google Antigravity just added REMOTE AGENTS!!! You can now start a coding task, close Antigravity, and the agent will STILL keep working in the cloud!!! It even supports GitHub and Google Drive, and you can check on your agents from any browser. I'm starting to think Google is going ALL IN on competing with Claude Code and Codex. Google is seriously cooking with Antigravity lately.
0:15

Google Antigravity just added REMOTE AGENTS!!! You can now start a coding task, close Antigravity, and the agent will STILL keep working in the cloud!!! It even supports GitHub and Google Drive, and you can check on your agents from any browser. I'm starting to think Google is going ALL IN on competing with Claude Code and Codex. Google is seriously cooking with Antigravity lately.

Stats Wire

52,700 Aufrufe • vor 4 Tagen

We've updated /fork in Claude Code /fork now runs a background agent with your exact context (system prompt, tools, history, model) and prompt cache. The result gets returned to your session. /branch (the old /fork) still copies the transcript to a new session you drive.
0:16

We've updated /fork in Claude Code /fork now runs a background agent with your exact context (system prompt, tools, history, model) and prompt cache. The result gets returned to your session. /branch (the old /fork) still copies the transcript to a new session you drive.

ClaudeDevs

381,886 Aufrufe • vor 5 Monaten

Claude Code 2.1.90 just dropped with a new /powerup command Run it and you get interactive lessons that teach you how to use Claude Code right inside the tool. It's solid and has a lot of potential for learning directly in the terminal. Curious how the UI will look in VSCode and Claude Code Desktop. Going to keep digging into this new release!
0:18

Claude Code 2.1.90 just dropped with a new /powerup command Run it and you get interactive lessons that teach you how to use Claude Code right inside the tool. It's solid and has a lot of potential for learning directly in the terminal. Curious how the UI will look in VSCode and Claude Code Desktop. Going to keep digging into this new release!

Daniel San

272,065 Aufrufe • vor 7 Monaten

New in Claude Code: your sessions can now message each other. Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task.
0:16

New in Claude Code: your sessions can now message each other. Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task.

ClaudeDevs

7,987,707 Aufrufe • vor 3 Monaten

Seems like Visual Studio Code is starting to tell you: your agent primitives need to move. There is now a new migration banner in the Chat panel, and it is part of a much bigger change happening under the hood: the move from the old Local harness to the new Agent Host architecture built around AHP. This is not just about moving where an agent runs. The old model was very VS Code-centric: prompts, custom agents, instructions and skills could live in VS Code-specific locations and the agent runtime lived inside the extension host. The new Agent Host separates the agent runtime from the editor. Sessions can keep running when the window closes, be shared across VS Code windows, run remotely, and support different harnesses such as Copilot, CLI and Copilot Desktop App through a common session layer. And that means some of our primitives need to move too. Prompt files are being deprecated for Agent Host and migrated to Skills. User-level agents and instructions that lived in VS Code profile storage need to move to harness-supported locations. Even the old location settings are being deprecated. The new migration experience can detect these things and guide you through moving or converting them, while keeping the originals unless you explicitly remove them. The new banner is basically the first visible sign that this migration is becoming a real product workflow. Basically telling us - it's time to move on!!!! If you have accumulated a lot of prompts, custom agents, instructions and skills over the last year, now is probably a good time to understand where they actually live and which harness owns them. To summarize the shift - it isn't just: VS Code Chat → Agent Host It is: VS Code-specific primitives → harness-native primitives. And I think this is going to become increasingly important as agents stop being features inside an IDE and become runtimes that multiple clients can connect to. Go run your migrations now 🏃‍♀️
0:16

Seems like Visual Studio Code is starting to tell you: your agent primitives need to move. There is now a new migration banner in the Chat panel, and it is part of a much bigger change happening under the hood: the move from the old Local harness to the new Agent Host architecture built around AHP. This is not just about moving where an agent runs. The old model was very VS Code-centric: prompts, custom agents, instructions and skills could live in VS Code-specific locations and the agent runtime lived inside the extension host. The new Agent Host separates the agent runtime from the editor. Sessions can keep running when the window closes, be shared across VS Code windows, run remotely, and support different harnesses such as Copilot, CLI and Copilot Desktop App through a common session layer. And that means some of our primitives need to move too. Prompt files are being deprecated for Agent Host and migrated to Skills. User-level agents and instructions that lived in VS Code profile storage need to move to harness-supported locations. Even the old location settings are being deprecated. The new migration experience can detect these things and guide you through moving or converting them, while keeping the originals unless you explicitly remove them. The new banner is basically the first visible sign that this migration is becoming a real product workflow. Basically telling us - it's time to move on!!!! If you have accumulated a lot of prompts, custom agents, instructions and skills over the last year, now is probably a good time to understand where they actually live and which harness owns them. To summarize the shift - it isn't just: VS Code Chat → Agent Host It is: VS Code-specific primitives → harness-native primitives. And I think this is going to become increasingly important as agents stop being features inside an IDE and become runtimes that multiple clients can connect to. Go run your migrations now 🏃‍♀️

Oren Melamed

30,867 Aufrufe • vor 1 Monat

THIS IS WHAT A SUPPORT TEAM LOOKS LIKE IN 2026 A customer reports that their export stops at 10,000 of 18,400 contacts. And instead of passing the ticket from tool to tool: → Support agent replies → Coding agent finds the bug → Docs agent updates the guide → CRM agent prepares the renewal All on the same ticket, with the same context: logs, billing, code and previous conversations. It's called Helpin. It's open source and you can self-host it.
0:15

THIS IS WHAT A SUPPORT TEAM LOOKS LIKE IN 2026 A customer reports that their export stops at 10,000 of 18,400 contacts. And instead of passing the ticket from tool to tool: → Support agent replies → Coding agent finds the bug → Docs agent updates the guide → CRM agent prepares the renewal All on the same ticket, with the same context: logs, billing, code and previous conversations. It's called Helpin. It's open source and you can self-host it.

marcus

22,919 Aufrufe • vor 1 Monat

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.
0:14

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 Aufrufe • vor 8 Monaten

🚨 YOUR AI AGENT CAN NOW READ YOUR NOTIFICATIONS AND ACT ON THEM BEFORE YOU EVEN SEE THEM It’s called PhoneUse and it just launched. It gives your agent its own phone in the cloud, a real Android, connected to Claude through an MCP. Time needed: 10 minutes Steps: connect the MCP, tell your agent what to watch for What it handles on its own: → Your flight gets delayed: it sees the push notification and texts whoever is picking you up → Your Uber is on the way: it checks the driver’s status and lets people know when you’ll arrive → An app asks for a 2-step code: it reads the SMS and gets through the verification → An old app with no API: it opens it and taps through it like a person would Until now agents were stuck in the browser. Most of the apps we use every day don’t have an API, so they couldn’t touch them. Now they have a phone. Save it before it gets deleted 🔖 Link in the comments 👇
0:13

🚨 YOUR AI AGENT CAN NOW READ YOUR NOTIFICATIONS AND ACT ON THEM BEFORE YOU EVEN SEE THEM It’s called PhoneUse and it just launched. It gives your agent its own phone in the cloud, a real Android, connected to Claude through an MCP. Time needed: 10 minutes Steps: connect the MCP, tell your agent what to watch for What it handles on its own: → Your flight gets delayed: it sees the push notification and texts whoever is picking you up → Your Uber is on the way: it checks the driver’s status and lets people know when you’ll arrive → An app asks for a 2-step code: it reads the SMS and gets through the verification → An old app with no API: it opens it and taps through it like a person would Until now agents were stuck in the browser. Most of the apps we use every day don’t have an API, so they couldn’t touch them. Now they have a phone. Save it before it gets deleted 🔖 Link in the comments 👇

draven

38,752 Aufrufe • vor 17 Tagen

someone packed 637 motion design techniques into a skill Claude Code can actually read if you make launch videos alone, steal this it's an open source field guide + agent skill for Claude Code and Codex what's inside: → mask reveals that bring your product onto the screen → kinetic type for headlines that need to hit → cursor moves and clicks that walk people through your UI → count-ups and chart races for your metrics → dashed flows and path diagrams for agent systems → parallax, camera moves and 3D card flips for depth → 11 recipes that stitch it all into demos and launch videos the part that matters: every effect has its own card with timing, easing, parameter ranges, good and bad examples and ready prompts so your agent builds from real numbers, not vibes 128 of them already ship as reference clips you can re-render with your own text the loop: describe the scene → pick the technique → swap in your content → render → check the frames try it on your next launch: one screenshot → one click → a 10-second demo bookmark this, repo below ↓
0:20

someone packed 637 motion design techniques into a skill Claude Code can actually read if you make launch videos alone, steal this it's an open source field guide + agent skill for Claude Code and Codex what's inside: → mask reveals that bring your product onto the screen → kinetic type for headlines that need to hit → cursor moves and clicks that walk people through your UI → count-ups and chart races for your metrics → dashed flows and path diagrams for agent systems → parallax, camera moves and 3D card flips for depth → 11 recipes that stitch it all into demos and launch videos the part that matters: every effect has its own card with timing, easing, parameter ranges, good and bad examples and ready prompts so your agent builds from real numbers, not vibes 128 of them already ship as reference clips you can re-render with your own text the loop: describe the scene → pick the technique → swap in your content → render → check the frames try it on your next launch: one screenshot → one click → a 10-second demo bookmark this, repo below ↓

Asteri

43,570 Aufrufe • vor 24 Tagen