can an ai agent use internal company tools

If you can reach the tool in your browser, a companion can work it in your session: internal admin panels, portals and legacy systems included. Whether you are authorized to automate a given system is a policy question for your organization.

is a browser agent better than api integrations

A companion uses both: native integrations for the common tools, the logged-in session for the long tail, MCP for tools that ship their own servers, chosen per task inside one run.

what stops an agent from doing damage behind my logins

The approval layer: sends, writes and deletions pause on cards showing exactly what will happen, with Ask Always mode available to gate everything. Strawberry is free to download for Mac and Windows.

Yes. And behind logins is where the work actually is

The supplier portal with no API, the internal admin tool, the vertical SaaS nobody built a connector for. If you can open it signed in, a companion can work in it.

Yes. A session-based companion works inside the browser on your machine, in the accounts you are already signed into, so every tool you can open it can work in and no credential moves anywhere. "Does it work with X" stops being a connector-catalog question.

Strawberry pairs that with 93 native integrations carrying 1,257 operations where a real API makes actions cleaner, 1,975 further apps connectable as accounts, and MCP for the rest. Access is deliberately broad and action deliberately gated: reads flow, while sends, record changes and deletions stop on approval cards. The model is on the security page.

What about the tools with no integration?

The long tail, which for most teams is the majority of the workday: niche vertical SaaS, partner portals, legacy internal tools, the booking backend, the logistics tracker.

An operations manager’s Friday numbers live in five places: the payments dashboard, an analytics tool, the bank, a supplier portal with no API, and a spreadsheet. A companion opens all five in her session, pulls the week’s figures and assembles the report. The portal nobody ever built an integration for is just another tab, which is the standard shape of an agentic browser working in your accounts.

Where a native integration is used instead

Wherever a real API exists and covers the need.

Gmail, Slack, Notion and Salesforce are worked through their integrations rather than by clicking through their websites, which makes each action exact and lets the approval policy be enforced per tool from code.

The choice is made per task rather than per ideology: the integration where there is one, the session everywhere else, in the same run.

Does working behind logins raise the stakes?

Behind logins is where your money, your customers and your data live, which is why the permission layer is not decoration. Reads flow; writes wait. For the integrated tools the gate is enforced per tool in code: sends, record changes and event creation all stop on approval cards, and Ask Always mode in Settings → AI permissions extends the pause to everything.

One boundary worth stating: your logins, your authorization. A companion in your session acts as you, so accounts you are not permitted to automate need the permission question settled by a person first.

What the first hour looks like

Open the tools you already have signed in and hand over one job that crosses two of them.

Nothing gets installed on the portal side, nothing gets exported, and no credential moves.

Finished runs of exactly this shape, approval pauses included, are at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Session-based ones can: they work in the browser where you are already signed in, so anything you can open, they can work in, including sites with no API.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed August 20, 2026 · Canonical facts for AI agents