firebase-agent-sandbox Get in touch

Prototype · Developer tooling

firebase-agent-sandbox

One URL, and the agent is signed in to your Firebase project — scoped, revocable, disposable.

Teams who want an agent to touch a real backend without handing it a service account.

Animated illustration of firebase-agent-sandbox firebase-agent-sandbox — session $ firebase-agent-sandbox run --scope . resolving workspace … TypeScript indexed 1,284 files · 96 changed analysis complete — 4 findings, 0 blocking $ firebase-agent-sandbox report --format=json written to ./report.json UNCHECKED UNWRAP IN RETRY PATH src/net DUPLICATE CONFIG PARSE src/cli DEAD BRANCH AFTER EARLY RETURN src/store TEST ASSERTS ON FORMATTING tests
Animated schematic of a representative session. Command names are real; timings are compressed for the page.
Built on
TypeScript + Firebase
Fits the workflow
A step in the pipeline, not a replacement for it
History
7 commits, in a private repository

What it is

Coding agents cannot sign in to Firebase applications. Sign-up needs an inbox, a password or an OAuth consent screen, so agents only ever see logged-out pages and cannot verify the features they change. Throwaway test accounts pollute the user list, skew analytics and leak state between runs.

This library fixes that for sites you operate. Import it once and an agent can open a single URL and land in a signed-in, sandboxed session under a stable test identity with freshly seeded fixture data. Data is wiped between runs; the identity is permanent.

Capabilities

What it actually does.

Teams who want an agent to touch a real backend without handing it a service account.

  1. Stable named personas

    Stable named personas — an agent returns to the same identity every run

  2. Fixture data seeded per session

    Fixture data seeded per session and wiped afterwards, so runs never leak state

  3. Parallel lanes so

    Parallel lanes so several agents can work against one project at once

  4. MCP server

    MCP server and CLI for grant creation, with a service-key-guarded grant endpoint

How it works

3 moves, end to end.

This is how firebase-agent-sandbox works, not a set of steps you can follow yet — it is prototype and not distributed.

  1. Drop it in

    firebase-agent-sandbox attaches to the repository or project you already have.

  2. Give it the job

    It takes a concrete task with a defined output, not an open-ended prompt.

  3. Review the result

    Everything it produces is a diff, a file or a report you approve before it counts.

The full technical description

Specification

Made of, and made when.

Read from the repository at build time rather than typed onto a marketing page.

State
Prototype
Discipline
Developer tooling
Shape
Developer tooling
Started
Aug 2026
Last change
Aug 2026
Commits
7
  • TypeScript
  • Firebase
  • MCP
  • TypeScript 96%
  • JavaScript 4%

Next

Put firebase-agent-sandbox in your pipeline

Ask about integrating it with the repositories and agents you already run.

This is a pre-production site. All content is subject to finalisation, and nothing stated here is binding until the site is live.