DeepClause Web UI

Overview

The Web UI is a local-first workbench around the DML runtime. The browser supplies the editor, the agent loop, the file workspace, and the Work presentation. Inference uses the model and credentials you choose.

• No signup. Bring an API key, sign in to a supported provider, or download a local GGUF model.
• Workspace in the browser. Files, harness history, and sessions use origin-private storage (OPFS) and IndexedDB.
• No DeepClause backend. Model requests go from this browser directly to the selected provider.
• Two modes. Develop changes the harness; Work runs what the harness exposes.

Onboarding

On the first visit, an animated DeepClause hero introduces the workbench, then the setup card opens.

1. Welcome explains that files and keys stay in the browser.
2. Model selects a provider and model, accepts an API key or provider sign-in, or opens the local-model downloader.
3. Ready starts the workbench.

Until setup completes, the header controls are disabled. Your model choice and credentials are stored locally in this browser; they are not sent to DeepClause.

Home

After setup, the home screen offers two entry points:

The header shows the active model, work status, process dock, home, help, local models, and setup. Use Setup for providers, API keys, MCP servers, and storage information.

Develop

Develop is the authoring surface. The left harness tree is the navigation:

• Expand a harness to see its predicates, edit sessions, and runner sessions.
• Use the chat icon for a new edit session; the agent can inspect, edit, and run the harness.
• Use Content actions to edit the source, open the diagram, or view version history.
• Harness-row actions create, clone, export, import, grant tools, and delete harnesses.

The main pane has three views: REPL for authoring chat, Run for runner sessions, and Files for the workspace. The composer sends a message to the active session; Stop cancels its current turn.

Sessions and versions

Sessions are listed per harness. Editing sessions can be resumed; runner sessions show the typed entry point and inputs. Version history is per harness, and saving the editor creates a new commit. Renaming, cloning, importing, and exporting all preserve the harness format.

Work

Work starts with a centered harness chooser. A harness with shell/1 defines its presentation; a harness without one exposes every ordinary predicate as a workflow.

Agent and workflow harnesses

• Agent shell: the left side lists exported workflows and Work sessions. The right side is a restricted Work assistant that can use listing, reference, execute, and show_image.
• Workflow shell: the left side lists workflows and runs. The right side shows the run transcript.

Click a workflow to start it. Workflows with arguments open a centered form; workflows with a file argument open a workspace picker, where you can select an existing file or upload one before running. The selected workspace-relative path is passed to the DML goal.

Work sessions and runs

Use New session for a fresh Work conversation. Details reveals full tool calls and runtime events. If the harness gains a new version while Work is open, the header offers a refresh; idle old Work sessions are closed, while a running session can continue on its snapshot.

The harness switcher is pinned to the bottom of the left sidebar. In Work, the main surface follows the same white authoring surface and grey tree styling as Develop. Use the Shell button in the Work header to edit the shell visually: choose a conversational or workflow-only experience, write the system prompt and welcome, select host tools, and add workflows with typed arguments.

Files

Files is the durable workspace. Use the tree to open files, create new paths, upload files, download the workspace as a zip, or download the selected file. Text files open in the editor; images preview inline; other binary files are shown as downloads rather than decoded as text.

Models and credentials

Choose a model from the header picker, or open Setup for provider login and API keys. Downloaded GGUF models run locally in the browser and are listed in the same picker. Model and credential changes apply to new turns and Work sessions; a local model must be loaded before it can serve a request.

Privacy and storage

Workspace files, harness history, and sessions stay in this browser origin. Clearing site data can remove them, so export important harnesses. API keys are stored in IndexedDB and sent only to the selected model provider. The app never asks for a DeepClause API key.

Mobile

On phones, Develop uses a slide-in harness tree and Work uses a slide-in workflows/sessions drawer. The chat and run view use the full width. Controls keep touch-sized targets, and the shell respects safe areas around notches and the home indicator.

Troubleshooting

• Model requests fail: check the provider key, sign-in, and selected model in Setup. A provider catalogue probe may return a network error without blocking a configured model.
• A local model is slow or cannot load: loading a GGUF consumes browser memory; close other tabs and use a smaller quantized model.
• OAuth does not return: the provider must allow the redirect from this site. API keys and local models are alternatives.
• An old harness is still shown in Work: use the refresh indicator in the Work header after changing the harness in Develop.
• Files disappeared: check the workspace storage in Setup and avoid clearing site data; export harnesses regularly.

Links

Open the Web UI → DML language reference → DML SDK & CLI guide → pi extension →