Overlay Workspace

Bring people, AI agents, shared knowledge, and connected tools into one workspace for delegated work and review.

Stars
★ 197
Last updated
today
License
AGPL-3.0
Primary language
HTML

At a glance

How it runs
Web appSelf-hosted serviceHosted service
Works with
Universal · cross-platform
Cost
Free tier plus a paid hosted plan
Setup effort
High · needs real infrastructure
You'll need
Node.js 22npmConvex accountWorkOS credentialsStripe test credentialsShell / CLINetwork accessLocal filesystemMCP Server
Typical use
A researcher who needs project materials, notes, and preferences kept together can save context and ask an agent to work from it.
Not a fit if
  • Teams seeking a ready-to-use workspace without setup
  • Deployers unwilling to configure WorkOS, Stripe, or Convex
Website
getoverlay.io ↗ set on GitHub
Maintenance
Commits in the last 30 dayslast commit 2026-11-20latest release v0.1.0-rc.1 (2026-07-16) · pre-release

What does this agent do, and when should you use it?

Overlay is an open-source workspace where people and AI agents share context, with Chat for conversation and Work for tool-driven execution. Users organize chats, notes, files, and memories in projects, then retrieve saved context to support later work. Agents can use browser sessions, cloud Computers, MCP servers, and external apps connected through Composio; users can review sources, files, and tool activity in the workspace. The interface is a Next.js 15 web app, backed by Convex functions, data, and realtime sync, with support for multiple model providers. The README links to a hosted product and documents a self-hosted development path; local setup requires Node.js 22, npm, a Convex account, WorkOS credentials, and Stripe test credentials.

Users upload files, create notes and memories, and organize them in projects; Knowledge supports semantic and keyword retrieval across files and saved context. They use Chat for multi-model conversations or Work to ask an agent to call tools, browse, or carry out a task. Available operations include interactive browser sessions, persistent cloud Computers with a terminal and desktop, MCP servers, and Composio connections to apps such as Gmail, Calendar, Notion, and GitHub. The workspace also supports image and video generation, audio recording and transcription, and scheduled automations that run at intervals or daily, weekly, or monthly. After execution, users can inspect sources, files, tool activity, and generated outputs, then continue in the same context.

  1. A researcher who needs project materials, notes, and preferences kept together can save context and ask an agent to work from it.
  2. A team with recurring procedures can schedule AI workflows to run at intervals or on a daily, weekly, or monthly cadence.
  3. A user who needs an agent to interact with web pages can run browser tasks in Work mode and inspect tool activity.
  4. A team connecting AI work to office apps can use Composio integrations for Gmail, calendars, Notion, or GitHub.
  5. A user reviewing agent output can inspect sources, files, tool activity, and generated images or videos in one workspace.

Key setup facts

Pulled from the install and usage notes below. The project README has the current values.

Config files
.env.example .env.local
Runtime
Node.js 22

How do you install or deploy this agent?

Local development requires Node.js 22, npm, Convex development and production deployments, WorkOS authentication credentials, and Stripe test credentials. Copy the sample environment file, fill in the required configuration, and start the app:

npm install
cp .env.example .env.local
npm run dev

The complete environment and deployment configuration is not included here; the README points to the project's local-run and self-hosting configuration docs.

How do you use this agent?

Start the web app and open the workspace, then upload files, save memories, or create notes and organize them by project. Choose Chat for conversation or Work to have an agent use tools, a browser, or connected apps; review sources, files, and tool activity after execution. Configure an integration before asking an agent to use an external app. To run recurring work, create an automation and select an interval, daily, weekly, or monthly schedule. The README does not provide a copyable API call or first-task command.

What are this agent's strengths and limitations?

Pros
  • Chat and Work share a thread and context, so users can move from discussion to tool execution and review.
  • Memories, files, notes, and projects live in one workspace with semantic and keyword retrieval.
  • The repository documents a multi-provider model path alongside browser, cloud Computer, MCP, and Composio integrations.
  • The workspace includes scheduled automation, image and video generation, and voice transcription.
Limitations
  • Local setup involves several prerequisites, including Node.js, npm, Convex, WorkOS, and Stripe.
  • Browser, Computer, external-app, and media capabilities depend on corresponding runtime, integration, or provider configuration; availability varies by deployment.
  • The README does not specify a fixed model catalog, model prices, or provider availability for each deployment.
  • The project is under active development, and hosted and open-source versions may change; production, billing, and provider settings are environment-specific.

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Overlay Workspace This agent 59 · Major gaps Web appFreemium ★ 197 today HTML —
Row-Bot 76 · Good Desktop appFree + model costs ★ 1.7k today Python ChatGPT · Codex · Claude.ai · OpenAI API · Claude API
Bitterbot Desktop 55 · Major gaps CLIFree + model costs ★ 2.5k 1d ago TypeScript OpenAI API · Claude API
Markus AI Workforce 51 · Major gaps Desktop appFree + model costs ★ 219 today TypeScript OpenAI API · Claude API

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
59/ 100 5-point scale 3.0 / 5
Trust 17/29
Reliability 6/14
Adaptability 12/18
Convention 12/18
Effectiveness 7/13
Verifiability 5/8
Why each dimension lost points
Trust17 / 29 · 2.9/5

The protocol defines selected-root or all-user-files grants, scoped and expiring credentials, signed challenges, and request proofs. The authentication guide recommends OAuth/PKCE and describes personal tokens and access levels. The FAQ says agents act with the requesting person's access, users can inspect tool activity, account deletion requires typing DELETE, and archived items can be restored. This supports ordinary-use controls for permissions, confirmation, data-flow disclosure, and recovery. Deductions: the samples do not show the full enforcement path or confirmation behavior for every external action; data goes to the chosen model provider, whose retention rules vary; dependency-security evidence is limited; publisher identity and a verifiable source for it are unclear.

Reliability6 / 14 · 2.1/5

The protocol includes version fields, strict schemas, and request and batch size limits. The host workflow specifies cross-platform compatibility checks, and the README links to deployment and feature-status documentation. These provide some evidence of consistency. Deductions: the samples do not show how these checks cover the whole product or how dependency failures are handled in practice; availability of external services and required accounts depends on deployment; the included routes are forwarding layers and provide little evidence about the quality of failure messages.

Adaptability12 / 18 · 3.3/5

The README describes human-agent collaboration and distinguishes Chat from Work. The protocol declares adapter, recovery, platform, filesystem-grant, and concurrency capabilities. The FAQ and authentication guide also explain personal versus shared spaces and access methods. Deductions: the samples do not fully define the boundaries of every adapter, feature flag, or runtime environment; scenario coverage is useful but not detailed enough to establish fit for every workflow.

Convention12 / 18 · 3.3/5

The README clearly organizes documentation, features, repository layout, setup, and commands, with links to quickstart, API, configuration, and security material. The FAQ addresses common account and feature questions. The LICENSE text and package metadata both identify AGPL-3.0-only. Deductions: setup requires configuring services such as Convex, WorkOS, and Stripe, with instructions spread across linked documents; the sample cannot establish repository-wide naming or version stability; the project is described as actively developing, but the supplied material has no clear changelog or named maintenance responsibility and update path.

Effectiveness7 / 13 · 2.7/5

The product describes shared context, persistent memory, file retrieval, tool execution, integrations, and automation, and says users can inspect sources, files, tool activity, and outputs. This supports some practical output usability and collaboration value. Deductions: these are primarily product claims in documentation; the evidence does not quantify added value, operating cost, or setup burden, and the broad feature set depends on external accounts and services.

Verifiability5 / 8 · 3.1/5

The README points to FEATURES.md for release status and to the deployed model selector for provider details; it says API documentation is generated from shared schemas. Protocol fields and workflow configuration provide implementation details that can be checked, while the FAQ makes explicit claims about visibility and provider data transfer. Deductions: this packet is only a sample, and some product claims lack corresponding implementation excerpts; several security and utility statements remain documentation claims without sufficient corroboration in the supplied material; facts and inferences are generally distinguishable, but evidence coverage is incomplete.

Risks and how to mitigate them
  • Agents inherit the access of the person talking to them, and workspace content is visible to workspace members. Check connected apps, workspace scope, and granted access before use.
  • Messages are sent to the selected model provider, and retention rules vary by provider. Self-hosted deployments also depend on external service configuration.
Evidence confidence: Low Reviewed Nov 13, 2026 Reviewed revision c939e38dc9d5 New commits since this review; the score may not cover them
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/overlay-web.svg)](https://followagents.com/en/agents/overlay-web)
<a href="https://followagents.com/en/agents/overlay-web"><img src="https://followagents.com/badge/overlay-web.svg" alt="FARS review"></a>

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v0.1.0-rc.1 Overlay v0.1.0-rc.1 Pre-release
    Release notes excerpt
    Overlay self-hosting release candidate This release candidate packages the provider-neutral Overlay runtime for an EC2 sanity-check deployment. Recommended deployment - Guide: https://www.getoverlay.io/docs/deploy-operate/docker-ec2 - Runtime image: ghcr.io/layernorm/overlay-web:0.1.0-rc.1 - Immutable digest: sha256:a21dd700fd2c84255e44b15dbcddb4e5b9d12502b325e4d4538f0e0b422d963c - Source commit: f96f3177b1aca4cca017e64e93e18481b2054b0d …
    View on GitHub ↗

FAQ

Is Overlay free to use?
The repository is licensed under AGPL-3.0-only, and the README says LayerNorm offers a separate commercial license. Costs for models, hosting, and external services are not specified as a single price; Stripe is used for billing and subscriptions.
What services and credentials are needed to self-host?
The README lists Node.js 22, npm, Convex development and production deployments, WorkOS credentials, and Stripe test credentials. Follow the self-hosting configuration docs for the full environment setup.
Which external tools can an agent use?
The README lists browser sessions, cloud Computers, MCP servers, and Composio connections including Gmail, Google Calendar, Notion, and GitHub. Availability depends on deployment configuration.
Do scheduled workflows and external actions run automatically?
Automations can run on interval, daily, weekly, or monthly schedules. Users can inspect sources, files, and tool activity, but the README does not specify authorization scopes or retry behavior for each integration.
Is Overlay Workspace open source?
Yes. The source code is on GitHub (LayerNorm/overlay-web) under the AGPL-3.0 licence. AGPL-3.0 is a copyleft licence that also covers network use: if you run a modified version as a service, you must offer its source to users.
Is Overlay Workspace safe to use?
FollowAgents' FARS review (Nov 13, 2026) scored Overlay Workspace 17/29 on trust and safety. None of the eight safety controls the review checks for was missing outright. The repository has changed since that review.
Is Overlay Workspace still maintained?
Yes. The latest commit on GitHub is from 2026-11-20, within the last 30 days.
Who makes Overlay Workspace?
Overlay Workspace is published on GitHub by the account LayerNorm. FollowAgents has not verified which person or company is behind that account.
What is Overlay Workspace's official website?
The project's GitHub repository lists https://getoverlay.io/ as its website. That link is set by the repository owner; the source code itself is on GitHub (LayerNorm/overlay-web).
Was this page helpful?
View on GitHub ↗ Install ↓

Related concepts