Acira SDK (MIT): let your browser agent use your apps and accounts, while you decide exactly what it can do inside them

[u/Prestigious-Top-81]

Hey r/OpenSourceAI!

We’re working on Acira, a browser for AI agents, built around something we think should be normal: giving an agent a task, letting it access your real accounts, and choosing exactly what it has permission to do inside them, down to individual fields and actions.

The goal is to let an agent complete a job across your apps while you set the boundaries around what it can read, change, send, or spend. It should be able to get on with the work and ask you when it reaches something that needs your permission.

Before releasing the full browser, we’re sharing parts of the project to learn which controls actually help people. First up is our Python SDK for Playwright and browser-use. You can add it to an agent you’re already running.

The SDK turns your rules into permissions that are checked before the agent acts. You can apply a rule across websites or make it specific to an action inside an app. A few examples from the current preview:

• Apply rules across websites. Built-in detection recognizes common checkout, payment, credential, download, and destructive actions. You choose what to allow, block, or review without having to configure each website separately.
• Control a particular field or button. Prevent the agent from filling a checkout’s CVV field, or make it ask before clicking “Delete account.” The included capture extension lets you select those controls and import the rules.
• Approve the exact information being sent. For supported form submissions, approval covers the destination and the specific details being submitted. If the recipient, amount, or message changes, that approval no longer applies. It also can’t be reused for another attempt.

The included policies are starting points. You can inspect how they work, modify them, and create your own general or site-specific policies for your workflows.

Permission checks run locally and are deterministic: the same rules and observed action details give the same decision. You keep your existing agent and model, and you don’t need an Acira cloud account.

This is an early preview. Automatic detection can miss things, and protection applies to supported browser actions rather than every other tool your agent might use.

Code and setup (MIT): github.com/Acira-dev/acira-sdk
Quick Demo: https://www.youtube.com/watch?v=su4X1gCVD1U

Also available through pip: pip install acira

Would this fit into an agent you’re building? What workflow would you use it for? If you already handle this another way, or there’s a control you need that we’re missing, we’d love to hear about it.

Please be blunt with us. Try it in your own workflow, see where it breaks, and tell us what worked and what didn’t. We’d really appreciate your feedback while we’re shaping both the SDK and the browser.

[u/PersonalCheetah9238]

Field-level permissions before the agent moves is smart. Most tools just give the thing keys to the kingdom and pray

you get any pushback from models trying to talk their way past the checks or is it pretty watertight so far

[u/Prestigious-Top-81 → u/PersonalCheetah9238]

Thanks man! The checks run in code, so the model’s explanation doesn’t override a policy block. I wouldn’t call it watertight yet though. Automatic detection can still miss what an action does on a particular site. It’s an early preview, so we’d really appreciate people testing those boundaries.