Titpea
Reads the whole account
S3, IAM, KMS, CloudTrail, Config and more: only operations that read.
Storage Agent Object storage agent
Find what’s wrong in S3.
Ask about your S3 storage in plain words. The agent reads what the services return and never changes anything; fixes are yours to run.
- macOS / Windows / Linux
- S3-compatible
- Apache-2.0
- Oct 30, 2026
Every read, shown and kept
Every step opens
Open any call to see exactly what the agent received.
Questions over many objects
A sandboxed script lists, counts and reads object bodies, with no network.
Logs and inventories as tables
Access logs, CSV, JSON or Parquet become local SQLite tables, every column kept.
Remembers between tasks
It saves notes as JSON and looks them up when needed; they survive app updates.
Where your data goes
- Keys are sealed in the system keychain, or an encrypted local file; an AWS profile account stores only its name.
- Tasks, datasets and memory stay in SQLite files on this machine. Account IDs never reach the model, the window or a log.
- Requests go only to the model and endpoints you configure; packaged builds also check GitHub Releases for updates. No telemetry.
FAQ
Does it need a model?
Yes. Every read goes through the agent, so without a model the window asks for one. OpenAI, Anthropic or any OpenAI-compatible endpoint works; models already running in Ollama or LM Studio are one click away.
Will a small local model work?
It runs: the context window and output limit come from what the provider reports, with no fixed caps. How well it investigates depends on the model; the project’s release notes carry a smoke test, not a quality score.
Does it watch my account?
No. It reads only while you ask in a task; there is no background or scheduled run.