Original Summary

I usually have several threads going, and each one starts its own dev servers, watchers and test loops. After a few hours I'd have processes running that I didn't know about: a server on some port, a watcher from a thread I'd closed, and no idea which thread started what. (one of my dev server was running in background for a month and I got to know when I asked claude to close all the running servers) So I built agenterm. It's a small background daemon with a CLI, an MCP server and a Mac app: - agenterm run --id web "npm run dev" (agents can also add other metadata) starts the command in a real terminal that keeps running after the thread ends, so it stays visible instead of disappearing into the background. - agenterm ls lists every task with its status, age, ports and who started it (Claude Code, Codex, OpenCode, your terminal, etc). It works that out from the process tree. - The Mac app shows each task's live terminal. You can click in and type in the same terminal the agent is using. - Agents can read the list too, so a new thread can check on or read the logs of a server an older one started. To connect it: claude mcp add --scope user agenterm -- agenterm mcp . There's also a skill ( npx skills add entange/agenterm ) that tells agents to use it only for things that don't exit, like dev servers and watchers, and not for ls or a build. It's MIT and free. CLI: npm install -g agenterm . GitHub: https://github.com/entange/agenterm Site: https://agenterm.entange.com   submitted by   /u/kxnakr [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/16 06:56:18