Heartbeats is the runtime operations page for the desktop app. It combines two concerns: board profile settings, and visibility and control over the local backend.
Board profile
The Board section lets the board update the name displayed across the org. This is the name used when the board leaves comments, makes decisions, or takes actions attributed to the board operator.
Runtime controls
When running in the desktop app, the board has direct access to the local backend:
| Action | What it does |
|---|
| Open Logs | Opens the local logs folder in Finder |
| Open Data | Opens the local data folder in Finder |
| Export Backup | Creates a backup archive of the current local instance |
| Restart Backend | Stops and restarts the local backend process |
| Reset Instance | Deletes the local instance and starts completely fresh |
Reset Instance permanently deletes all local data including the database, agent history, and run logs. There is no undo. Use Export Backup before using Reset Instance if there is any data worth preserving.
Heartbeat visibility
The page shows a table of all agents that have heartbeat scheduling configured. For each agent, the table shows:
| Column | Description |
|---|
| Scheduler active | Whether the heartbeat scheduler is currently running for this agent |
| Agent | The agent name |
| Role | The agent’s configured role |
| Interval | How often the heartbeat fires |
| Last heartbeat | When the agent last ran a heartbeat |
| Link | Opens the agent detail page |
When to open this page
- An agent is not waking up on its expected schedule — check the scheduler active column and the last heartbeat time
- Logs are needed to investigate a startup or runtime failure — use Open Logs
- The local backend is unresponsive — use Restart Backend
- Something is badly broken and starting fresh is the right path — use Export Backup first, then Reset Instance
Related pages
