Skip to main content
The workbench is a read-only desktop investigation surface over the existing SQLite evidence store. It does not create synthetic sessions, run analysis with different rules, or record activity. Recording remains a CLI/operator responsibility. The workbench reports recording_supported: false and has no record button.

Build the workbench

Install the desktop prerequisites, then:
Development mode starts Vite on 127.0.0.1:1420 and launches the Tauri window. Build a release binary without an installer:
The binary is target/release/syscall-workbench.

Web UI preview (Docker)

To preview the standalone workbench UI without the desktop toolchain, run:
Open http://localhost:8080. This serves the mock/preview UI from ui/ (not the Tauri evidence-backed backend). For CLI access to mounted databases in the same stack, use docker compose exec syscall syscall --help. See Installation for details and limitations.

Open a database

The database path is fixed when the application starts:
Alternatives:
The frontend cannot supply or change a database path. The database must already exist and must use a supported schema. Read-only open does not migrate it.

Screens

Overview

Evidence posture, recent sessions, integrity distribution, latest verification, and the read-only boundary. Overview

Sessions

Searchable, sortable session browser with status, scope, loss, verification, and finding counts. Results are bounded and report the matched count. Session browser

Investigation summary

Session identity, collection accounting, evidence composition, verification, and a behavioral finding preview. Investigation summary

Processes

Observed process tree with explicit unresolved ancestry and identity markers. Selecting a node shows instance identity, lifetime, exit status, relationships, and provenance notes. Processes

Timeline

Paged event timeline with type, process, path or address search, time bounds, and an event dossier containing the recorded payload and provenance. Timeline

Filesystem

openat attempts with absolute or relative path form, flags, result, errno, and attempt semantics. Relative paths are shown as recorded. Filesystem

Network

IPv4/IPv6 connect attempts. The screen states that a successful connect does not prove an established session, data transfer, or reachability. Network

Behavioral analysis

Deterministic findings with severity, confidence, rule filters, supporting event links, related processes, next steps, limitations, and rule metadata. Behavioral analysis

Verification

Verification assessment, findings, severity distribution, and interpretation. Verification checks the stored record; it does not prove that collection was complete. Verification

Export

The destination is selected by the Rust backend. Existing files require explicit confirmation before replacement, and the result displays the component manifest. Evidence export Export result The screenshots above use the standalone renderer’s deterministic preview dataset and label the contract as ui-preview. They document the interface, not live-recorded evidence.

Interface semantics

Counts represent persisted rows. An empty category means no matching event was recorded, not that the activity did not occur.

Desktop command contract

Contract version: syscall-desktop/v2. All request fields are camelCase. Database and analysis work run on a blocking worker. Bounds and validation:
  • Session list is capped at 500; page size is capped at 500; recent overview at 20.
  • Search strings are limited to 200 characters.
  • Session IDs reject empty values, ., .., path separators, and overlong values.
  • Status, sort, direction, and address family are normalized against fixed sets.
  • get_event requires both a session ID and an event ID; a mismatched session returns no event.
  • Errors are structured as { code, message }, including SESSION_NOT_FOUND, DATABASE_NOT_FOUND, INVALID_REQUEST, STORAGE_ERROR, ANALYSIS_ERROR, and EXPORT_ERROR.

Security boundary

  • The database is opened with Storage::open_read_only; the workbench never inserts, updates, migrates, vacuums, or deletes evidence.
  • src/lib/api.ts is the only source module that imports the Tauri core API.
  • The capability grants only core:default to the main window.
  • The CSP restricts scripts, styles, images, fonts, frames, and connections to the application and Tauri IPC.
  • No SQL, shell, filesystem, dialog, or HTTP plugin is exposed.
  • Untrusted event strings render as React text. There is no dangerouslySetInnerHTML.
  • Export writes to ~/.local/share/syscall/exports/<session-id>.json or SYSCALL_EXPORT_DIR. The frontend cannot choose a path.
  • Export creates the directory with mode 0700 and the package with mode 0600.

Why there is no record button

Recording needs privileged BPF. A GUI record button would require one of:
  1. Running the whole window as root, expanding the attack surface.
  2. Embedding or caching sudo credentials, which the project forbids.
  3. A separate privileged helper with authenticated, narrow IPC.
The current design has none of these. Record with the CLI and open the result read-only.

WSLg

If the window is blank under WSLg, disable WebKit compositing:
See WSL2 compatibility for observed behavior.

Limitations

  • No automatic migration for old databases.
  • No signed installer or packaged bundle in this revision.
  • Export destination is fixed by the backend.
  • No OS-level sandbox around the renderer beyond Tauri capabilities and CSP.
  • Large sessions are paged, but the table is not fully virtualized.
  • No automated GUI end-to-end test; the renderer has component tests and the service layer has real-SQLite tests.
For the build and validation record, see Testing.