The agent calls read-only tools
It can review configuration, read metadata, sample objects, and import logs or inventory for DuckDB queries.
Storage Agent · For SRE & storage ops · Desktop · Read-only · S3-compatible
Ask an agent about your storage
Open a chat about a bucket problem, error, or log. The agent plans read-only tools, shows what it checked beside the answer, and asks before anything is downloaded or bulk-imported.
Desktop investigation agent
Chat plans the checks; evidence stays open
Describe a bucket, error, or log. The agent follows storage playbooks, runs large analyses locally, and leaves the material it used beside the answer.
Example investigation
What it checked stays beside the answer
The agent compares object metadata and content, explains a storage-class mismatch, and leaves evidence you can open before the next step.
How investigations work
How investigations work
Follow a storage investigation playbook
The agent loads a storage playbook that matches the problem and follows a known investigation path. It does not download capabilities from an extension store or run arbitrary code.
Large analyses stay local
DuckDB and rule jobs process large datasets on your machine. The agent explains the result with supporting rows and tool records open beside it.
Answers list what was used — and what is missing
Each conclusion names playbooks used, evidence used, and gaps, so a fluent answer still points at material you can open.
How a session runs
How a session runs
Ask, or pick a starting task
Describe an error, bucket, log, or cost question — or start from config review, access logs, inventory, triage, or capacity.
The agent investigates with tools
It chooses read-only checks and keeps going under simple budgets for list, preview, and latency — so you are not confirming every small read.
Results land locally; you can open them
Analysis stays in local app data. Metadata, log rows, inventory, and tool activity stay next to the answer.
You approve downloads and large imports
Anything that moves data out of the cloud asks first. Then you decide the next step with the evidence in view.
Built to investigate safely
Built to investigate safely
Keys and evidence stay on your machine
Credentials, imported evidence, DuckDB state, and chat history live in local app data. Requests go only to the model and cloud endpoints you configure.
It cannot change your storage
There are no write, delete, or bucket-policy tools. The agent can investigate; it cannot mutate production.
Confirm only when data would leave the cloud
Ordinary reads stay fast. Downloads, large scans, and evidence import always ask for approval.
What it is not
Not a full S3 browser or sync client, not multi-user SaaS, and not auto-fix or arbitrary shell.
FAQ
How is this different from a console with chat?
Consoles manage objects; chat panels wrap APIs. Storage Agent runs the investigation: plan checks, call tools, analyze locally, and show evidence — without changing production storage.
Can it change my buckets or objects?
No. Cloud access is read-only. There are no write, delete, or config-change tools.
What if I have no model API key?
Local evidence and rule analysis can still run. Add a model when you want the agent to plan and explain the investigation in chat.
How is this different from StorageOps?
StorageOps adds storage skills to Pi. Storage Agent is the full desktop app: chat, tools, local analysis, evidence, and approvals in one place.