Aleph

02 / LOCAL RUNTIME

Work lives on the machine.

Workspaces, files, chats, artifacts, indexes, databases, memory and local execution are part of the desktop runtime. A connected API or service is used when the user invokes a capability that needs it.

Local runtime and data boundaries
DEVICEEXTERNAL SERVICE
Local application stateSessions · workspaces · memoryFiles · indexes · artifactsSidecars · isolated compute
intentional
invocation
Connected capabilitiesRemote model APIOAuth / connectorExternal provider

Data sent to an external service is governed by that service and the connection the user authorizes.

03 / EXECUTION MODEL

From request to artifact.

This is the conceptual flow. The model reasons; an agent operates with scoped context and capabilities. Execution and persistence remain separate responsibilities.

  1. 01Configure

    Select a model, workspace or Workshop composition, and available capabilities.

  2. 02Ground

    The agent receives the relevant session context, memory and permitted tools.

  3. 03Execute

    A tool runs inside its local or connected boundary; code execution uses an isolated guest.

  4. 04Persist

    Chats, workspace state and artifacts are handled as distinct local records.

Model / inference and generation.

Agent / a configured actor that uses context and available tools inside a workflow.

Aleph / the surrounding runtime, work surfaces and boundaries.

Aleph is a local harness for the models you choose. The model layer supports a separately provisioned local Qwen 8B model and BYOK for supported external providers. Supported agent/CLI workflows include Codex and Claude Code; Aleph has also been used with Grok Build. This does not imply universal compatibility with every model or CLI. Models and agents →