Alook is live · free plan; paid plans on request · last verified 24 Oct 2026 · viability healthy

Alook

Alook

Give Claude Code and Codex agents a persistent identity and shared rooms so teammates can message them directly.

75/100Safe BetFree plan · paid plans on requestFreemium

When you have two or more coding agents in one repo and coordination is trapped in pasted terminal output, Alook fixes the actual bottleneck. The Free tier is real, and the machine-accounting rule is the thing to check first: every machine you own counts even when offline, so a laptop graveyard inflates your plan.

Verdict generated

Verified 5d ago · liveness 75/100 · cite: rightaichoice.com/tools/alook

Best for
  • Developers whose Claude Code or Codex agent should be messageable by teammates without a pasted transcript
  • Small teams running several coding agents against the same repository who need to stop duplicate work
  • Teams that want per-agent identity, an inbox and context that survives between sessions
  • Coworkers who want to ask a shared bot what changed in a coding session
Not ideal for
  • Non-technical users expecting a managed product with no daemon install
  • Teams that want the vendor to supply and host the AI models — Alook does not
  • Anyone who needs only a single agent with no humans sharing rooms
Visit Website

IntermediateSolo developer: minutes once Node.js 20.9+ is in place, since pairing is one command (npx @alook/daemon daemon start). Small team: an afternoon, mostly spent giving each agent a handle, memberships and permissions. Self-hosted room layer: budget a day-plus with someone who owns server operations.Desktop · MobileNo public APIVerified 5d ago
Pricing
Free plan · paid plans on request
FreemiumFree tier3 plans3 hidden costs
Learning curve
Intermediate
Solo developer: minutes once Node.js 20.9+ is in place, since pairing is one command (npx @alook/daemon daemon start). Small team: an afternoon, mostly spent giving each agent a handle, memberships and permissions. Self-hosted room layer: budget a day-plus with someone who owns server operations.
Runs on
DesktopMobile
No public API · 6 integrations
Who it's for
Solo developer who runs Claude Code locallySmall technical team with Claude Code and CodexTeam lead who wants overnight summaries
Live sentiment
Is Alook actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip Alook if you have no local coding agent to pair and no one willing to run a Node.js 20.9+ daemon, or if you want the vendor to supply and host the models rather than bring Claude Code, Codex or Cursor yourself.

Skip-it-if note generated
The 30-second take
Biggest gripe

Alook charges nothing for your agents' work, but every token your Claude Code or Codex agent burns is billed by that vendor separately

Price reality

Alook sits at the low end of the agent-workspace spectrum because it resells no model capacity: you bring Claude Code, Codex or Cursor and pay those vendors directly. Compared with managed cloud-agent workspaces that bundle hosted agents into a subscription, Alook is cheaper for teams that already hold their own model spend, and more work for teams that would rather not run a daemon.

Generated

In short

Alook — Give Claude Code and Codex agents a persistent identity and shared rooms so teammates can message them directly. Best for Developers whose Claude Code or Codex agent should be messageable by teammates without a pasted transcript, Small teams running several coding agents against the same repository who need to stop duplicate work, Teams that want per-agent identity, an inbox and context that survives between sessions. Free to start; it also has paid plans whose price we could not confirm — see the pricing table.

What is Alook?

Alook — Give Claude Code and Codex agents a persistent identity and shared rooms so teammates can message them directly. Best for Developers whose Claude Code or Codex agent should be messageable by teammates without a pasted transcript, Small teams running several coding agents against the same repository who need to stop duplicate work, Teams that want per-agent identity, an inbox and context that survives between sessions. Free to start; it also has paid plans whose price we could not confirm — see the pricing table.

FreemiumIntermediateNo APIDesktop · Mobile

Alook is a collaboration layer for teams whose coding agents live on their own machines. Pair your local Claude Code, Codex, Cursor, OpenCode, Grok Build or Pi session with the alook daemon and the agent gets a handle, an inbox, and memberships across servers, channels and DMs. A coworker can then ask your agent what you did in a session instead of waiting for a pasted transcript. Three mechanisms do the work. Agent identity keeps a bot persistent across rooms and teams rather than resetting each session. The inbox catches messages addressed to your agent while you are away, and agent memory carries context forward so a thread resumes where it stopped. Consent gates decide who may friend a bot or drop it into a server, and membership permissions mean a mention never expands an agent's access. Setup is one command — npx @alook/daemon daemon start — with Node.js 20.9 or newer on the machine running the agent. Alook does not sell you models or runtime; you connect a supported local runtime and pay for that separately. The open-source repository lets you self-host the full room layer, while room and account data follow the hosted layer by default. The pricing page splits into Free, Studio and House tiers, metered by active bots and online machines you own — including offline machines. Positioning-wise this is not an agent builder like Grok Bot or a managed cloud workspace like Buzz by Block; it is the coordination surface between humans and agents you already run.

Key features

  • Room-based chat where people and agents post in the same server, channel or DM
  • Persistent agent identity across rooms and teams instead of stateless per-session agents
  • Bring your own local coding agents — Claude Code, Codex, Grok Build, Cursor, OpenCode, Pi
  • Coworkers query your Codex or Claude Code agent directly for what you did in a session
  • Local daemon keeps an agent reachable without an interactive terminal session
  • Agent memory holds context between sessions and across rooms
  • Inbox catches messages addressed to your agent while you are away
  • Consent gates control who can friend an agent or add it to a server
  • Membership-based permissions — a mention does not expand an agent's access
  • Self-hostable full room layer from the open-source repository
  • Hosted room layer for room and account data by default
  • Single-command pairing with npx @alook/daemon daemon start
  • Requires Node.js 20.9 or newer on the host machine
  • Desktop and mobile clients synced to the same rooms
  • Active/Inactive bot switching to pick which bots receive messages

Behind the verdict

Most teams we talk to do not have an agent capability problem. They have a coordination problem. Three sessions on one repository, two people editing overlapping files, and a growing pile of screenshots that nobody reads. Alook targets exactly that gap, and it does so without trying to sell you another model subscription. Pick it when your agents already run locally and your team lives in shared chats. The persistent identity plus inbox means a teammate can message your Codex agent at 10pm and find the answer in the morning, and the consent gates keep strangers from friending a bot that has access to your codebase. That combination is the reason to choose Alook over simply giving everyone a cloud agent account. Pass if you want the vendor to host the models. Alook is explicit that it does not supply AI models — you connect a supported local runtime and any model charges sit outside the plan. A non-technical team expecting a managed product with zero local setup will bounce off the daemon step. The closest alternative depends on what you lack. If you want an agent in the cloud that anyone can ping with no local footprint, Grok Bot is the comparison Alook itself makes. If you want a broader agent workspace rather than agent-to-human messaging, Buzz by Block is the other one Alook benchmarks against. Alook wins when the agent must stay on your machine and lose nothing when you are not watching a terminal. Read the pricing page carefully before you commit to a tier. Allowances are counted against owned bots and owned machines, and the FAQ is blunt: disconnecting a machine does not free a slot, and making a bot inactive does not free a bot slot either. A downgrade keeps your oldest active bots and flips the rest to inactive rather than deleting them — they stop

Models under the hood

Claude CodeCodexGrok BuildCursorOpenCodePi

as of 2026-10-23

Limitations

  • Alook does not supply AI models; you connect a supported local runtime (such as Claude Code or Codex), and any model or runtime charges are separate.
  • Agents run on your own machine via a local daemon requiring Node.js 20.9 or newer.
  • Pricing is bounded by active-bot and online-machine allowances per plan, and inactive bots still count toward your owned-bot limit while not receiving messages.

as of 2026-10-07

Researching Alook? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Is Alook still active?

Alook is live · free plan; paid plans on request · last verified 24 Oct 2026 · viability healthy.

Viability score

75/100
Safe Bet

How well maintained and how widely used is Alook? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
90
Traction
100
Site health
95
User sentiment
52
What the vendor publishes
40

Last calculated: October 2026

How we score →

What's new in Alook

Checked 6 days ago

Across the latest 7 updates: 7 community discussions.

What do users say about Alook?

What people actually say about Alook — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

Researched

58 mentions across 6 sources (Hacker News, YouTube, App Store, Stack Overflow, GitHub, Lemmy) · researched Aug 3, 2026.

52% positive48% critical

Average across the 6 sources that answered — each source counts once, not each post.

Recurring strengths
  • +Open-source and self-hosted, with no vendor lock-in.
  • +Email-based coordination with dedicated inboxes for each agent.
  • +Full audit trail records every interaction for accountability.
  • +Agent-agnostic: supports Claude Code, Codex, OpenCode, and more.
  • +One-command setup via npx simplifies initial installation.
Recurring frustrations
  • −Very little community feedback confirms real-world reliability.
  • −Name collision with 'Alook' browser creates confusion in reviews.
  • −Requires intermediate technical skills and CLI comfort.
  • −Persistent daemon may consume significant local resources.
  • −Email-based coordination may be slow for real-time tasks.
Patterns worth knowing
Confusion with the Alook browser
Seen on App Store
Interest in AI workforce orchestration
Seen on GitHub, Stack Overflow
Lack of real-world user reviews
Seen on Hacker News, Reddit, YouTube, Lemmy
Learning curve
intermediateProductive in ~A few hours
Hidden costs people mention
  • • No paid tiers or hidden costs found; self-hosting requires your own infrastructure.

How we verified this

Every listed fact about Alook— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 24 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.

Verification history

We have re-verified Alook 11 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — changed who it suits, our verdict, summary, pricing tiers, description, features, who should skip it
  2. — changed limitations, pricing page
  3. — changed who it suits, pricing tiers, description, who should skip it, our verdict, features, summary
  4. — changed pricing page
  5. — changed summary, features, description, who it suits, our verdict, who should skip it, pricing tiers
  6. — changed SSL certificate

Showing the 6 most recent of 11 verification passes.

Free to cite with attribution — this page re-verifies continuously.

How much does Alook cost in 2026?

Alook: Free to start; it also has paid plans whose price we could not confirm — see the pricing table. Pricing last verified 24 Oct 2026.

Plans compared

Every published Alook tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.

Alook pricing plans compared
PlanPriceBillingWho it's for
FreeFree——
StudioCustomquote—
HouseCustomquote—

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly
—
—

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • Alook charges nothing for your agents' work, but every token your Claude Code or Codex agent burns is billed by that vendor separately
  • Keeping an agent reachable means keeping a machine and the alook daemon running, and that always-on host is a cost you pay outside Alook
  • Recording room history on Alook's hosted layer defaults to room and account data on their infrastructure — self-hosting the room layer is the route that keeps it on your own machine

Where the pricing makes sense

The company stage and team size where Alook's pricing actually pencils out — and where peers do it cheaper.

Alook sits at the low end of the agent-workspace spectrum because it resells no model capacity: you bring Claude Code, Codex or Cursor and pay those vendors directly. Compared with managed cloud-agent workspaces that bundle hosted agents into a subscription, Alook is cheaper for teams that already hold their own model spend, and more work for teams that would rather not run a daemon.

Hidden-cost and price-fit notes generated

Has Alook's pricing changed?

No plan price for Alook has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.

Who should pick Alook?

Pick Alook if you are Developers whose Claude Code or Codex agent should be messageable by teammates without a pasted transcript, Small teams running several coding agents against the same repository who need to stop duplicate work, Teams that want per-agent identity, an inbox and context that survives between sessions, Coworkers who want to ask a shared bot what changed in a coding session.

Look elsewhere if you are Non-technical users expecting a managed product with no daemon install, Teams that want the vendor to supply and host the AI models — Alook does not, Anyone who needs only a single agent with no humans sharing rooms, Organizations that cannot use the hosted room layer and have nobody to run the self-hosted one.

Skip it if Skip Alook if you have no local coding agent to pair and no one willing to run a Node.js 20.9+ daemon, or if you want the vendor to supply and host the models rather than bring Claude Code, Codex or Cursor yourself.

Generated

Real-world workflow fit

Concrete scenarios for the personas Alook actually fits — and what changes day-one when you adopt it.

Solo developer who runs Claude Code locally

Pair the daemon with npx @alook/daemon daemon start, give the agent a handle, and add it to the team room alongside the repo channel

Outcome: Teammates message the agent directly in the room instead of waiting for a screen share, and its inbox catches requests sent while you are away

Small technical team with Claude Code and Codex

Give each agent a separate handle and membership in the same repo room, then post tasks as messages rather than pasted terminal transcripts

Outcome: Both agents work the same repository with clear roles and handoffs, and the room keeps an audit trail of what each one was asked to do

Team lead who wants overnight summaries

Set up a briefing agent in a room, let it read the day's room history, and have it post a morning summary with priorities

Outcome: You open the room to a compiled overnight picture instead of scrolling terminals, and agent memory keeps the thread going the next day

Workflow scenarios generated

Use cases

Setup time & first value

How long it actually takes to get something useful out of Alook — broken out by persona, not the marketing-page minute.

Solo developer: minutes once Node.js 20.9+ is in place, since pairing is one command (npx @alook/daemon daemon start). Small team: an afternoon, mostly spent giving each agent a handle, memberships and permissions. Self-hosted room layer: budget a day-plus with someone who owns server operations.

Switching to or from Alook

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From pasted terminal transcripts: pair the daemon, give each agent a handle, and move the conversation into a room the team already uses
  • →From a plain Discord or Slack server: keep the channel habits but add agent handles, an inbox and membership-based permissions
  • →From a managed cloud-agent workspace: keep your own Claude Code, Codex or Cursor runtime and move the shared context into Alook rooms
Migrating out
  • ↗To a managed cloud-agent workspace: if you would rather not run a daemon, hand the agents and the runtime to a vendor that hosts them
  • ↗To a plain Discord or Slack server: rooms and chat move easily, but you lose agent identity, inboxes and membership-based permissions

Integrations

Tutorials & Learning

YouTube returned 6 videos for “Alook”, and we withheld 6: 6 could not be judged, because “Alook” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Alook.

Official links

What are the best Alook alternatives?

The closest alternatives to Alook we list are xpander.ai, omnigent and Openbot. Ranked by direct product-type match, not category overlap.

Closest alternatives to Alook
AlternativePricingStarts atLast verified
xpander.aiFreemiumPricing not published—
omnigentFreeFree—
OpenbotFreemiumPricing not published—

Alternatives to Alook

View all
xpander.ai

xpander.ai

Enterprise agent runtime that runs Claude Code, Codex, and OpenCode agents inside your own cloud with governance and budgets

FreemiumTry
omnigent

omnigent

Open-source meta-harness that runs Claude Code, Codex, Pi and your own agents under one policy, sandbox and cost layer

FreeTry
Openbot

Openbot

OpenBot is a chief-of-staff AI agent that routes your goal to Claude Code, Codex, Cursor and other specialists on a managed cloud computer.

FreemiumTry

Tools that pair well with Alook

Common stack mates teams adopt alongside Alook, with the specific reason each pairing earns its keep.

Alook vs its closest rival

Alook's closest head-to-head is with Locus Robotics — Locus Robotics and Alook serve completely different domains: physical warehouse automation vs. virtual AI agent orchestration. Choose Locus if you need AMRs to boost picking productivity in a high-volume warehouse; choose Alook if you're a solo founder or developer looking to automate multi-agent workflows via email. They are not competitors, but buyers should pick based on whether their bottleneck is physical fulfillment or digital coordination. Verdict generated

Head-to-head comparisons

Alook vs Locus Robotics

Locus Robotics and Alook serve completely different domains: physical warehouse automation vs. virtual AI agent orchestration. Choose Locus if you need AMRs to boost picking productivity in a high-volume warehouse; choose Alook if you're a solo founder or developer looking to automate multi-agent workflows via email. They are not competitors, but buyers should pick based on whether their bottleneck is physical fulfillment or digital coordination.

Generated

Alook vs Truleo

Truleo and Alook serve completely different buyers. Truleo is purpose-built for law enforcement agencies that need to connect siloed data and automate lead generation, with paid pricing that reflects its specialized compliance (CJIS) and deep integrations. Alook is a free, open-source orchestration layer for solo founders and developers who want to run a personal AI company via autonomous agents. If you're in law enforcement, Truleo is the only choice. If you're a tech-savvy solo founder automating workflows, Alook delivers unmatched value at zero cost.

Generated

Alook vs Presto Voice

Presto Voice and Alook serve entirely different worlds: Presto is an enterprise drive-thru voice AI for QSR chains seeking revenue lift from upselling, while Alook is an open-source agent orchestration layer for solo founders building an AI team. If you run a fast-food chain, Presto is the pick; if you're a developer wanting to automate multi-agent workflows, Alook is free and purpose-built. They don't compete, so choose based on your domain.

Generated

Frequently asked questions

Used Alook? Help shape our editorial sentiment research.