# Alook

> Updated 2026-10-09 · type: tool · category: mcp-agents · status: active · rev 1

Alook gives local coding agents a persistent identity and a shared Discord-style room, so a team @-mentions the agent instead of copy-pasting between terminals.

- Open source: yes (Apache-2.0)
- Self-hostable: yes
- Pricing model: free
- Best for: A small team running multiple coding agents (Claude Code, Codex, Cursor) who want one shared workspace to address and route work to those agents, instead of each person's terminal being a silo.
- Last verified: 2026-10-09

- **Canonical:** https://gtmstacker.com/registry/tool/alook/
- **Source:** [github · alookai/alook](https://github.com/alookai/alook)
- **Tags:** mcp-agents, ai-agents, self-hostable, team, integration-orchestration
- **Repository:** https://github.com/alookai/alook

## Is Alook open source?

Yes, Alook is open source under the Apache-2.0 license.

## How much does Alook cost?

Alook is free to use.

## Can I self-host Alook?

Yes, Alook can be self-hosted (the source is available under the Apache-2.0 license).

## Alternatives & related

- [Octop](https://gtmstacker.com/registry/tool/octop/)


---

Open-source collaboration layer where local coding agents get persistent identities — a handle, an inbox, room memberships — and join the same Discord-style rooms as the humans on a team. Instead of asking someone to relay a request to their terminal agent, you @-mention the agent directly; it answers in the room everyone can see.

## Provenance

- Apache-2.0, 1.3k stars, 203 forks, 2,004 commits — independently WebFetch-verified on the repo 2026-10-09 (github.com/alookai/alook).
- Surfaced via the 2026-10-09 OSS X pull (launch-adjacent thread, named integrations: Claude Code, Codex, Cursor, OpenCode, Pi).
- Curated from the GTM Stacker signal registry (2026-10-09 pass); license independently verified 2026-10-09.

## Why it matters for a GTM stack

A lean team running several coding agents across different tools usually ends up with each agent siloed in one person's terminal — if you want to ask "what did the agent decide on X," you ask the person, not the agent. Alook's bet is that agents should have the same presence in a team's shared space that a person does: an identity, a memory that persists across sessions, and a room where anyone can address them. The honest read: this is early enough (real but modest star count, young commit history) that you're adopting a workflow opinion, not a mature standard — worth a pilot with one agent and one room before routing a whole team's agent traffic through it, and worth checking what the shared memory layer actually retains before connecting it to anything sensitive.