← Back to Crewlo

PROJECT STATUS · 27 SEPTEMBER 2026

Know what you’re trying.

Implemented features, observed evidence and remaining validation are different things. Here is the current boundary.

Availability & validation

Current scope, not a promise of universal compatibility
AreaStatusEvidence and boundary
Windows source appAvailable in sourceLocal interface, terminal, SQLite and credential-storage checks. A clean native rebuild is not yet fully verified. Diagnostic findings.
Voxel studio & mission surfaceAvailable in sourceOwn artwork, responsive mission composer and activity labels. Populated interface captures use fixtures. Implementation notes.
Agent providersValidation variesTwelve provider presets are available. A real Codex file-reading response passed through packaged Crewlo IPC and PTY in a temporary project. This does not validate full hive routing or every provider.
TelegramBasic live exchange verified23 September: request, queue acknowledgement and named reply observed in Telegram Web. No physical-phone or every-provider claim. Transcript and scope.
WhatsAppExperimentalImplemented Meta Cloud API transport; simulated API tests. Real account-to-agent delivery remains unverified. Live-test checklist.
macOS / LinuxMac CI runtime checks passApple Silicon and Intel DMGs built on matching macOS 15 runners. SQLite, PTY and disk-image verification pass. No Apple Developer ID/notarization; DMG installation and onboarding/settings checks also pass in CI; personal-Mac permissions and live agents remain unverified. Linux runtime remains unverified. Mac report.
Windows installerPublic unsigned Windows previewFrench setup tested on the development PC. Rebuilt package passes SQLite, PTY, onboarding and settings-persistence checks. Clean Server 2022 CI installation and first-launch checks pass; personal-PC and uninstall checks remain open. Download the Windows preview. No automatic update feed. Windows report.

The 27 September full-suite run passed 961 tests with no failures and 8 skipped (969 total), including the later signing and universal-DMG regressions. Earlier baseline failures are resolved. Current validation · Later interface checks.

NEXT VALIDATION WORK · NOT RELEASED FEATURES

What is still missing?

  • A continuous, real mission recording: request, activity, any permission prompt and completed result.
  • A clean Windows installation, completed uninstall validation, signing and a separate release/update process. The local unsigned preview has already been tested.
  • Live WhatsApp delivery with real credentials, public webhook and receipt checks.
  • Provider-specific live tests, reconnect scenarios, physical-phone checks, Mac installation/UI tests and Linux runtime validation.

These are remaining work items, not scheduled releases or guarantees. Follow or contribute to the work.

FOUNDATIONS & DIFFERENCES

What belongs to Crewlo?

Crewlo is an independently maintained fork of Munder Difflin, by Chaitanya Giri and contributors. It retains the Electron, React, Pixi.js and xterm.js foundation, including agent sessions, orchestration, permissions, memory and task records.

Crewlo adds original procedural voxel artwork, its own visual identity, a responsive mission surface, activity labels derived from execution events, and paired-owner Telegram/WhatsApp transports that reuse existing sessions and delivery controls. The studio’s visual zones are not separate autonomous teams.

Engineering notes · Asset origins · MIT license · Third-party asset licenses

Local does not mean offline.

Workspace state is stored locally, but agent CLIs can send prompts and code to their AI providers. Telegram and Meta process messages through their platforms. Their data policies, subscriptions and API charges remain separate.

Messaging credentials use OS-encrypted storage, with no plaintext fallback. Conversation history is not encrypted by these integrations. Paired messaging reuses agent permissions; it cannot approve tools or resume paused delivery remotely.

Application analytics require a configured build-time key and can be disabled in Settings or with DO_NOT_TRACK. This landing page uses local assets and no analytics script. Telemetry contract · Privacy details.

Recent work

  • Interactive illustrated studio, twelve-agent scene, tabbed phone previews, Windows packaging and worktree protection, real Codex response check, and macOS packaging review. Windows evidence · Mac evidence.

  • Phone previews regenerated with larger text, full-size access and explicit evidence labels. View the change.

  • Basic Telegram request and reply recorded in the verified transcript.

Try Crewlo from source ↗

About the living studio demo

The 15-second mission is illustrated, using the actual voxel renderer with scripted agents. Its project summary was written for the website from source entry points; it is not a captured agent response. The selectable profiles and sample missions are illustrative. A continuous video of a real mission, from request to completed result, is not yet available.

The Telegram sequence quotes the documented request, queue acknowledgement and named reply observed on 23 September 2026. Its timing is condensed and the phone and studio are reconstructed; it is not continuous footage or a physical-phone test.

Capture notes and original interface tour · Return to the demo

BUILT IN THE OPEN

Small steps.
Visible evidence.

Follow the evidence behind the interface, the messaging connections and the latest changes.

OBSERVED · 23 SEP 2026

A real Telegram reply.

A basic greeting, verified in Telegram Web.

Request
Hey Remy! Say hello from the Crewlo studio in one short sentence. No file changes.
Agent reply
Hello from Remy in the Crewlo studio!

This verifies a message round trip. It does not demonstrate a completed coding task, deployment or a physical-phone test.

Read the transcript and scope
Watch the recreated phone view
Real Telegram exchange · recreated phone UI, time condensed · Transcript and verification scope

WHAT CREWLO ADDS

A studio with its own point of view.

Crewlo is an independently maintained fork of Munder Difflin. It keeps the underlying agent engine and adds:

  • Original voxel studio and figurine artwork
  • A responsive mission surface and execution-event activity labels
  • Paired-owner Telegram and WhatsApp transports with visible delivery states

Agent sessions, orchestration, memory and permissions build on the upstream foundation. Messaging validation varies by channel.

Foundations, changes & licenses
RECENT WORK · SEPTEMBER 2026

Living studio demo, public Windows and macOS previews, worktree protection and packaged runtime checks. Personal-machine and further live messaging checks remain open.

Read the commit history ↗
Help with the next small improvement ↗
All availability and verification notes