Personal agents and Playbooks

The personal agent harness

Sirro is developing a personal library of Playbooks and confirmed work facts. It gives connected agents a method to check before a task and a place to record what worked afterward. The coding library already supports saving and reusing named work across projects.

Read How work improves for the outcome and versioning loop, or For enterprise for shared company workflows.

A library of ways to get work done

An agent’s memory holds facts about you. A new chat often loses the method that worked. Sirro is designed to keep that method in a named Playbook for a connected personal agent to retrieve on the next task. Think of a weekly update, a research brief, an application, or outreach that follows your preferred steps.

This is the personal agent harness: before a task, the agent checks Sirro for a method that has worked; afterward, it records the outcome and proposes changes to the method. A Playbook describes the steps, inputs, and checks. Work facts hold details you have confirmed, such as standard answers, figures, tone, and boundaries.

Improve with evidence

1. Create a draft Playbook for a task you repeat.
2. Let an agent use it and record what happened.
3. Review the result and improve the same Playbook for next time.
4. Mark it proven only after you confirm the result or there is checkable proof.

The planned stages are draft, used, and proven. An agent's own claim of success will not make a Playbook proven. Versions let you see what changed and restore an earlier method. To avoid overwriting newer work, an agent should only edit the exact version it read.

Take the method to another agent

Your Playbooks will live in Sirro rather than one agent's chat. Connect another supported personal agent to retrieve the same approved method. The personal-agent library will be separate from your coding library, even though both belong to your Sirro account.

Your work stays yours

Personal Playbooks and work facts will stay private unless you choose to share them. Team and community sharing are planned as explicit choices, with review before work leaves your personal library. Planned company Playbooks will require a workspace owner to approve changes. Sharing a generalized Playbook with the community will be opt-in and reviewed to remove private facts. You will be able to inspect, change, restore, download, and delete what is saved.

For the features you can use now, see the coding-agent documentation. To hear when personal agents are available, join the waitlist.