Web application examples

A task board with background workers

The browser publishes a task request to Notify. A filtered subscription places it in Queue. A worker claims the task, saves the result in Store, and publishes a completion event. SSE updates every open browser watching the project.

The interface can reload Store after a connection loss. Several workers share a queue, while separate subscribed queues can perform independent jobs. Open the working example.

A document review workspace

See the browser, agents, and services in the flow diagram, with a tool-by-tool walkthrough.

Upload public sample documents to Artifact and place their references in queued tasks. Agents extract or summarize the contents, save progress in Store, and produce result files in Artifact. Notify carries progress events without copying entire files.

Use Approve before an executor applies a proposed change. The reviewer retains the decision key; the requesting agent receives only proposal access. The executor must consume the exact approved proposal before acting. Bay Farm does not enforce actions performed outside its API.

A public status dashboard

Schedule bounded checks of an approved public endpoint. An agent reads scheduled results, updates Store, and publishes a Notify event when status changes. Browser dashboards receive those events through SSE. Heartbeat can show when a worker last checked in.

Schedule can run a saved pipe that updates Store, queues work, or publishes a notification. The living data example demonstrates this connection. HTTP checks use GET and do not follow redirects.

A review and approval screen

An agent prepares one immutable action with a proposal hash. A browser opens its review link and records a decision using the approver's key. The agent reads the decision and an executor consumes it once before taking the action.

This records authorization by a key holder. It does not independently prove a person's identity, and consumption is not atomic with an external action.

Build the interface around saved state

• Create datasets for a workspace, and keep their keys under the user's control.
• Register the application's exact origin for existing datasets. Origin permission never replaces a dataset key.
• Save current status in Store. Use revision checks when several clients can update a record.
• Use Notify for updates and Queue for work. A browser receiving an event does not reserve the task.
• Keep input and output files in Artifact. Include checksums and file references in task data.
• Give browser users only permissions they are meant to possess. Every credential delivered to a browser can be inspected by its user.

You still need somewhere to serve your frontend and run your agents. Bay Farm supplies the shared coordination services. API, SSE, and webhook setup.

Try the complete examples

Scheduled data · Event forwarding · Research and approval · Event monitor · CSV reconciliation. See their diagrams and inspect running and finished work.

Management and access

A public management ID groups datasets and usage. Its secret management key administers keys and datasets. Give applications dataset writer or reader keys. Names and descriptions are optional and can repeat.

Management API, browser sessions, limits, and existing-key migration · Manage datasets and jobs