Answers
My agent said the task was done. What should the next session believe?
Treat "done" as a claim until something that can be reopened says so. "Created", "fixed" and "verified" are what the agent reports about its own work, and a later session that inherits the sentence as settled inherits the agent's confidence along with it. In Arroway a finished task leaves a dated record of what was done, and a fact an agent saves carries a pointer to its source and a date after which it stops being served. A session whose work takes it to that source marks the fact as matching, conflicting or gone, and a conflicting fact gets a proposed correction that names the one it replaces. Arroway does not run your checks or confirm the work itself: it keeps a claim of completion tied to the place where it can be checked. Use Arroway when the next session, yours or someone else's, will act on what the last one reported. The install page is the first step.
Last updated October 29, 2026
Why "done" is the claim that travels worst
An agent reports on its own work in its own words, and what it saw and what it did can differ: a fix can remove the symptom and leave the requirement unmet, and a step can be logged as sent when it never left. When that sentence is saved as a fact, the next session reads it as settled, and the mistake moves from one conversation into the memory of everyone who reads it after. The problem is not that agents are wrong more often than people. A person's "done" usually comes with a ticket, a receipt or a name to ask, and the agent's sentence often comes with nothing to reopen.
What a record can carry so the next session can check it
A record of finished work says what was done and where the result lives: the pull request, the record that changed, the address. A fact carries a pointer to that source and a review date, and after the date it leaves the read, so a status from last week is not served as current. When a session's own work takes it to the source, it records what it found: matches, conflicts, with what the source says, or gone, only on proof that it was removed. A timeout, a login wall or an outage is not proof of removal. A conflicting fact is corrected by a proposal that names the one it replaces, and a rule or a decision that a source contradicts is only marked, so a person decides what to do about it. Nobody is sent to verify memories as a task: the mark happens when the work already went there.
When to use Arroway
Use Arroway when the next session will act on what the last one reported, and a wrong "done" costs more than a minute: a migration, a payment flow, a message to customers. Record the result with the source it can be checked against. Arroway does not run tests, does not read the work, and cannot tell a true "done" from a false one by itself. What it keeps is the pointer, the date and the mark each later session leaves. The first step is the install page.
What it looks like in practice
Mara asks an agent to stop the nightly export from crashing when a customer has no email. The agent reports: fixed, the crash is gone. What it changed was an early return when the email is missing, so the crash is gone and the receipt is never sent. Saved as a plain note, that sentence is what every later session believes. In Arroway the agent records the result as a fact, with the pull request as its source and a review date. A week later another session opens the same pull request for an unrelated reason, sees the early return, and marks the fact as conflicting, with a note that the receipt is still not sent when the email is missing. It proposes the corrected fact, which names the earlier one. Nothing here was measured on a real project; the people and the export are illustrative.
Questions people ask about this
- Does Arroway check that the agent's work is correct?
- No. It does not run tests, read the code or confirm the result. It records the claim with its source and date, and records what a later session finds when it opens that source. Whether the work is right is still settled where the work lives.
- What if the source cannot be reached?
- Unavailability is not removal. A timeout, a login wall or an outage leaves the fact as it was, and only proof that the source is gone retires it.
- How do I try Arroway?
- Install it in the tool you already use — the install page has one route for Claude, ChatGPT, Codex, Cursor or any MCP tool — and sign in when the tool asks. From then on, sessions open by reading the project and close by recording what was decided.
Where this is verifiable
Product documentation on this site (How it works, Install), the answers on what an AI leaves for its next session and on out-of-date memory being read as current, and the verification, supersede, sanction and expiry rules in the sanctioned product spec. Everything described here about Arroway is behaviour the tools apply today, not roadmap. The person, the agent and the export in the example are illustrative.
https://www.arroway.app/en/answers/the-agent-said-done-what-the-next-session-inherits