Goal: Support increased autonomy in obot.agent

[jwildfire]

Add a new goal around increased autonomy for obot.agent

[obotclaw[bot]]

@jwildfire this idea is currently just a one-line title and body, so I do not have enough to write a Business Requirement and Overview without guessing.

My best reading: obot.agent (formerly safety.agent, v0.1.0 shipped 2026-07-11 per obot.roadmap#17) should be able to operate with less human-in-the-loop supervision — e.g. fewer required confirmations, longer unattended runs, or broader default permissions than it has today.

Questions:

1. Which specific behavior(s) should become more autonomous — confirmation prompts, unattended run duration/scope, permission defaults, or something else?
2. Is there a concrete trigger for this goal (an incident, a friction point, a specific workflow that is too manual today), or is it a general direction-setting goal without a specific deadline?
3. Should this land as one requirement, or is it really an umbrella goal that should spawn multiple separate requirement issues as sub-scopes get clarified?

---

This was drafted by obot ideas-triage (Claude Code headless using Sonnet 5) — review by @jwildfire

[obotclaw[bot]]

Promoted → goal issue #73 — increased autonomy in obot.agent.
Scope drawn from the autonomy arc already in flight: #18 shipped --auto v1 (maiden A1 run 2026-07-24), #58/#61 harden the triage lane, obot.agent PR #42 carries wrapup --auto + remote control; future children include grant-matrix expansion and a /goal command.
On triage's question 3: yes — this is an umbrella goal that spawns requirements as sub-scopes clarify, which is exactly what goal issues are for per your #55 decision.
Boundaries are stated on the issue: the operating contract (merge gates, carve-outs, no deletions) does not move.
Closing as resolved.

---

This comment was drafted by Claude Code using Fable 5 and reviewed by @jwildfire