Introducing React Doctor Scan your React codebase for anti-patterns:... - Unnecessary useEffects - Fix accessibility issues - Prop drilling instead of context / composition Run as a CLI or agent skill. Repeat until passing. Fully open sourceshow more

Introducing /react-doctor Your React app probably has bad code.... This fixes it Install as agent skill. Fully open source. npx react-doctor@latestshow more

Introducing Expect Let agents test your code in a... real browser 1. Run Claude Code / Codex to QA your app 2. Watch a video of every bug found 3. Fix and repeat until passing Run as a CLI or agent skill. Fully open sourceshow more

Introducing React Native Doctor Find performance and security bugs... in your mobile app Run via CLI and fix with agents. Fully open source npx react-doctor@latestshow more

Introducing Amicro. A curated library of premium micro-interactions and... transition components for React. Add beautiful card hovers, button interactions, and seamless transitions to your app with a single CLI command. ✨ Open source. Try it:show more

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 context stays private Dashboard + activity logs + searchable sessions so you can see exactly what your agent did Free forever for individual devs curl -fsSL | sh This is the wayshow more

New open-source agent harness just landed! I got early... access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.show more

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 ( 𝚌𝚞𝚛𝚕 -𝚏𝚜𝚂𝙻 𝚏𝚡.𝚜𝚑/𝚜𝚎𝚝𝚞𝚙.𝚜𝚑 | 𝚋𝚊𝚜𝚑show more

🚨 NOW YOU RUN A COMPANY WITH ZERO EMPLOYEES... Paperclip is a 100% open-source framework (70k+ stars) that makes this possible. Rather than just prompting a model, you hire a CEO, engineers, and a QA reviewer. Every worker is an AI agent, and Paperclip is the Node.js and React control plane that keeps them aligned. Stop chaining messy scripts together and build a living organization: → Stand up a CEO agent to set strategy → Hire engineers and designers via Claude or Codex → Build in an automated QA loop before any ticket closes → Manage the entire portfolio from your phone When an agent slips, you do not rewrite your whole pipeline: you just correct its persona prompt, exactly like coaching a junior hire. It is exactly the kind of tooling the space needs right now. Free, open-source, and self-hosted. Repo link in 🧵↓show more

React Native now has its own shadcn/ui equivalent —... introducing 𝗡𝗮𝘁𝗶𝘃𝗲𝗨𝗜. If you love the flexibility of copying customisable components directly into your project (avoiding heavy, dependency-laden packages), NativeUI is designed for you. 𝗡𝗮𝘁𝗶𝘃𝗲𝗨𝗜 offers beautifully crafted, accessible components tailored for React Native, following the same copy-paste philosophy as shadcn/ui. Built with 𝗡𝗮𝘁𝗶𝘃𝗲𝗪𝗶𝗻𝗱 for fast, declarative, and flexible styling optimised for React Native. ➡️ 𝗖𝗼𝗽𝘆 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁 𝗰𝗼𝗱𝗲 𝗱𝗶𝗿𝗲𝗰𝘁𝗹𝘆 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 — no black-box dependencies required. ➡️ 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 𝗮𝗿𝗲 𝗮𝗰𝗰𝗲𝘀𝘀𝗶𝗯𝗹𝗲 𝗯𝘆 𝗱𝗲𝗳𝗮𝘂𝗹𝘁, supporting screen readers and keyboard navigation, and designed to align with native iOS and Android UX patterns. ➡️ 𝗙𝘂𝗹𝗹 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 𝗼𝘃𝗲𝗿 𝘆𝗼𝘂𝗿 𝗨𝗜 without rebuilding common elements like buttons, inputs, or sliders from scratch. ➡️ 𝗖𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗹𝗲 𝘄𝗶𝘁𝗵 𝗘𝘅𝗽𝗼 𝗮𝗻𝗱 𝘃𝗮𝗻𝗶𝗹𝗹𝗮 𝗥𝗲𝗮𝗰𝘁 𝗡𝗮𝘁𝗶𝘃𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀, but not yet integrated with Tamagui’s styling system (future support may be planned). ➡️ 𝗦𝘂𝗽𝗽𝗼𝗿𝘁𝘀 𝘁𝗵𝗲𝗺𝗶𝗻𝗴 𝘃𝗶𝗮 𝗡𝗮𝘁𝗶𝘃𝗲𝗪𝗶𝗻𝗱 — though you’ll need to wire it up manually using Tailwind variables, context providers, and config files. Note: The term “install” in the documentation refers to using the shadcn CLI (e.g., npx shadcn@latest add component) to fetch and copy component code into your project, not adding a package to your dependencies. NativeUI isn’t a plug-and-play library; it’s a lightweight toolbox that empowers you to shape your UI with precision and control. 𝗪𝗵𝗮𝘁’𝘀 𝘆𝗼𝘂𝗿 𝗽𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲: npm install a pre-built UI kit for speed, or copy/paste NativeUI components for ultimate customisation? #ReactNative #KeyboardUX #MobileDev #OpenSource #JSDev #Performance #iOSDev #KeyboardExtensions #ReactNativeKeyboard #UIUX #shadcn #nativeuishow more

Are you a developer working on iOS 27 app... updates? Drowning in screenshots and screen recordings? I made something for you. Free and open source. Apple Frames CLI lets you (or your agent) frame any screenshot or screen recording from any Apple device. It supports *every* official Apple frame color, grouped batches, it can merge images and videos, and so much more. I just released version 1.4 with even faster performance, videos with transparent background, and lots of fixes. This has been a labor of love over the last few months, and I hope it can help you automate your App Store screenshots as much as it helps me for my articles ☺️ Enjoy:show more

Sharing my new skill! It keeps track of high-signal... X accounts for top AI news, papers, projects, etc. Total gamechanger for me. Built with X MCP tools. Give your agent the skill and tell it to generate the artifact with top stories. Works for Codex, Claude, Hermes, OpenClaw, or whatever you use. 3 steps: 1. Set up X MCP - X API: 2. Install skill here: 3. Run prompt: "Use the x-agent-intelligence skill to build a self-contained local feed from my X MCP connection; ask for my source handles if needed, save feed.html, and validate it." It should generate a nice, beautiful HTML artifact like the one shown in the clip. You can tune it however you want. You can then set a schedule/automation to do this daily or whatever cadence you prefer. I have it every 4 hours. You will need to curate the X accounts yourself, but I have shared a few good ones under the assets. You can ask your agent to tune it to however you like. I have also shared my personal feed with our community here: I understand if it gets tricky to set up. Please reach out to me in the community forum. I plan to do a little tutorial or live session soon to help others reproduce the process. You can also store the feed as a wiki, as I have in my own implementation, but that's optional. If you encounter any issues or have ideas on how to improve it, please open a PR.show more

LangGraph. CrewAI. Agno. Which one to pick? The good... news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.show more

Introducing a new tool called "SideChannel". A secure alternative... to OpenClaw. Utilizes signal for communication and has Claude integration. I built SideChannel, an open-source Signal bot that connects Claude AI to your entire development workflow. End-to-end encrypted. From your pocket. The real power is autonomous development. Send one message like "Build a REST API with auth, pagination, and tests" and SideChannel will: - Generate a full PRD with stories and atomic tasks. - Dispatch up to 10 parallel workers (each running Claude). - Independently verify every task with a separate Claude context. - Run quality gates to catch regressions - Auto-fix failures. - Send you progress updates via Signal as work completes. Every piece of code is reviewed by a separate AI context using a fail-closed security model. If it detects security issues, backdoors, or logic errors — the code gets rejected automatically. No rubber stamps. It also has memory that actually works. Conversations are stored with vector embeddings for semantic search. Claude remembers your project conventions, past decisions, and what's been tried before. It gets smarter about your codebase over time. Other things I'm proud of: - Plugin framework for extending with custom commands. - Multi-project support with per-user scoping. - Rate limiting, path validation, phone allowlist. - Git checkpoints before every task, atomic commits after. - Stale task recovery, circular dependency detection. - Works on Linux and macOS, one-command install. It also integrates into OpenAI or Grok (optional) for more Generative AI response for simple things like "Whats the weather in New York City right now?".show more

Fixed this small bug in Linear’s app today which... I often see in other apps as well. Here’s a small before/after. The issue: When you open a popover inside a modal (think a custom select), clicking outside the popover to close it also closes the modal. The desired behavior is to close the select on click outside while keeping the modal open. This often happens because custom dropdowns or select components are rendered in a portal. The modal then treats the interaction as an outside click because, technically, the dropdown isn’t inside the modal in the DOM, it’s rendered elsewhere via a portal. The fix depends on your setup, whether it’s Radix/Base UI, fully custom etc. But since you now know the cause of it, you can ask your agent to fix it for you!show more

Top 12 agentic use cases for Jev: (bookmark this)... Jev handles semantic decisions that ordinary code cannot express reliably. It returns typed answers and probabilities, while code continues to cover the workflow. Here are 12 practical use cases for Jev: 1. Browser next action > Convert the current DOM state into a bounded action such as click, type, or stop. Code executes only valid operation-target pairs. There are already several open-source Jev web agents. 2. Context compaction > Decide which events from a long agent trace should remain. The selected text stays verbatim instead of being replaced with a generated summary. 3. Skill and context loading > Compare the current user turn against the available skills. Load only the instructions needed for that turn instead of filling the context window with every skill. 4. Typed tool-call compilation > Map a natural-language request to a function and fill its typed arguments. Each argument is evaluated separately before code allows execution. 5. Citation verification > Check whether a quoted passage exists and whether the surrounding evidence supports the claim. The output can be supported, unsupported, or contradicted. 6. Extraction verification > Run a cheap extractor first, then use Jev to verify questionable fields. Clean records stay on the fast path while uncertain ones reach a reasoning model. 7. Agent trace evaluation > Turn raw trajectories into queryable labels such as progress and repetition. This avoids asking another LLM to write a full review of every run. 8. Semantic regression tests > Replay a trace suite against a new agent build. Semantic checks can then pass or block prompt, model, tool, and policy changes in CI. 9. Jevgrep code search > Search a codebase by what the code does rather than its exact words. Jev scores candidate snippets and returns the most relevant code first. 10. Entity alignment > Compare two candidate records and decide whether to merge, review, or keep them separate. Candidate generation remains deterministic while Jev handles semantic identity. 11. Retrieval reranking > Let embeddings retrieve a broad candidate set, then use Jev to reorder passages by relevance. The generation model receives the most useful evidence first. 12. Memory promotion gate > Capture a completed agent trace, then judge whether its corrections contain a reusable lesson. Trace-backed lessons can be promoted while task-specific noise is discarded. If you want to see the final pattern in practice, it is already implemented in the Beacon open-source project. Beacon captures full sessions across Claude Code, Codex, Cursor, OpenCode, and 20+ agent harnesses, and then Jev identifies which workflows and corrections are worth learning from, so that a lesson discovered by one agent can become available to the others. GitHub repo: (don’t forget to star it ⭐) If you want to dive deeper, I also wrote about a similar mechanism in a hands-on guide. It covers building a Jev-style decision path with open models, entirely locally. Read it below.show more

Incase you haven't been paying attention Mr.Zuck just said... it in plain english that they want to have a cut of your revenue when using their Muse Agent. Make it free and available to everyone so you can build your business around it and then they take a cut of that money you make. Now the question is how many of these services planning to do that we absolutely don't know but as for me a prefer paying for a subscription than have them take a cut of the money I make btw the cut doesn't apply only for free users. So No thank you I'm gonna do my best to stick to open source agents (Hermes Agent, OpenClaw, etc) and run them on my machine instead of giving my data and money to any service whatsoever. I recommend watching the full interview some statements are outrageous.show more

AgentLinter is here! Is your agent sharp & secure?... I built AgentLinter, a linter for and agent config files. Here's why. Whether you're vibe-coding or agent-coding, your AI's output quality comes down to one thing: how well you wrote your But managing these files properly? Way harder than it looks. 🎯 The Silent Failure Problem Vague instructions like "write good code" let the agent interpret however it wants. Output gets inconsistent, but nothing throws an error. The failure is silent. Anthropic's own docs say write "Use 2-space indentation" not "Format code properly." But as the file grows, spotting these with your eyes alone is nearly impossible. 🔐 The Security Problem People hard-code API keys and tokens directly into or and commit them, way more often than you'd think. AgentLinter stats show 1 in 5 workspaces has exposed credentials. .gitignore doesn't catch secrets buried inside markdown files. 💥 The Consistency Problem Multiple config files = contradictions. says "be a friendly assistant," says "concise, direct tone." The agent gets confused. references files that don't exist. Past 5 files, these conflicts triple. So I thought: is code. Code has ESLint. Why doesn't this have a linter? 🔍 What AgentLinter Does It diagnoses your agent config across 8 categories: 1) Structure: file organization 2) Clarity: instruction specificity 3) Completeness: missing definitions 4) Security: exposed secrets 5) Consistency: cross-file contradictions 6) Memory: session handoff 7) Runtime Config: gateway/auth settings 8) Skill Safety: dangerous shell commands & injection patterns Each scored 0–100 with concrete fix suggestions. Write "be helpful" and it tells you to specify response length, tone, and format. Find an API key? Instant CRITICAL alert to rotate. 🔒 Privacy-First & 100% Local Everything runs on your machine. Files never leave. Only the results are shared, and you can turn that off in settings. This matters — these files can contain system prompts, security rules, and personal context. Fully open source, MIT license, 100% free. 🛠️ Multi-Tool Support Works with Claude Code, Cursor, Windsurf, and Clawdbot. Detects for project mode, or clawdbot.json for agent mode and adjusts diagnostics automatically. 🚀 Get Started with one line npx agentlinter Node.js 18+, no config needed. Run it, check your score, fix what needs fixing. Happy vibe-coding & happy agent life! 🤙 Website: Github:show more

Make any knowledge base or LLM wiki follow the... Open Knowledge Format with our new OKF plugin. OKF is an open spec created by Google that makes markdown-based knowledge bases portable and interoperable through a set of shared patterns and rules. With the new plugin, you can easily convert any existing knowledge base to OKF, and have agents write and maintain your wiki in the format. The plugin leverages a combination of linting, deterministic rules, and automations for creating special files like 𝚒𝚗𝚍𝚎𝚡.𝚖𝚍. It also adds a skill and leverages our MCP tools to give agents real-time hints and warnings as they write, so issues get caught immediately — plus 𝚊𝚞𝚍𝚒𝚝 and 𝚕𝚒𝚗𝚝 tools to check the entire knowledge base any time.show more

BREAKING: SpaceXAI has released a major new update for... Grok Build (v1.0.14) Grok v1.0.14 is a reliability and workflow update for the Grok CLI. It makes OIDC token refresh proactive, lets PostToolUse hooks send feedback back to the model after tools run, adds per-turn token and cost tracking via grok usage, and cuts Windows downloads by about 70%, with a large set of fixes that tighten sandboxing, subagent handling, hooks, and startup. Features: • OIDC token refresh is now proactive by default for better reliability. • PostToolUse hooks can now provide feedback and context to the model after tool execution. • SDK-registered PostToolUse hooks now provide model-facing feedback. • grok usage now shows persisted per-turn token and cost data. • Retry status in composer and title now shows a short reason for the retry. • Models can now declare a different identifier for each reasoning-effort level instead of always sending the same id. • Prompt suggestions now respect remote configuration and default to the current session model. • Windows CLI downloads are now ~70% smaller using the same compressed sidecars as macOS and Linux. Bug Fixes: • grok inspect now correctly shows Claude bypass locks as advisory rather than enforced. • Subagent sessions no longer leak threads or file descriptors when the parent is busy. • Cold startup no longer performs duplicate remote settings fetches. • Compaction failures due to context size now degrade input instead of retrying identically. • --sandbox strict now restricts writes to ~/.grok/sessions only. • Subagent spawning now waits longer on a busy coordinator and shows clearer retry guidance instead of "unreachable". • Failed task and todo tool calls now appear in the transcript instead of disappearing without a trace. • Composer status row no longer collapses or flashes when using double-Enter to send now. • Session close is no longer delayed by a single slow hook; each SessionEnd hook now has its own timeout. • Hook removal in the extensions modal no longer offers actions that the handler will refuse. • Interjections during a turn are now delivered atomically or not at all. • Subagent tasks no longer get incorrectly cancelled when the parent session is waiting for completion. • Workflow detail view now closes the overlay on X or outside click instead of returning to the run list. • Resuming subagents now succeeds for larger transcripts that still fit the model context with headroom. Performance: • Startup now fetches remote settings only once per boot instead of potentially twice. • First message on large repositories no longer waits on repository status scan. • Large session memory no longer blocks the agent during turn completion or subagent spawning. • Signed-in CLI starts faster by serving remote settings from a local cache on warm boots. Download Grok Build: Update to the latest Alpha release: grok update --alpha Update to the latest Stable release: grok updateshow more

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)show more