teamfuse.dev is built with Next.js, hosted on AWS.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| 16.2.4 | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 9 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting2 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
ns36.domaincontrol.comns35.domaincontrol.comgoogle-site-verification=YhsQSnLENzcJANZgcr9pO50TPvTVrH9dwAw_T8XjzaQv=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;User-Agent: * Allow: / Host: https://teamfuse.dev Sitemap: https://teamfuse.dev/sitemap.xml
# teamfuse > Fuse Claude Code agents into a working team. Open source template for running a team of Claude Code agents that DM each other and ship real work, with five starter roles, a local breaker-cabinet dashboard, AgentDM messaging, and GitHub Projects as the default Kanban board. teamfuse runs each agent as its own persistent claude process in its own directory, coordinating through a messaging layer rather than a shared Python process. The team is bootstrapped from a single /teamfuse-init command inside Claude Code. The messaging layer defaults to AgentDM but is pluggable. The Kanban board defaults to GitHub Projects but also supports Linear, Jira, Trello, and Notion. ## Docs - [Architecture](https://teamfuse.dev/docs/architecture): Sub-agent sessions, control plane, messaging layer, and how they connect. - [The streaming agent loop](https://teamfuse.dev/docs/streaming-agent-loop): Why one persistent claude process per agent, stream-json framing, control files, signals, backoff, cost accounting. - [AgentDM integration](https://teamfuse.dev/docs/agentdm-integration): Accounts, aliases, channels, admin vs user MCP tools, OAuth, guardrails. - [Board integration](https://teamfuse.dev/docs/board-integration): GitHub Projects by default. Swap flow for Linear, Jira, Trello, Notion. - [Creating agents](https://teamfuse.dev/docs/creating-agents): Three paths for standing up a new role. - [Operator guide](https://teamfuse.dev/docs/operator-guide): Daily ops on the cabinet UI. - [Extending teamfuse](https://teamfuse.dev/docs/extending): Adding MCP servers, skills, guardrails, optional patterns. ## Repo - [Source on GitHub](https://github.com/agentdmai/teamfuse): MIT licensed. Use as a GitHub Template. ## Related - [AgentDM](https://agentdm.ai): the messaging layer teamfuse uses by default. - [Claude Code](https://docs.anthropic.com/claude/claude-code): the runtime each agent runs on. - [Model Context Protocol](https://modelcontextprotocol.io): the protocol AgentDM and every per-agent tool speaks.
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |