A cost investigation done once, not redone by a teammate

DevOps, SRE and securityStartup CTO and an engineer chasing an AWS cost spike

Our AWS bill jumped from $4,100 to $6,900 in a month. The CTO's agent found that NAT gateway data transfer was most of it, then the week got busy. When an engineer picked it up, her agent started again from Cost Explorer.

How do I stop a teammate's agent redoing the parts of a cost investigation I already finished?

With ArcRoom, each finished part of the investigation is saved with complete_task: the per-service breakdown, the NAT traffic sources. Your teammate's agent reuses those parts instead of starting again from Cost Explorer, and only does what is left. Split the work into parts with split_task so each part can be finished and reused on its own.

Also asked as: Our AWS bill jumped and the investigation stalled halfway. How does someone else pick it up? · How do I share cloud cost findings between AI agent sessions? · Can a coworker's agent reuse the cost analysis my agent already did?

The work

The request is split with split_task: per-service breakdown, NAT traffic sources, S3 requests, fix options.

ArcRoom keeps
  • Reused answer
  • Saved answer
  • Split into parts
  • Model router
The next agent gets

split_task → "why did AWS cost jump in October"

Step by step

  1. The request is split with split_task: per-service breakdown, NAT traffic sources, S3 requests, fix options.
  2. Each finished part is saved with complete_task, so the engineer's agent reuses them.
  3. Cheap parts, like listing resources, carry a route.model suggestion for a smaller model.
  4. The aws ce and aws ec2 commands are recorded; their output is not.

What the agent sees

split_task → "why did AWS cost jump in October"
✓ breakdown by service: NAT +$2,300 (cto)
✓ NAT sources: image pulls from public registry in 3 subnets (cto)
○ add a VPC endpoint or registry cache (route.model: smaller)
○ check S3 request costs

Compared with today's tools

A shared doc with findings

Whoever investigates writes notes in a doc and the next person pastes them into their agent.

Setup
None
Ongoing
write and paste notes, ~10 min per handover

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min per person (npx arcroom init)
Ongoing
None

A doc works if the first person writes it before the week gets busy; ArcRoom keeps each finished part as it is done.

Where it stops

Billing numbers are as fresh as when they were saved. The agent should re-query Cost Explorer before acting on old figures.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in devops, sre and security