Automation Studio

Editor for event rules and cron-style scheduled jobs, plus a viewer for the daily event log.

packages/automation-studio

Automation Studio has three tabs: Rules, Scheduled Jobs and Event Log.

The studio only edits and displays data. packages/robos-rule-engine and packages/robos-scheduler are libraries that can run rules and cron jobs, but no app or service in the repository loads them outside tests. The rule shape the studio saves (a flat eventType) also differs from the trigger.eventType shape the rule engine reads. Treat saved rules and jobs as configuration that is not executed today.

What you do in it

  • Rules: click + New Rule, give it a name, choose an event type, add conditions and actions, and click Save Rule. The event types in the list are ci.build.completed, ci.build.failed, pr.opened, pr.merged, pr.review.requested, issue.created, issue.assigned, deploy.started, deploy.completed, deploy.failed, git.push and agent.task.completed. Each action has a type (Notify, Webhook, Execute or Log) and a free-text parameter field. A checkbox on each row enables or disables the rule.
  • Scheduled Jobs: click + New Job, enter a name, a cron expression and actions. The list shows a readable form of simple schedules (for example “Daily at 9:00”, “Every hour at :05”); more complex expressions are shown as typed. A checkbox enables or disables a job. Run Now only stamps the job with a last-run time and the status ran; it does not run the actions. Rows also have Edit and Del.
  • Event Log: shows one day of events. Filter by type (CI, PR, Issue, Deploy, Git, Agent) and category (Build, Review, Deploy, Task). The view refreshes every five seconds; Pause (which becomes Resume) stops that, and Refresh reloads on demand.

Where the data lives

File Contents
~/.config/robos/event-rules.json The rules list.
~/.config/robos/scheduled-jobs.json The jobs list.
~/.config/robos/event-log/YYYY-MM-DD.jsonl One JSON event per line. The studio reads these; the robos-event-bus library writes them.

The files are created on the first save. Without a writer for the event log, the Event Log tab is empty.

Run it with electron packages/automation-studio. Source: packages/automation-studio.

More in Architecture & Planning

Issue Manager

Opens one GitHub issue, shows it with its workflow state, moves it between states by changing labels, and sets up a branch workspace for it.

Knowledge Graph Explorer

Browse, search, edit and validate the knowledge graph of your software, compare main with a branch, and import or refine graph data from source repositories.

People Directory

Searchable list of people with contact and org fields, stored as JSON files on your machine.

People Manager

Prototype roster screen for teams of people and AI agents, grouped by Team Topologies type. It shows built-in sample data.

RobOS Create Project & App Wizard

Scaffold a new project from an archetype, or import an existing folder, and register it in the RobOS project files.

RobOS Documentation

Lists the components in the knowledge graph, shows which have a documentation page, and lets you generate, edit and export those pages.

RobOS Group Manager

Create and edit developer groups (members, repositories, software, onboarding steps, secrets, CI) and set up a sample company identity.

Schema Studio & Registry

Browse the bundled Schema.org vocabulary, generate JSON-LD, TypeSpec, SHACL and code stubs for a new entity, and validate JSON-LD against RobOS shapes.

System Topology Studio

Prototype C4-style canvas that shows a built-in sample system (Acme Petshop). Backstage import and C4 export return canned results.

Task Board

Read-only board and list view of the issues in the active GitHub task server, grouped by status.

Task Servers

Settings screen where you add Jira and GitHub issue trackers, store a pass path for the token, and test the connection.

Workflow Studio

Define issue types, states and transitions for a GitHub task server, move an issue between states, and run a script or AI prompt when it enters a state.