elie222/inbox-zero

Latest recorded source activity: November 3, 2026 at 13:35

SkillsMP catalog refreshed: November 9, 2026 at 14:22

skills collected: 26

GitHub stars: 12,951
GitHub forks: 1,657

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/elie222/inbox-zero.

Repository README

Repository README source: README.md

Read the source README

Expand full README

[![](apps/web/app/opengraph-image.jpg)](https://www.getinboxzero.com) <p align="center"> <a href="https://www.getinboxzero.com"> <h1 align="center">Inbox Zero - your 24/7 AI email assistant and email app</h1> </a> <p align="center"> Organizes your inbox, pre-drafts replies, manages your calendar, and organizes attachments. Chat with it from Slack or Telegram to manage your inbox on the go. Open source alternative to Fyxer, but more customizable and secure. We also offer an email app, an open source alternative to Superhuman. <br /> <a href="https://www.getinboxzero.com">Website</a> · <a href="https://www.getinboxzero.com/discord">Discord</a> · <a href="https://github.com/elie222/inbox-zero/issues">Issues</a> </p> </p> <div align="center"> ![Stars](https://img.shields.io/github/stars/elie222/inbox-zero?labelColor=black&style=for-the-badge&color=2563EB) ![Forks](https://img.shields.io/github/forks/elie222/inbox-zero?labelColor=black&style=for-the-badge&color=2563EB) <a href="https://trendshift.io/repositories/6400" target="_blank"><img src="https://trendshift.io/api/badge/repositories/6400" alt="elie222%2Finbox-zero | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a> [![Vercel OSS Program](https://vercel.com/oss/program-badge.svg)](https://vercel.com/oss) </div> ## Mission To help you spend less time in your inbox, so you can focus on what matters most. ## Features Inbox Zero has two parts: an AI email assistant that works in the background on your Gmail or Outlook account, and an email client. Each works on its own. ### AI email assistant - **AI Personal Assistant:** Organizes your inbox and pre-drafts replies in your tone and style. - **AI Rules for email:** Explain in plain English how your AI should handle your inbox. - **Reply Zero:** Track emails to reply to and those awaiting responses. - **Bulk Unsubscriber:** One-click unsubscribe and archive emails you never read. - **Bulk Archiver:** Clean up your inbox by bulk archiving old emails. - **Cold Email Blocker:** Auto‑block cold emails. - **Email Analytics:** Track your activity and trends over time. - **Meeting Briefs:** Get personalized briefings before every meeting, pulling context from your email and calendar. - **Smart Filing:** Automatically save email attachments to Google Drive or OneDrive. - **Slack & Telegram Integration:** Chat with your AI assistant from Slack or Telegram to manage your inbox without leaving the apps you already use. ### Email client A fast email client for Gmail and Outlook, with a split inbox, all your accounts in one place, and team comments. - **Web and desktop:** open source. The desktop app is Electron, in [`apps/desktop`](apps/desktop). - **iOS:** a native Swift app, not open source yet. The [App Store app](https://www.getinboxzero.com/app) can connect to your own server URL if you self-host. - **Android:** an older React Native [Android app](https://www.getinboxzero.com/android). Learn more in our [docs](https://docs.getinboxzero.com). ## Demo [![Inbox Zero demo](https://image.mux.com/YeTrweHxCIM5tcBMXlvRbmDuPqL028lJrmJ3F6ZgwnDY/thumbnail.jpg?time=4.4&width=1280)](https://player.mux.com/YeTrweHxCIM5tcBMXlvRbmDuPqL028lJrmJ3F6ZgwnDY) ## Built with - [Next.js](https://nextjs.org/) - [Tailwind CSS](https://tailwindcss.com/) - [shadcn/ui](https://ui.shadcn.com/) - [Prisma](https://www.prisma.io/) - [Upstash](https://upstash.com/) - [Turborepo](https://turbo.build/) - [Popsy Illustrations](https://popsy.co/) ## Star History [![Star History Chart](https://api.star-history.com/svg?repos=elie222/inbox-zero&type=Date)](https://www.star-history.com/#elie222/inbox-zero&Date) ## Feature Requests To request a feature open a [GitHub issue](https://github.com/elie222/inbox-zero/issues), or join our [Discord](https://www.getinboxzero.com/discord). ## Getting Started We offer a hosted version of Inbox Zero at [getinboxzero.com](https://www.getinboxzero.com). ### Self-Hosting The fastest way to self-host Inbox Zero is with the CLI: > **Prerequisites**: [Docker](https://docs.docker.com/engine/install/) and [Node.js](https://nodejs.org/) v24+ ```bash npx @inbox-zero/cli setup # One-time setup wizard npx @inbox-zero/cli start # Start containers ``` Open http://localhost:3000 For complete self-hosting instructions, production deployment, OAuth setup, and configuration options, see our **[Self-Hosting Docs](https://docs.getinboxzero.com/hosting/quick-start)**. ### Local Development > **Prerequisites**: macOS or Linux (WSL on Windows), [Node.js](https://nodejs.org/) v24, and the pnpm version pinned in `package.json`. Install either [Docker Desktop](https://docs.docker.com/desktop/) with Compose or native PostgreSQL and Redis. On macOS, native services can be installed with `brew install postgresql@16 redis`. ```bash git clone https://github.com/elie222/inbox-zero.git cd inbox-zero pnpm install pnpm local:start ``` Open http://localhost:3000/mail and sign in with Google as `developer@example.com`, or Microsoft as `developer@outlook.test`. The Google mailbox contains demo messages. Demo users have onboarding completed, and premium checks are bypassed for local development. The command starts an isolated database, Redis and its HTTP endpoint, both mail-provider emulators, billing and email-delivery emulators, an LLM emulator, and Next.js. It applies migrations and waits for services to become ready. No OAuth credentials or AI API keys are required. AI responses are canned; this mode exercises application flows, not model quality. Existing `.env` files are left unchanged and ignored by this launcher. Generated credentials, seed data, and the current service addresses are stored under `.context/local-dev/`. Native database data stays there; Docker database data stays in a volume unique to the checkout. Restarts preserve database data and credentials. Redis caches and provider/emulator state start fresh on each run. Press **Ctrl-C** to stop the app and the services this command started. Start it again with the same command. If port 3000 is occupied, use `pnpm local:start --port 3001`. Native PostgreSQL and Redis are selected when available; use `--backend docker` or `--backend native` to select explicitly. A checkout-specific loopback port prevents concurrent launchers; the operating system releases that lock after a crash, and stale PID files are replaced automatically. Services use automatically assigned ports, so existing databases and Redis instances are not reused or stopped. Run `pnpm local:start --help` for options. If an unrelated process occupies the reported lock port, stop that process or use a different checkout location. PostgreSQL data must be opened with the same major version that created it. If you upgrade your native PostgreSQL major version, back up or move `.context/local-dev/postgres` before starting a new cluster. For development against real providers, continue to use `pnpm setup`, your own environment files, and `pnpm dev`. See the **[Contributing Guide](https://docs.getinboxzero.com/contributing)** for configuration and devcontainer setup. ## Contributing View open tasks in [GitHub Issues](https://github.com/elie222/inbox-zero/issues) and join our [Discord](https://www.getinboxzero.com/discord) to discuss what's being worked on. Docker images are automatically built on every push to `main` and tagged with the commit SHA (e.g., `elie222/inbox-zero:abc1234`). The `latest` tag always points to the most recent main build. Formal releases are tagged with the version number without the `v` prefix (e.g., git tag `v2.30.0` → `ghcr.io/elie222/inbox-zero:2.30.0`), plus a minor alias (e.g., `2.30`).

Loading the repository README…

Skills in this repository

Software Developers Software Quality Assurance Analysts & Testers Database Architects Office Clerks, General

5 occupation categories · 81% classified

skill

occupation

description

updated

pr-watch

unclassified

Take an open pull request to green — wait for CI, triage failing checks, and answer review-bot comments — using one backgrounded observation per cycle. Use when monitoring or babysitting a PR, waiting on checks or review bots, or addressing PR review feedback.

2026-11-03

cloud-dev-environment

unclassified

Cursor Cloud VM setup and service startup instructions for local development

2026-10-22

create-pr

unclassified

Review the working tree, commit it safely, and open a GitHub pull request. Use when the user asks to create, open, raise, or publish a PR, or to finish changes as a PR. For watching an existing PR — CI, review bots, failures, comments — use the pr-watch skill…

2026-10-21

llm

unclassified

Guidelines for implementing LLM (Language Model) functionality in the application

2026-10-19

logging

unclassified

How to do backend logging

2026-10-06

testing

Software Quality Assurance Analysts & Testers

Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features

2026-09-23

inbox-zero-mcp

Office Clerks, General

Search Inbox Zero mail, read threads, create mailbox drafts, and manage automation rules through a remote MCP server. Use when the user wants ChatGPT, Claude, or Cursor to work with their Gmail or Outlook inbox.

2026-09-17

update-packages

Software Developers

Update workspace packages while respecting the repo's pinned package list in .ncurc.cjs. Use when the user asks to update dependencies or refresh package versions.

2026-09-11

test-feature

Software Quality Assurance Analysts & Testers

End-to-end feature testing — browser QA, API verification, eval tests, or any combination. Covers browser interactions (via agent-browser CLI), Google Workspace operations (gws CLI), API calls, and LLM eval tests. Can also persist checks as reusable automated…

2026-09-02

code-simplifier

Software Developers

Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.

2026-05-05

review-ai-prompt-changes

Software Developers

Review prompt and tool-description changes in a branch or PR. Use when asked to audit system prompts, prompt builders, tool descriptions, prompt inputs, or nearby evals/tests; summarize what changed; identify guidance that feels eval-shaped or too heavy for…

2026-04-22

changelog

Software Developers

Add a new changelog entry to docs/changelog-entries/

2026-04-16

qa-label

Software Quality Assurance Analysts & Testers

Label a PR as ready for QA so the QA server picks it up automatically

2026-03-25

agent-browser

Software Developers

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include…

2026-03-23

llm-test

Software Quality Assurance Analysts & Testers

Guidelines for writing tests for LLM-related functionality

2026-03-22

inbox-zero-api

Software Developers

Use the Inbox Zero API CLI to inspect the live API schema, list and manage automation rules, and read inbox analytics through the public API. Use this when a task involves Inbox Zero rules, stats, or API-driven automation and can be solved through the CLI…

2026-03-18

review

Software Quality Assurance Analysts & Testers

Review code changes, auto-fix safe issues, and report bugs

2026-03-17

e2e

Software Quality Assurance Analysts & Testers

Run and debug E2E flow tests. Use when triggering E2E tests, checking test status, debugging failures with Axiom logs, or setting up local E2E testing.

2026-03-13

fullstack-workflow

Software Developers

Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.

2026-03-13