Direct Model API Routing
Configure Gemini, GPT-series, Claude, DeepSeek, or internal vLLM endpoints in the control plane. Built-in planning calls your API directly.
Submit a multi-step job in the WebUI. The built-in CEO calls the model API you configure directly to decompose work, acquire exclusive leases, and dispatch open-source executors such as Hermes. Every step is recorded in PostgreSQL so you can inspect outputs, retry failed steps, or route exceptions to a person.
Data disclaimer: test records below reflect Fidwell isolated internal test runs and have not been independently audited. Workflow steps below illustrate system architecture with sample data.
Illustrative sample workflow — inspect how task breakdown, execution isolation, and recovery work before booking a live walkthrough.
Enter the deliverable goal, repository/file boundaries, and target verification criteria in the ZeroOS WebUI.
Validates project authority rules, registers the task record in PostgreSQL, and writes an initial execution lease.
Status: QUEUED -> PLANNING · Assigned owner and target workspace logged with audit timestamp.
POST /api/tasks { "goal": "Audit 3 repos for outdated dependencies", "workspace": "readonly-mirror" }
Built-in CEO invokes your configured LLM endpoint directly (OpenAI-compatible, Gemini, or self-hosted gateway) without relying on external Hermes.
Splits the job into discrete steps with bounded file ownership and deterministic verification checks.
Each sub-task receives a unique step token and lease expiration window to prevent duplicate side effects.
step_01: scan_manifests | lease: worker-linux-03 (TTL 300s) | idempotency_key: zos-2026-8841-s1
Assigned workers (such as Hermes or containerized CLI runners) run shell, code, or data tasks inside the isolated Linux workspace.
Workers query LongMemOS via MCP to retrieve verified historical decisions and codebase constraints with source links.
Checkpoints, exit codes, and generated files stream back to the WebUI task ledger as artifacts.
mcp.call("longmemos.search", { query: "dependency pin policy", limit: 3 }) -> 3 source passages matched
If step_02 fails due to transient API timeout and caused zero side effects, ZeroOS retries automatically within the step boundary.
If verification still fails twice or touches an authorization gate, ZeroOS pauses that branch and surfaces exact logs to the operator.
Approved artifacts remain stored in PostgreSQL and your workspace file store for audit or downstream publishing.
status: NEEDS_REVIEW -> Operator approves resume -> artifact SHA-256 archived in PostgreSQL
Focused on deterministic task tracking, crash recovery, and clear ownership rather than black-box chat loops.
Configure Gemini, GPT-series, Claude, DeepSeek, or internal vLLM endpoints in the control plane. Built-in planning calls your API directly.
Distributed step leases prevent two executors from editing the same target simultaneously, while idempotency keys guard re-runs.
Task hierarchies, transcripts, tool receipts, and artifact hashes survive server restarts so long tasks resume cleanly from the last verified step.
Define read-only paths, secret isolation rules, and explicit operator handoff gates per project workspace.
Pair every execution step with shell tests, build checks, or content rules before marking a deliverable complete.
Attach LongMemOS (MemoryBox 2.0) locally over MCP so every ZeroOS executor shares exact past decisions instead of starting cold.
Agents lose project rules and debugging decisions whenever sessions reset. LongMemOS (packaged locally as MemoryBox 2.0 v2.0.4) runs inside your own Linux or Windows network and exposes a standard MCP & HTTP endpoint. ZeroOS workers, Claude Code, Cursor, and Codex read and write shared project memory anchored to exact source passages — with no built-in LLM inside the memory engine.
Figures below come from Fidwell engineering records in isolated test environments. They are not third-party certifications or hardware SLAs.
| Subject | Version / Scope | Recorded Outcome | Conditions & Boundaries |
|---|---|---|---|
| ZeroOS Control Plane Failover | Internal staging build · Nov 2026 | ~6.99s failover recovery observed | Measured on Fidwell isolated test cluster under simulated worker disconnect; network latency and hardware affect real deployments. |
| LongMemOS (MemoryBox 2.0) Recall | v2.0.4 (embedded_models=false) | 463 / 500 (92.6%) on public LongMemEval | Internal automated evaluation script on public LongMemEval dataset with external model endpoint; not independently audited. |
| Hardware Targets Verified | v2.0.4 binary release (~3.1 MB) | Win11 x86_64 · Linux x86_64 · ARM64 RK3588 | Tested on physical devices by Fidwell engineering; macOS is currently in compatibility validation. |
Choose standalone local memory or full server-hosted agent coordination.
WebUI control plane, PostgreSQL ledger, lease manager, and worker runtime connectors deployed on your Linux servers or private cloud.
Software release (~3.1 MB) or pre-configured ARM64 RK3588 local appliance for teams sharing context across coding IDEs and agents.
Full task orchestration paired with local shared memory across teams, internal codebases, and operational workflows.
No. The built-in CEO planner calls whichever model endpoint you configure, including OpenAI-compatible APIs, Google Gemini, Anthropic Claude, or private self-hosted models.
No for task planning: the built-in CEO talks to your model API directly. Open-source executors such as Hermes run as modular task workers assigned by the control plane.
ZeroOS coordinates multi-step execution; LongMemOS (formerly MemoryBox 2.0) is the pluggable long-term memory subsystem that lets ZeroOS workers and developer IDEs recall prior decisions from original records.
Yes. LongMemOS exposes a standard MCP server and local HTTP API so individual developers and teams can connect Claude Code, Cursor, or Codex directly.
Share how your team runs coding tools or internal automation today. Only your name and one contact method are required.
All consultation records go directly to Fidwell engineering support. We respond during standard business hours (UTC+8).
Email: fidwellservice@fidwell.cn
Tel: +86-411-81981709
Address: Room 1303, Bank of East Asia Tower, No. 7 Renmin Road, Zhongshan District, Dalian, Liaoning, China