Nimbus: Cloud Development Agent
A cloud development agent that understands repositories, researches technical questions, and delivers verified code changes.
- Codex
- E2B
- GitHub
- Next.js
- PostgreSQL
- Agent Workflows
The problem
Most coding agents stop at generating an answer or a patch. I wanted Nimbus to handle the complete loop: understand the repository, research when needed, make the change, verify it, and leave the user with an inspectable result.
What I built
Nimbus lets users start with a general conversation or a selected repository. It can read files, answer codebase questions, search the web, generate files and artifacts, create Mermaid diagrams, and continue the same conversation when the user later asks it to change the code.
For repository work, Nimbus provisions an isolated E2B workspace and uses Codex to inspect files, edit code, run commands, execute checks, and stream the work back to the user. Completed work can be reviewed and delivered through trusted GitHub pull-request creation, updates, merges, and closures.
Architecture
The Next.js control plane owns authentication, tenant data, conversations, model and skill selection, attachments, audit history, and trusted GitHub actions. Codex handles repository reasoning and tool use, while the executor and Eve provide durable task orchestration around each turn.
Each repository task runs in an isolated E2B workspace. The sandbox can work on the checked-out code, but GitHub credentials and publishing decisions stay in the trusted backend. PostgreSQL stores durable session state, and Cloudflare R2 stores user attachments.
Bugs I actually debugged
Bug 01
Turning a general chat into repository work
A user may begin with a normal conversation, ask about a repository later, and only then request a code change. Nimbus keeps the earlier context, identifies the repository from the conversation, and provisions a workspace only when the request actually requires one.
Bug 02
Pausing a session without losing its context
Workspaces pause after inactivity, but the conversation must remain useful. Nimbus checkpoints the workspace and conversation state, then restores the same session and Codex thread when the user sends a follow-up instead of starting from scratch.
Bug 03
Keeping agent actions safe to publish
The agent can edit code and run commands, but the execution environment should never receive the credentials needed to publish changes. Nimbus keeps credentials in the trusted backend, validates the resulting workspace changes, and performs GitHub pull-request actions through controlled server-side operations.
Results
- One conversation can move from repository questions to verified code changes without losing context.
- Users can inspect streamed work, file changes, checks, generated artifacts, audit events, and pull-request results before delivery.
- Sessions support follow-ups, selected skills, attachments, Mermaid diagrams, and pause-and-resume recovery.
- GitHub credentials remain outside the sandbox while repository changes are delivered through controlled pull-request actions.
Stack
- Frontend & Control Plane
- Next.js · React · TypeScript · WebSockets
- Agent & Orchestration
- Codex App Server · Agent Workflows · Eve · Mermaid
- Backend & Data
- Node.js · PostgreSQL · Drizzle ORM · PostHog
- Execution & Integrations
- E2B · GitHub App · Cloudflare R2