Palmdeck

Solo developers can run several persistent cloud agents while away from a desktop. The supplied research confirms mobile spend approval and first-party mobile agent control, but no reviewed cross-runtime command deck. None of the required runtime action interfaces is verified, and first-party mobile products narrow the window.

Palmdeck receives explicitly integrated action proposals with actor, runtime, scope, diff or payload summary, estimated consequence and expiry. Policies decide whether an action can run automatically, requires step-up approval or must be denied. Mobile approval requires authenticated intent and is bound to the immutable proposal.

Notification, authenticated approval, runtime request, acknowledgment, execution, external side effect, spend, stop request, termination readback and rollback remain separate. Idempotency can reduce duplicate requests but cannot undo a committed migration, payment or public change.

The first release should use two sandbox runtimes and reversible actions. It excludes direct production control, secret display, force operations, hidden adapters and claims of universal kill or budget enforcement.

Solo developer or small technical operator supervising multiple persistent agent runtimes and needing bounded mobile control