Current

ClawWork

ClawWork is an Electron-based desktop client for the OpenClaw agent framework that manages parallel task sessions, local file persistence, and scoped configuration settings outside of chat interfaces.

Signal

ClawWork

ClawWork is a GitHub-hosted desktop application (repository: clawwork-ai/ClawWork) designed as a client for the OpenClaw agent framework. Built with Electron, TypeScript, and React, it provides a persistent workspace interface distinct from chat-based interactions (Telegram/Slack). Key capabilities include parallel task sessions, local SQLite storage for artifacts, and scoped gateway/agent settings per task. Distribution is available via Homebrew for macOS and GitHub releases.

Context

Standard chat interfaces for LLM agents often obscure state management during complex operations. Task status disappears into message streams, concurrent sessions require manual tab juggling, and generated files are ephemeral within chat history. ClawWork addresses these friction points by treating each agent task as an isolated workspace with visible tool activity, persistent file associations, and explicit approval gates for risky execution actions.

Relevance

This entry supports the Inspectable Agent Operations Circuit by moving agent control from ephemeral chat logs to a structured, browsable desktop environment. It reinforces the Local Inference as Baseline circuit by packaging agent orchestration into a local-first application rather than a cloud-dependent SaaS. The tool enables operators to maintain context across parallel workflows without losing visibility into intermediate states or outputs.

Current State

The application is in active development as of March 2026. It utilizes an Electron runtime with a SQLite database for local state management. The interface supports streaming replies, tool call cards, and progress tracking within the task window. Configuration for gateway, agent, and model settings is scoped per task rather than globally. The codebase is open-source under an MIT license.

Open Questions

  • Maintenance Cadence: Frequency of upstream synchronization with OpenClaw core updates.
  • Security Model: Implications of local file persistence and potential exposure of agent artifacts on shared systems.
  • Cross-Platform Support: Current focus is macOS; Windows/Linux parity status is undefined.
  • State Migration: Mechanisms for exporting task history between instances or for archival purposes.

Connections

  • OpenClaw: Direct integration as the underlying agent runtime framework.
  • ClawPanel: Functions as a complementary visual management interface, differing in deployment (desktop vs. cross-platform dashboard).
  • Inspectable Agent Operations: Provides the operational layer where mediation remains visible and revisable through local file and session management.

Connections

External references

Mediation note

Tooling: OpenRouter / qwen/qwen3.5-flash-02-23

Use: drafted entry from external signal, assessed linkage against existing knowledge base

Human role: review, edit, and approve before publication

Limits: signal content may be incomplete; verify primary sources before publishing