Understand the
intended workflow.

From proposal to review

gxrun is being developed as a local-first control center for applications built with AI. Its intended workflow separates creating a proposal, approving an exact plan and observing execution.

1. Prepare a proposal. An AI client or CLI describes the requested change. A proposal alone grants no authority.
2. Review the complete plan. The intended review shows the target, ordered steps, warnings, immutable inputs and complete plan hash.
3. Approve locally. Only a trusted native review or deliberate interactive CLI review on the paired Mac may authorize privileged execution.
4. Observe and reconcile. Planned run records and receipts must distinguish success, failure and unknown outcomes.

This describes design intent. Deployment, native approval and runtime behavior are not available from this site.

Different surfaces, different authority

Public website

Static information only. No account, server connection, license import or approval inputs.

Customer-local panel

Planned to run on the customer’s computer. A browser can request review; it cannot grant privileged approval.

AI and MCP clients

Planned to propose, read and dispatch already approved work within granted capabilities. AI has no approval authority.

Server panel

Planned for access through an explicit SSH tunnel. A connection does not grant deployment authority.

Planned platforms

These are intended targets, not a support promise. Release-specific downloads and tested compatibility must be published together.

Before an install guide

A release needs verified runtime behavior, trusted local approval, signed distribution and platform-specific evidence. No installation command is offered while that work remains pending.