Your AI development team, commanded from your phone: PM · DEV · QA · OPS ready for the next task.
Send a software goal, follow progress remotely, take over critical actions and accept the delivery; engineering runs on your authorized Windows development machine.
Not another chat. A real flow from planning and implementation to verification, delivery and human decision.
Start the control center in 5 minutes · Run a first installable, offline-capable and statically hostable PWA task in 30 minutes
Free preview · Proprietary software · Windows x64 · Local-first control plane
简体中文 · Download for Windows · V2.2.8 Preview 2 · Watch 60 seconds · Quickstart · First PWA task · Install guide · Architecture & boundaries
Important
This public repository distributes a free preview of proprietary software. It is not the CodeFlowMu source repository and does not grant an open-source license. The installer is unsigned, and the current version is a prerelease rather than a formally supported stable release.
Note
The current complete release identity is V2.2.8-preview.2. Downloads, verification and update comparison all use the complete release identity; do not use an old installer to validate current behavior.
V2.2.8 Preview 2 is available from the public GitHub Pre-release, and it is the target in the signed public Preview update manifest. Release acceptance records an isolated silent-install pass and a startup pass from the installed directory through /api/v2/health.
V2.2.8 Preview 2 improves Codex app-server agent startup and recovery: it registers an observable RunHandle before checking role-specific FCoP tools; a short preparation failure or one wait-window timeout enters recovery and continues polling, while a real subprocess exit, protocol error or explicit cancellation still settles the session as a failure. Install to a user-writable directory on an NTFS volume.
- Download CodeFlowMu-Setup-2.2.8-preview.2-win-x64.exe.
- Download SHA256SUMS.txt.
- SHA-256:
3d8c459e5636ef18bbba8538b714796d4f23fba333b5ee31cbd20a31aa3e97a9. - Customer assets consist only of the installer and
SHA256SUMS.txt; GitHub's automatic Source code archives are not installers.
CodexCliAdapter.send()returns immediately and registers an observable RunHandle instead of synchronously waiting for MCP readiness.- After
thread/start, Codex app-server checks the role's configured FCoP tools and callsturn/startonly when the tool contract is satisfied. - A
failedorcancelledreadiness result, or one 30-second wait-window timeout, records recovery evidence and continues polling in the same session. - Chat and track wakeups arriving during preparation wait on the same readiness promise and are delivered through
turn/steerafter the first turn starts. - A real subprocess exit, protocol error or explicit cancellation still settles the session; real technical failures are not reported as success.
- Restart uses the installed launcher and bundled Node, not a customer-installed npm. Pending startup recovery waits can be cancelled during shutdown.
- Switching business projects rebinds Runtime, MCP and task/report watchers. Reopening the EXE restores the previously selected project.
- Product resources come from the installation; business projects retain their own directories and ledgers. Derived Skills configuration and fact-source directories are repaired without requiring deletion of the business project.
- The header and Settings show product version, eight component versions and version history. Switching projects does not change the installed product identity.
The final V2.2.8 Preview 2 EXE passed a silent installation into an isolated directory and then started from that directory with /api/v2/health passing. This conclusion covers the install-and-start loop only; it does not claim acceptance of paid-model tasks, the full mobile workflow or a complete upgrade/rollback matrix. This remains an unsigned Preview.
In V2.2.8 Preview 2, choosing E:\CodeFlowMu means:
| Content | Default location |
|---|---|
| Application and default project root | E:\CodeFlowMu |
| Tasks, reports and collaboration files | E:\CodeFlowMu\fcop (created by initialization) |
| State, logs, Provider and update cache | E:\CodeFlowMu\data |
| Per-user project registry | %USERPROFILE%\.codeflowmu\instances\<instance-id>\projects-registry.json (paths and selection, not project source) |
Fresh installs no longer default to C:\ProgramData\CodeFlowMu or a nested projects\default. Choose a directory writable by your Windows user. Separately registered business projects retain their own paths. A fresh installation needs no data migration; historical directories are not silently removed.
To close CodeFlowMu: closing the browser only closes its interface. Right-click the CodeFlowMu notification-area icon, choose Exit CodeFlowMu, and confirm. Alternatively use Exit CodeFlowMu in the Start menu or run CodeFlowMu.exe --exit from the installation directory. This stops running tasks and disconnects the phone control surface.
An answer is not a delivery. Real software work needs scope, ownership, execution, verification, rework, evidence and a final decision. CodeFlowMu brings that lifecycle into one local control plane:
Request
→ PM clarifies, plans and dispatches
→ DEV implements + OPS runs and delivers + QA verifies and regresses
→ REPORT and runtime evidence
→ PM review
→ human approval, rejection or continuation
Tasks, reports, approvals, files, live activity and delivery evidence remain connected. The human operator can see what the team is doing, why it is doing it, what actually changed and when intervention is required.
Click the poster to play in the browser. The video uses real product surfaces: the PC control center, task tree, human gate, verification evidence and CodeFlowMu Mobile PWA. Fallback: open the 1080p MP4 directly.
The Windows distribution uses a branded installer and version-controlled full-installer upgrades. V2.2.8 Preview 2 has passed release acceptance and is present in the signed public Preview update manifest; older installed versions can discover it by its complete release identity:
First or manual installation
→ see the CodeFlowMu welcome page, product name, version and logo
→ choose the destination in the installer
→ confirm the final destination before files are written
A higher complete release version is detected
→ ask the user before downloading anything
→ the user confirms “Download and install”
→ download the full Windows installer
→ verify manifest signature, origin, size and SHA-256
→ silently apply it to the existing installation directory
→ verify the installed product version and candidate number
→ restart CodeFlowMu
Version control compares both the product version and release candidate:
V2.2.8-preview.1 < V2.2.8-preview.2;V2.2.7 < V2.2.8;- the same complete version is not downloaded again;
- an older version is never treated as an upgrade.
Only an accepted and explicitly published prerelease can become the signed update target. Drafts, local builds and unpublished candidates cannot trigger a customer upgrade. The updater preserves the existing installation directory; projects, tasks, reports and other mutable customer data must not be treated as replaceable program files.
Caution
This distribution repository is public, so customers can anonymously read the Preview update manifest and Release assets. A full upgrade runs only when the manifest's complete target version is newer than the installed version and the user confirms download and installation. Drafts, unpublished candidates and older versions do not trigger an upgrade.
A proprietary product cannot honestly claim a reproducible build from source in this repository. CodeFlowMu Distribution uses a proprietary runtime plus reviewable release evidence:
| What to verify | Evidence to inspect | Current conclusion |
|---|---|---|
| Download origin | This repository's GitHub Release and explicit version tag | Accept only the official Release, never a mirror or forwarded file |
| File integrity | SHA256SUMS.txt |
The installer hash can be recomputed independently; do not run a mismatch |
| Install and start | Checks bound to the installer hash | V2.2.8 Preview 2 silent install into an isolated directory passed; startup from the installed directory passed /api/v2/health |
| Signing and provider | Unsigned installer; Cursor uses an external sdk.v1 Provider |
Preview only, not a stable formal release; provider accounts and compatibility are managed separately |
The Release download page intentionally contains only the installer and SHA256SUMS.txt. Product inventory, module configuration, security audit and installation-acceptance details remain in the Workbench's internal version record; customers are not asked to identify or download a collection of pipeline JSON files. See the public repository readiness review and release policy for the boundary.
- Use a Windows 10/11 x64 machine.
- Download the installer and
SHA256SUMS.txtfrom V2.2.8 Preview 2. - Compare the installer SHA-256 against this candidate's record.
- Install and launch CodeFlowMu.
- Confirm that the header project root matches the chosen installation directory, then confirm initialization in Environment Preflight. Preserve errors instead of repeatedly clearing the environment. Additional business projects can be registered separately.
Verify the download in PowerShell:
(Get-FileHash .\CodeFlowMu-Setup-2.2.8-preview.2-win-x64.exe -Algorithm SHA256).HashCompare the output with this page's candidate SHA-256, ignoring case. Do not run a mismatch.
Warning
The test installer is unsigned and Windows SmartScreen may warn. The default project shares the installation directory, but application binaries, bundled runtimes and data must not be deleted or overwritten as task outputs. Provider accounts, credentials and usage charges are separate from the free preview. Installation/startup checks do not prove a real model business workflow.
The standard first task is not “Hello World.” It is an installable, offline-capable and statically hostable ShipReady PWA:
- add, complete, reopen and delete today's delivery items;
- persist data in
localStorage; - work on phone and desktop widths;
- include a Web App Manifest and Service Worker;
- open offline after the first successful load;
- use no backend, database, CDN or external API;
- deploy to GitHub Pages, Cloudflare Pages or any HTTPS static host.
Expand and copy the complete first task to PM
Build and deliver a static PWA named ShipReady.
Users can add, complete, reopen and delete “today's delivery items.” Show the total,
completed count and completion percentage. Persist data in localStorage. Support a
390px phone viewport. Include manifest.webmanifest, a Service Worker, 192/512 icons
and a README. Use no backend, database, CDN or external API. After the first load,
the app must still open and work offline.
QA must verify every behavior, refresh persistence, responsive layout, Manifest,
Service Worker, offline mode and console errors. OPS must provide a local run path.
Any public deployment requires my explicit approval before it happens; after approval,
return the deployment URL and verification evidence. PM must summarize the delivery
and every known limitation.
Next: follow Your first ShipReady PWA, step by step for screen-by-screen actions, success signals, role handoffs, the acceptance table, static deployment and Mobile PWA continuation.
| Stage | Team action | Success signal |
|---|---|---|
| Request enters | You give the brief to PM and review it before publication | A formal TASK appears in the task list |
| Plan and dispatch | PM fixes scope, acceptance criteria and child work | DEV, QA and OPS work appears in the task tree |
| Engineering | DEV creates the static site and PWA capabilities | Page, Manifest, Service Worker and icon files appear in the project |
| Run and deliver | OPS starts a local static server and records the entry point | The local URL works; any public deployment waits for approval |
| Verify and regress | QA tests behavior, phone layout, persistence and offline use | A REPORT maps PASS/FAIL and evidence to every criterion |
| Review and accept | PM summarizes results, limitations and rework | The human accepts, rejects or continues the delivery |
The example demonstrates the central principle: commands flow, evidence returns, humans decide.
| Role | Current responsibility | Work in the first PWA example |
|---|---|---|
| PM | Clarify, plan, dispatch and review | Freeze scope, acceptance criteria and the delivery conclusion |
| DEV | Implement and refactor inside an authorized project | Build UI, interaction, storage, Manifest and Service Worker |
| QA | Verify criteria, test behavior and report regressions | Test behavior, 390px layout, offline use, installability and errors |
| OPS | Run environments, deliver artifacts and record evidence | Start the static service; after approval, deploy and verify the public URL |
The human remains ADMIN: defining project scope, holding credentials, approving external writes and risky operations, and accepting the final result from reports and evidence.
CodeFlowMu is the engineering implementation in a public three-part architecture: TMPA defines governance theory and normative semantics, FCoP turns collaboration and evidence into a tool-executable protocol, and CodeFlowMu provides the Agent programming Runtime that performs real engineering work.
| System | Public position | What it contributes | What it is not |
|---|---|---|---|
| TMPA | Theory and normative governance layer | Governance objects, role/action relationships, Reader semantics and conformance criteria | An application Runtime or tool host |
| FCoP | File-based collaboration and evidence protocol | TASK / REPORT / REVIEW / ISSUE records, lifecycle semantics, references and tool entry points such as PyPI and MCP | The CodeFlowMu Runtime or a substitute for real execution |
| CodeFlowMu | Agent programming engineering Runtime | A Runtime Foundation, pluggable Execution Slots, and a controlled Capability Bus for models, Skills, MCP tools and local engineering tools | A new name for TMPA or FCoP |
The operational loop is explicit: CodeFlowMu work actions → FCoP collaboration evidence → TMPA governance reconstruction → CodeFlowMu governance use. This diagram is a public semantic view; it does not disclose private deployment topology, provider configuration, internal class names or credentials, and it does not make a new conformance claim.
Public references: TMPA A1.0 · TMPA S1.0 · TMPA–FCoP–CodeFlowMu I1.0 · FCoP · Public architecture and trust boundaries
| Path | Entry point | Use it for | Boundary to understand |
|---|---|---|---|
| Theory and specification | TMPA / Digital Employee Works | Study governance architecture, normative Core, conformance and evidence ideas | Follow that repository's own license and status |
| Collaboration protocol | FCoP | Study or implement the MIT-licensed file-based behavior-governance protocol | The protocol is not the proprietary CodeFlowMu runtime source |
| Early implementation | CodeFlowMu-open | Inspect the earlier four-role product proof and historical workflows | Maintenance-frozen; not the current product's Community Edition or Open Core |
| Current product | CodeFlowMu Distribution | Download the proprietary PC/PWA product, report issues and inspect release evidence | A free preview is not open source; the current Release contract controls |
| Ecosystem integration | Candidate future public SDKs, adapters and examples | Build integrations, adapters and templates against stable interfaces | No compatibility-backed public SDK exists today; this is roadmap only |
| Long-term product direction | Digital employee development machine | Produce, test, assemble and upgrade employee packages | Not a current capability |
This is a Spec First + Proprietary Distribution path, not a relabeling of the early open-source version as the current product's Open Core. The ideas and protocol continue while product engineering and distribution boundaries evolve; old install methods, ports, capabilities and support status do not transfer to Distribution.
| Concept | What it answers | What it cannot decide by itself |
|---|---|---|
| Role | Who owns planning, implementation, verification or operations? | A role name does not grant unlimited authority |
| Skill / Playbook | Which procedure, constraint and evidence standard should a role follow? | A Skill is not a tool and does not create execution authority |
| MCP / Tool | Which external capability can an agent connect to and call? | A callable tool does not make a task legitimate or an outcome trustworthy |
| Permission | Is this operation authorized for this project and occurrence? | Skill or MCP cannot expand it on their own |
| FCoP | How do TASK, REPORT, ISSUE and REVIEW persist and hand off? | A protocol record does not replace a real runtime result |
| Evidence | How is a real file, command, test or page demonstrated? | Evidence cannot accept business risk for a human |
| Human Gate | Who approves external writes, sensitive actions and final delivery? | Technical checks cannot replace product acceptance |
The current release ships a Skill schema, a controlled FCoP MCP execution boundary and Browser Use runtime components. A capability is usable only when the product actually ships it, the project enables it and the operation is authorized. This README does not promise automatic installation of arbitrary community MCP servers or formal support for unverified tools.
| PC control center | Task tree |
|---|---|
 |
 |
| Runtime and protocol evidence | CodeFlowMu Mobile PWA |
|---|---|
 |
 |
CodeFlowMu Mobile PWA is a remote control surface for a running PC instance, not a second product that executes independently.
Start CodeFlowMu on the PC
→ refresh Gateway and binding information on Mobile
→ bind the phone over LAN or the public Gateway
→ inspect the ShipReady task tree, role states, REPORTs and live activity
→ ask PM from the phone to “add dark mode”
→ review the second QA/OPS evidence cycle
→ handle decisions that require human approval or acceptance
Never share a QR code or bind link. Revoke lost or retired devices from the PC. The PWA, Gateway, PC product and Provider have independent version lifecycles. See the install and Mobile PWA guide.
- Windows x64 installer with bundled base Node.js/Python runtimes;
- PC control center for projects, tasks, reports, approvals, files, logs, skills and runtime state;
- fixed PM / DEV / QA / OPS team and visible task tree;
- FCoP-backed task, report, issue, review and evidence collaboration;
- human gates and project authority boundaries;
- Mobile PWA bound to a running PC;
- external Provider lifecycle plus release manifests, security and third-party license evidence.
- CodeFlowMu-branded welcome page, product logo, complete candidate identity and non-colliding installer filename;
- interactive destination selection before installation;
- update detection using both product version and release-candidate number;
- user-confirmed download, verification and installation of the full Windows installer;
- post-upgrade version verification, preservation of the current install directory and automatic restart;
- update-feed activation only after the Workbench publishes an accepted prerelease.
- V2.2.8 Preview 2 improves agent startup, FCoP tool readiness and short-failure recovery within the same session while retaining destination selection, complete-version comparison, full-installer upgrades and native exit. It is still not a stable formal release.
The “digital employee development machine” is intended to produce, test, assemble and upgrade reusable digital employee packages. It remains outside the current product promise until those capabilities ship with their own evidence, compatibility and lifecycle contracts.
- keep the public README, update manifest and each GitHub Release aligned on version, download links and hashes;
- add code signing for a formal installer;
- add real-account Cursor Provider compatibility evidence;
- continue to record versions, changes, hashes and compatibility boundaries through GitHub Releases;
- decide whether to publish SDKs, adapters and examples only after public interfaces, authority models and compatibility tests are stable.
| Public now | Evaluate after stabilization | Must remain private |
|---|---|---|
| Product ideas, architecture, four-role responsibilities and sanitized real screenshots | Versioned public APIs and a minimal SDK | Current proprietary product source and private implementation history |
| Public TMPA and FCoP specifications and project relationships | Sanitized adapter, example and template repositories | Unreleased governance experiments and private evaluation policy |
| Skill formats, layers, public templates and sanitized Playbook examples | Extension kits with explicit authority and compatibility contracts | Customer Skills, business knowledge, tasks, reports, logs and data |
| MCP's architectural position, controlled tool classes and safety principles | Security-reviewed client protocols and adapter examples | Gateway credentials, Provider keys, customer MCP configuration and private backend topology |
| Install, first-task, PWA binding and static deployment tutorials | Standalone static examples and verification tools | Signing material, release credentials, internal test accounts and private pipelines |
| Installer, hashes, manifests, third-party notices and reviewed public security evidence | Versioned compatibility matrices and migration examples | Any build or runtime material that has not passed sanitization and publication review |
The distribution repository is public, but the product is not open source. Technical checks do not complete product acceptance; each later version still requires repository-owner acceptance and explicit publication before it can become a public download or automatic-update target.
- Your first ShipReady PWA, step by step
- Install, Provider, Mobile PWA and upgrade guide
- Public architecture and trust boundaries
- 中文 README
- Release policy
- Public repository readiness review
- Support policy
- Security policy
- Proprietary software notice
Use GitHub Issues for sanitized reproducible problems. Never post API keys, bind links, customer data, private source or internal tasks. Report vulnerabilities privately as described in SECURITY.md.
Commands flow. Evidence returns. Humans decide.