Night_Agent: a 24/7 operator with approval gates
A 24/7 background operator on a Raspberry Pi with broad authority, where anything paid or external waits for an approved request card before it runs.
Era 6, the AI-agent-native practice · Live, Phase 0 operational on physical hardware
The situation
Autonomous overnight operation sounds appealing until you ask the real question: what happens the first time the agent needs to spend money, send an email to someone outside the household, or open a pull request against production code, while you are asleep and cannot be asked? Most "24/7 agent" demos quietly skip that question. We did not think it was safe to skip, so the answer to it was built into the foundation of the design rather than bolted on later.
What we built
Night_Agent is a background operator that runs on a physical Raspberry Pi 4B (with a future path to cloud hardware). While the operator sleeps, it scans the filesystem and GitHub for work that is ready to move forward, runs the queued next steps of an existing project pipeline, consolidates the day’s activity into a persistent knowledge base (a searchable memory the agent and the operator both read from), and prepares a briefing for the morning rather than acting blind on anything ambiguous.
The approval-gate angle (this is the story)
Night_Agent’s authority is broad on purpose (real filesystem access, real GitHub access, real email access), which is exactly why the operator-approval protocol is the load-bearing part of the design, not an add-on. Any action that costs money or reaches outside the system (a paid API call, an email to a third party, a merge to a shared branch) is written up as a request card and held for the operator’s explicit approval before it executes. Routine, reversible, in-system work proceeds on its own. Anything paid or external waits for a yes.
Verified results
- Raspberry Pi 4Balways-on runtime
- GitHub, files, emailauthority granted
- Request cardrequired for any paid or external action, no exceptions
Phase 0 shipped on 2026-04-13: the Pi deployment path (SD-card preparation through a systemd service), the multi-provider language-model routing layer, and the persistent knowledge-base wiki are built and running. Later phases are scoped and queued behind named blockers the operator has to answer, not silently assumed.
What this means for your business
Unattended does not have to mean unsupervised. We can build you an operator that works while you are away and still never spends a dollar or touches the outside world without your sign-off. You get the coverage of a night shift without giving up the control of a locked door.