$ firebase-agent-sandbox roadmap
What’s planned
Where firebase-agent-sandbox stands today, why nothing else is scheduled, and what it isn’t going to do.
Where it stands
The feature set is complete.
One URL signs a coding agent into a real Firebase project with a scoped, revocable session, isolated data lanes, a session audit trail and a way to reset. Current work is fixing and hardening what’s there: edge cases in session expiry, tenant isolation, IAM setup and error reporting.
Planned work
Nothing new is scheduled
No new features are queued. The open items in the tracker are bugs in existing behavior: edge cases in session lifetime, data-lane isolation when tenancy changes, and failed setups that say "internal error" instead of what went wrong. Those are fixes, so they aren’t listed here one by one.
Out of scope
Not on the roadmap
If you need one of these, firebase-agent-sandbox isn’t the right product for you.
-
Handing an agent a service account
That’s what it’s built to avoid. A session is scoped, time-limited and revocable. A service account key is none of those.
-
Production access
The sandbox is for a project you don’t mind an agent breaking. It doesn’t give access to a live backend.
-
Hosting your Firebase project
It signs an agent in to your project. It doesn’t host anything.
How this is maintained
Every item above is tracked in our own issue tracker, and this page is rewritten from it. Open bugs and security work are left off. Those stay in the tracker until they’re closed.
Want more detail on something here, or to know where it stands? Write to dmoore@
Next
Put firebase-agent-sandbox in your pipeline
Ask about hooking it up to the repositories and agents you already run.