@fresh-machine-37269 look at Automations in your VM environment and tell me how many Automations are defined, and how many are enabled. Be careful, don’t interfere, and count them right.

🤖 On it! View progress here: oss-agent-canvas.ngrok.dev/conversations/…

@fresh-machine-37269 Are you sure? Tell me how you counted. And tell me if you checked the db.

✅ Done! Yes — and I'll show my work. I did check the database. I opened the live SQLite file at

/var/lib/agent-canvas/.openhands/automation/automations.db

in read-only mode (I didn't modify anything). How I counted: 1. The

automations

table has 36 rows total. 2. 13 of those have a

deleted_at

timestamp set (soft-deleted), so I excluded them — they aren't "defined" as active Automations. 3. That leaves 23 active (non-deleted) Automations. 4. Of those 23, filtering on

enabled = true

gives 15 enabled and 8 disabled. The breakdown: So: 23 defined, 15 enabled. One nuance worth flagging: if you meant "defined" to include everything ever created (including soft-deleted rows), the raw count is 36. I interpreted "defined" as active/current Automations, which is the 23. Happy to restate it either way., with interactive elements

@fresh-machine-37269 ok give me a list of those 23 / and enabled/disabled

✅ Done! Here are the 23 active (non-deleted) Automations, grouped by state. ✅ Enabled (15) 1. Agent Canvas weekly KPI Slack summary 2. Fix Failing Version Bump (dependabot): extensions, OpenHands, software-agent-sdk, automation, enterprise 3. Friday issue closure review 4. GitHub Issue Resolver (multi-repo): extensions, OpenHands, software-agent-sdk, automation, enterprise 5. GitHub Mention Responder (multi-repo): extensions, OpenHands, software-agent-sdk, automation, enterprise 6. GitHub PR Reviewer (multi-repo): extensions, OpenHands, software-agent-sdk, automation, enterprise 7. Issue Triage (multi-repo): extensions, OpenHands, software-agent-sdk, automation, enterprise 8. Nightly Memory Curator 9. Slack Channel Monitor - All Joined Channels 10. Slack Channel Monitor - OpenHands AI Authorized 11. Stale Issue Nudge (multi-repo): extensions, OpenHands, software-agent-sdk, automation, enterprise 12. Weekly AGENTS.md relevance review (multi-repo): extensions, OpenHands, software-agent-sdk, automation, enterprise 13. Weekly Automation & Conversation Health Review 14. Weekly High-Impact Regression Hunt 15. [Docs] Release → Docs Issue → Docs PR (event-driven) ⛔ Disabled (8) 1. GitHub Issue Resolver: OpenHands/OpenHands for @all-hands-bot 2. GitHub Issue Resolver: OpenHands/extensions for @all-hands-bot 3. High-priority GitHub issue digest 4. Stale Issue Nudge — OpenHands 5. Stale Issue Nudge — software-agent-sdk 6. Weekly AGENTS.md relevance review — OpenHands/OpenHands 7. [Docs] OpenHands - Make Issue from Release Notes 8. [Docs] OpenHands - Make PR from Release Issue That's 23 total: 15 enabled + 8 disabled.

@fresh-machine-37269 on what repos runs regression hunt and conversation health? read them.

✅ Done! I read both Automations' prompts from the DB. Here's what repos they target: Weekly High-Impact Regression Hunt — runs against

OpenHands/software-agent-sdk

. Its prompt explicitly scopes it to that single repo ("Conduct a weekly regression hunt for `OpenHands/software-agent-sdk`"). Weekly Automation & Conversation Health Review — does not target any source repository. It's a read-only health/improvement audit of the shared OSS automation VM itself (

dev-oss-automation-vm

). Its data sources are local: the

automations.db

file, the

dev_conversations/

directory, the KV store, and process list — not GitHub repos. So: one repo (software-agent-sdk) for the regression hunt; no repos for the health review.