APPLICATIONS / POWERED BY PIONEER CLI
Four tools. Clear responsibilities.
Start from the work you need to do. These applications share an engineering philosophy, while keeping their interfaces, execution responsibilities and release status distinct.
No general commercial release, public installer channel or all-platform support is claimed here.
01 / PIONEER FLOW · ACTIVE DEVELOPMENT
Make repeatable work visible.
For workflow builders, data engineers and technical operators.
Author saved, revisioned Flows from deterministic transforms, models, scripts, control blocks and explicit approvals. Its integrated engineering chat can work with bounded Canvas context.
Review run identity, persisted outputs and execution evidence. Current Windows packaging remains subject to installed-candidate qualification; broader platform qualification is still open.
Recorded seven-block incident demonstration; synthetic operational scenario.
02 / PIONEER CHAT · OWNER-REVIEW BUILD
Current local-model qualification: synthetic conversation, center-panel crop for privacy. Separate from Flow’s integrated chat.
An engineering conversation, grounded.
For developers who want a desktop workspace over Pioneer Engineer CLI.
Choose an installed local Ollama model, converse, inspect a local Git project and prepare an owner-defined engineering task. Review frozen source and check boundaries before execution; inspect streaming activity, changes and retained evidence.
Chat uses CLI for inference and engineering authority. Conversation completion is not engineering acceptance. Current integrated delivery is implemented for owner review; public downloads and general availability are not established.
03 / PIONEER COMMAND · OWNER-REVIEW BUILD
Coordinate the work. Keep the decisions.
For engineering leads and operators managing bounded work across repositories.
Prepare a mission, review source and check boundaries, preview specialist choices, then approve a sequential queue. One-time scheduling and retained review checkpoints support deliberate operator oversight.
Native Pioneer CLI execution and consented, bounded Codex planning are distinct paths. Specialist evidence and manual overrides do not establish general architecture capability. Current UX qualification is conditional; fresh-profile startup remains an open qualification boundary.
Current UX-02 isolated mission-review fixture. The application’s provisional navigation-ring mark is not a proposed family-logo adoption.
04 / PIONEER ENGINEER CLI · ENGINEERING PROTOTYPE
A bounded engine behind the interface.
For developers and technical integrators.
The independent Python/SQLite engine performs authorized source reads and edits, tool use, approved checks, pause/resume and evidence retention. Chat and Command provide different interfaces over this engine.
Real local-model qualifications exist, with failures and partial outcomes retained honestly. Protected verification and human acceptance remain separate from model completion prose. Trusted local execution is not hostile-code operating-system isolation.
OBJECTIVE → FROZEN SCOPE → BOUNDED EXECUTION
Inspect the change. Inspect the proof.
Retained source context, tool outcomes and checks make engineering work inspectable across processes.
Illustrative execution pattern, not a fabricated terminal recording. No public package or download is offered.
Not sure where to start?
Pioneer CLI is the family’s engineering foundation, derived originally from Flow. Its improved standalone engine powers Chat and Command today; those improvements are being integrated back into Flow. Flow currently retains its own bundled backend.
Use Flow for repeatable visual workflows, Chat for a developer conversation and bounded task, Command for mission-level planning and review, and CLI as a standalone engineering engine.