Add cron agents and logging ideas

This commit is contained in:
2026-04-07 21:05:36 +00:00
parent e1f1a24a37
commit 426ca8f1c1

View File

@@ -134,6 +134,19 @@ One-VM-per-service is overkill for trusted MCP servers but could be used for unt
- **database** — SQLite or PostgreSQL query tool
- **fetch** — HTTP fetch + readability extraction
### Cron / scheduled agents
Add `schedule` field to templates (cron syntax). Overseer checks every minute, spawns matching agents, they do their task, report to #agents, self-destruct after timeout. Use cases: daily health checks, backup verification, digest summaries.
## Logging
### Centralized log viewer
Agent logs go to /workspace/agent.log inside each VM. For a centralized web UI:
- rsyslog on host (agents send to 172.16.0.1:514) for aggregation
- frontail (`npx frontail /var/log/fireclaw/*.log --port 9001`) for browser-based real-time viewing
- Or GoTTY (`gotty tail -f ...`) for zero-config web terminal
Start simple (plain files + !logs), add rsyslog + frontail when needed.
## Infrastructure
### Agent metrics dashboard