Scenes

Every workflow becomes a scene — its data, its tools, the agent that runs it, and the history of everything it did. The scene is the central object in Daslab; everything else exists to fill scenes with useful state, or to react when that state changes.

Cells on top, a conversation below

A scene is a persistent, shared workspace with two halves:

  • A set of cells projecting your assets — the repo, the Sheet, the chart — at chosen sizes and positions. Each cell knows which assets it looks at and re-queries on view.
  • A conversation thread of jobs against the scene. Anyone with access to the scene sees the same cells and the same conversation history.

The answer stays on top

In a chat, the answer arrives and then scrolls away under the conversation that follows. A scene puts the answer at the top — structured, current, the same for everyone — and keeps the conversation below it, as the record of how the answer got built and the place to ask for changes.

A scene tracks one thing your team cares about: "What's happening with deploys this week." "Top accounts by ARR × their renewal dates." "Compliance status across the fleet." Each is a scene.

Properties of every scene

  • Live, not snapshots. Every cell re-queries its source each time the scene opens. Dashboards never go stale.
  • Composed of cells over shared assets. The same asset can appear in multiple scenes at different sizes and positions; the asset is shared, the cells are local.
  • Cell size affects what loads. icon-size cells skip enrichment entirely (a launcher tile costs no API quota). Larger sizes pull more data. See cells for the full picture.
  • Scoped. Tools and credentials resolve from the scene you're in. A scene holds what its workflow needs, and the agent's toolset follows.
  • Shared. Per-scene roles (owner, admin, member, viewer). Grant a team full control of one scene and read-only on another — not all-or-nothing at workspace level.
  • Persistent. A scene exists between sessions. You leave it open, come back tomorrow, the data is current.
  • Schedulable. Scenes can re-run on a cron, on an event, or on demand. The conversation continues across runs.
  • Permalinkable. Every scene has a URL. Every conversation in a scene has a permalink, backed by the commit chain. Share the trace, not the screenshot.

Scenes in practice

You can have many scenes per workspace. There's no upper limit that matters in practice. Most teams settle into 5–20 active scenes for the workflows they actually run, plus an archive of one-offs.

The agent can write back to the source systems through the scene's assets. Writes go through approval gates.

Scenes nest: a child scene appears in its parent as a cell you can peek into.

What's next

  • Assets & cells — the data, and the views on it.
  • Jobs — individual conversations within a scene.
  • Blueprints — pre-built scenes for common workflows.
  • Approvals — how writes are gated.

Updated 2026-07-18