ClawTab vs Skrun

ClawTab is a macOS desktop app that turns managing multiple AI coding agents from a terminal circus into an organized workflow. Built by indie developer Tõnis Tiganik, it provides a proper GUI for running Claude Code, Codex CLI, and OpenCode in parallel — with a sidebar showing per-agent status, pane splitting, auto-yes passthrough, and the ability to trigger agent restarts from your phone. The core problem it solves: once you start running more than 3-4 coding agents simultaneously, tmux panes become unreadable and you start losing context on which agent is doing what. ClawTab gives each agent a labeled tab with status indicators, scrollable history, and the ability to quickly switch contexts without losing your place. It's the kind of tool that only makes sense in a world where shipping a feature means spinning up 10 agents on 10 tasks at once — and that world is arriving fast. Version 1.0 launched on Product Hunt today and is already getting traction from the vibe-coding crowd.

Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.