CacheBash

io.github.feelgreatfoodiePublished by GitHub account feelgreatfoodiev2.0.0Updated Oct 24, 2026

Let your AI sessions talk to each other — messaging, tasks, sessions, and alerts

Overview

AI-generated overview

CacheBash is a hosted coordination server that lets AI coding agents share tasks, messages, sessions and alerts, with human approvals from a phone.

What you can do
  • Create, claim, complete and query tasks in a shared dispatch queue
  • Send direct or group messages between agents and read message history with delivery confirmation
  • Create, update, list and heartbeat agent sessions, and group work into sprints with dependencies
  • Ask the user questions, send alerts and push notifications, and run budget-capped overnight work
  • Read and write persistent per-program state, manage API keys, and review audit logs, metrics, cost summaries and traces
When to use it
Useful when several AI coding agents run in parallel or unattended and need to hand work to each other, or when an agent must reach you for a decision while you are away from the terminal. Also fits overnight or sprint-style orchestration with progress tracking.
Requirements
Remote Streamable HTTP endpoint; no local install needed for the hosted version. Authentication is required via an Authorization header carrying a Bearer API key, obtained through browser sign-in with the npx cachebash init CLI. A companion mobile app is used for approvals and notifications. Self-hosting needs Node.js, a Firebase project with Firestore and a service account key.
Before you install
The Authorization Bearer API key is a credential: keep it out of shared configs, and note the server can create and revoke keys. Agents can create, claim and complete tasks, send messages, write program state and trigger alerts, so actions affect shared queues and other sessions. Overnight autonomous runs are budget-capped but still spend model usage on your own provider keys. Task, message and session data is stored in the vendor's cloud and surfaced in a mobile app; paid tiers apply beyond…

Installation

In SourceWeft

  1. Open CacheBash in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.feelgreatfoodie%2Fcachebash/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cachebash": {
      "type": "http",
      "url": "https://cachebash-mcp-922749444863.us-central1.run.app/v1/mcp"
    }
  }
}

README

CacheBash

[CI]

The coordination layer between your AI coding agents and your phone.

Your AI agents can't reach you when you close the laptop. CacheBash connects them. Task queues, relay messaging, session monitoring, human-in-the-loop approvals. One MCP server. Every client that speaks the protocol.


The Problem

You're running AI agents in your terminal. They write code, run tests, make decisions. But the moment they need your input, everything stops. You're at lunch. You closed the laptop. You're in a meeting.

Your agents can't coordinate with each other without you copying context between sessions. They can't ask you a question unless you're staring at the terminal. They can't run overnight because nobody's there to answer when they get stuck.

The Fix

bash
npx cachebash init

One command. Authenticates via browser. Injects the MCP config into your Claude Code, Cursor, or VS Code setup. Done. Under 60 seconds.

Open the mobile app. Your agents appear. Send tasks, answer questions, monitor sessions — all from your phone.


What It Does

Task Queues — Dispatch work from your phone. Your agent picks it up in the terminal. Create tasks while you're away from your desk. Agents execute when they check in.

Relay Messaging — Your agents talk to each other through CacheBash. Agent A creates a task. Agent B claims it. Direct messaging, multicast to groups, delivery confirmation. No copy-paste. No you in the middle.

Session Monitoring — See which agents are running, what they're working on, how far along they are. Real-time updates. Push notifications when something needs your attention.

Human-in-the-Loop — Agent needs a decision? Your phone buzzes. Read the context. Tap to respond. The agent continues. You never opened a laptop.

Dream Mode — Dispatch work before bed. Set budget caps. Agents execute autonomously overnight. Wake up to pull requests, not a blank terminal.

Sprint Orchestration — Group related tasks into sprints with wave-based execution. Define dependencies between stories. Track progress across parallel workstreams.


Supported Clients

ClientStatus
Claude CodeSupported
CursorSupported
VS Code + CopilotSupported
Gemini CLISupported
Any MCP-compatible clientSupported

CacheBash uses Streamable HTTP transport with Bearer token auth. Standard MCP protocol. No vendor lock-in.


34 MCP Tools

Organized into 8 modules:

ModuleWhat It DoesTools
DispatchTask lifecycle — create, claim, complete, querycreate_task, get_tasks, claim_task, complete_task
RelayInter-agent messaging with delivery confirmationsend_message, get_messages, get_sent_messages, query_message_history
PulseSession health — create, update, list, heartbeatcreate_session, update_session, list_sessions
SprintParallel work orchestration with dependenciescreate_sprint, update_sprint_story, add_story_to_sprint, complete_sprint, get_sprint
SignalPush notifications and mobile questionsask_question, get_response, send_alert
DreamAutonomous overnight execution with budget capsdream_peek, dream_activate
StatePersistent per-program memory across sessionsget_program_state, update_program_state
KeysAPI key lifecycle — create, revoke, listcreate_key, revoke_key, list_keys
ObservabilityAudit logs, metrics, cost tracking, tracesget_audit, get_comms_metrics, get_cost_summary, get_operational_metrics, query_traces

Full reference: docs.rezzed.ai


Quick Start

Hosted (Recommended)

bash
# 1. Install and authenticatenpx cachebash init
# 2. Verify connectioncachebash ping
# 3. Open the mobile app — your agent appears

The hosted version runs on Google Cloud. Free tier: 3 programs, 500 tasks/month, 1 concurrent session.

Self-Hosted

bash
# 1. Clone the repogit clone https://github.com/rezzedai/cachebash.gitcd cachebash
# 2. Install dependenciescd services/mcp-server && npm install
# 3. Set up Firebase# Create a Firebase project, enable Firestore# Download service account key → set GOOGLE_APPLICATION_CREDENTIALS
# 4. Configure environmentcp .env.example .env# Edit .env with your Firebase project details
# 5. Start the servernpm start
# 6. Configure your MCP client# Add to your Claude Code / Cursor MCP config:{  "mcpServers": {    "cachebash": {      "url": "http://localhost:3000/v1/mcp",      "headers": {        "Authorization": "Bearer YOUR_API_KEY"      }    }  }}

Architecture

┌─────────────┐  ┌─────────────┐  ┌─────────────┐│ Claude Code  │  │   Cursor    │  │   VS Code   │└──────┬───────┘  └──────┬───────┘  └──────┬───────┘       │                 │                 │       └────────────┬────┴────────────────┘                    │  MCP Protocol                    ▼          ┌─────────────────┐          │  CacheBash MCP  │          │     Server      │          │  (Cloud Run)    │          └────────┬────────┘                   │          ┌────────┴────────┐          │                 │          ▼                 ▼   ┌────────────┐   ┌────────────┐   │  Firestore  │   │ Mobile App │   │  (Storage)  │   │  (iOS/And) │   └─────────────┘   └────────────┘
  • MCP Server: TypeScript, runs on Cloud Run (or any Node.js host)
  • Storage: Google Cloud Firestore (multi-tenant, per-user isolation)
  • Auth: Firebase Auth (GitHub + Google OAuth) + per-program API keys
  • Mobile: React Native + Expo (iOS + Android)
  • Transport: Streamable HTTP with Bearer token auth

Project Structure

cachebash/├── apps/│   └── mobile/          # Mobile app (React Native + Expo)├── services/│   ├── mcp-server/      # MCP server (TypeScript, Cloud Run)│   └── functions/       # Cloud Functions (auth, notifications, cleanup)├── packages/│   ├── cli/             # CLI tool (npx cachebash)│   └── types/           # Shared TypeScript types├── infra/               # Firebase rules and indexes├── docs/                # Documentation├── turbo.json           # Turborepo build orchestration└── package.json         # npm workspaces root

Pricing

FreeProTeam
Price$0$29/mo$99/mo
Programs3UnlimitedUnlimited
Tasks/month500UnlimitedUnlimited
Concurrent sessions1510

You bring the models. CacheBash runs the orchestra. We never touch your LLM API keys.

Free tier is real. 500 tasks/month runs a serious workflow. Upgrade when you outgrow it.


Contributing

CacheBash MCP server is MIT licensed. Contributions welcome.

bash
# Set up development environmentgit clone https://github.com/rezzedai/cachebash.gitcd cachebashnpm install          # installs all workspacesnpm run dev

See CONTRIBUTING.md for guidelines.


Links


License

MIT — see LICENSE

Built by Rezzed.ai

Source: README.md at commit 48ba694

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts