Workspace / Overview+ Send an event
YOUR AGENTS, AT WORK

Your goals. Always moving.

Follow the signals. Review the work. Decide what happens next.

Loading backendActions follow your configured policies
GOAL IN FOCUS

Loading your workspace…

Waiting for the local runtime

  1. 01 Receive an event
  2. 02 Agent investigates
  3. 03 Apply your policy
  4. 04 Inspect results
EVENTS RECEIVED—Signals in your workspace
CONFIGURED AGENTS—Persistent goals to pursue
WORK COMPLETED—Results ready to inspect
AWAITING REVIEW—Your next decisions

Your agents

Review proposed actions

Your permission, for this exact action

Work in motion

Progress and evidence from the live runtime

Received events

Including filtered and irrelevant events

Confidence is the model's estimate for its label, not a calibrated probability. Filtered or unassessed events have no score. Low confidence blocks task actions.

Activity timeline

LIVE

Send an event

Local input

Subscription rules still apply. Edit your configuration to add targets, subscriptions, tools, or schedules.

RECENT WORK
MAKE IT YOURS

Connected to your workflow

Inspect the sources, models and plugins behind your agents.

What is listening?

Configuration currently in effect

Sources collect information. Subscriptions route it to an agent. Matching events are assessed against the goal when model relevance is enabled.

Connect a source or create your own event

An event is a JSON object with a type, source, and payload. You choose names such as input.build_failed; there is no fixed list of custom event types.

Use the form below for a local message, or send the same JSON to POST /api/events with Content-Type: application/json and X-OpenDots-Request: dashboard.

JSONL: add a jsonl source with an inbox path, then append one JSON event per line. GitHub polling: add a github_poll source with a repository. Heartbeats: add a schedule. Each needs a matching target subscription. Restart after config edits.

GitHub webhooks need a signing secret and a receiver that forwards to this local runtime. Kafka, Redis, Slack, and email need an external bridge or a trusted source plugin.

Step-by-step source configuration and producer examples

Model providers

Profiles and target assignments

Loaded plugins

Capabilities available to this runtime

A loaded plugin makes capabilities available. Configure a source to connect it; inspect its connection status above.

Notifications

Destination and delivery status

Event and relevance decisions

RETAINED LOCAL CHANGE

Patch evidence