The question
The project syncs client data into three tools: HubSpot, Stripe and QuickBooks. Each one has its own connector. We asked the agent:
Which of the connectors in this repo retry a failed request, and for which errors? List each connector with its retryable errors.
It is the kind of question that comes up again and again: before a fix, in a review, when someone new joins.
The first time
Nobody had asked this before, so there was nothing to reuse. The agent searched the code, read four files and worked it out: no connector retries on the spot; each marks an error as retryable or not, and the retryable ones wait in a queue that a nightly job retries.
That took 6 steps and 283,126 tokens. When the agent finished, ArcRoom kept the answer, with the steps that found it and the files it came from, in the team's memory.
The second time
We closed the session and started a brand-new one. Nothing carried over in the chat. Then we asked the same question, word for word.
Before the agent started, ArcRoom found the team's answer and handed it over. The agent said so itself: “I didn't read the code for this.” It answered in 1 step and 43,042 tokens.
| First time | Second time | |
|---|---|---|
| Steps | 6 | 1 |
| Files read | 4 | 0 |
| Tokens | 283,126 | 43,042 (85% fewer) |
Not just your next session
The answer lives in the team's memory, not in one chat. Your next session gets it, and so does a teammate's agent asking the same thing tomorrow. On the dashboard, the answer shows who found it and that it was reused.