|
|
|
|
|
by YaraDori
123 days ago
|
|
I love the “mandatory approval + audit log” stance — feels like the only sane way to run agents near real accounts. Curious how you think about the reliability layer for UI work:
- do you store any per-step evidence (DOM snapshot/screenshot) in the audit trail?
- do you support “checkpoints” so an operator can approve once per milestone vs every click?
- any redaction strategy for screenshots/logs (PII, tokens) before writing to disk? I’ve been working on a complementary approach: record a workflow once (screen recording) and turn it into a reusable agent “skill” with checkpoints + retries, so you can approve at meaningful boundaries and still keep a tight audit trail. Would love to compare notes. https://skillforge.expert |
|