{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Machine Learning Tech Brief By HackerNoon","title":"AI Coding Agents for Teams: Building a Managed Runtime, Not Just More tmux","html":"","width":"100%","height":180,"duration":1329,"description":"\n This story was originally published on HackerNoon at: https://hackernoon.com/ai-coding-agents-for-teams-building-a-managed-runtime-not-just-more-tmux.\n A practical guide to running AI coding agents as a team: dev servers, durable tmux sessions, separate agent users, and controlled access. \n Check more stories related to machine-learning at: https://hackernoon.com/c/machine-learning.\n You can also check exclusive content about #ai-agents, #claude-code, #devops, #developer-tools, #tmux, #codex, #infrastructure-as-code, #coding-agents-for-teams, and more.\n \n \n This story was written by: @zakarov. Learn more about this writer by checking @zakarov's about page,\n and for more stories, please visit hackernoon.com.\n \n \n \n - agents live on dev servers, not laptops;\n- tmux keeps long-running sessions alive;\n- Eternal Terminal gives you a connection that survives drops;\n- each person has their own Linux user and runs agents under a separate Linux user;\n- agent permissions are trimmed to the bare minimum;\n- on top of tmux you build a session manager that lets leads see different people's sessions across different servers and attach to them;\n- control over who can see and connect to whose sessions should be flexible and obvious, with no shared keys and no root handed out;\n- events are logged and available for audit.\n \n ","thumbnail_url":"https://img.transistorcdn.com/KyA01h2FD2insgk-wX_xzV6vbJnTNl2BvPYVL-XaI9A/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMjcyLzE2ODM1/ODI0ODgtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}