AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 13 November 2026

Can Anomaly AI save an answer and reproduce it when the user reopens it?

Anomaly AI saved the answer as a dashboard and reproduced it outside the original conversation. Reopening retained the explanation and the order counts—18 for July 2026, 27 for August 2026 and 3 for September 1–2, 2026—with a heading identifying the question and cutoff.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Saved answer reopened in a new sessionPassEvidence
What we sent

“Show me our monthly order count for the last 3 months, as of September 2, 2026.”

What the tool returned

Order counts

Your monthly order counts as of September 2, 2026 are: Month / Orders — July 2026 18, August 2026 27, September 1–2, 2026 3

How the counts were interpreted

I’ve treated “last 3 months” as July, August, and September month-to-date. Counts include cancelled orders and use your Asia/Calcutta timezone. Data was last synced October 30, 2026, with placements restricted to the requested cutoff.

Transcribed from Proof 1 · Screen recording at 0:06

Transcribed from Proof 1 · Screen recording at 0:27

Everything the tool returned, in order (3)
  1. Order counts

    The final response, printed above.

  2. How the counts were interpreted

    The final response, printed above.

  3. Original insight panel

    Monthly order count through September 2, 2026 — Interpreting the last three months as July, August, and September month-to-date through September 2. Counts include all order statuses, including cancellations, and use Asia/Calcutta placement dates. Based on data last synced October 30, 2026, restricted to the requested placement cutoff.

Expected vs. Found
✓Expected: Reopening must reproduce the same answer and clearly identify the original question.Found: Original and reopened answers both showed July 2026: 18 orders; August 2026: 27; September 1–2, 2026: 3. The explanation remained, and the heading identified the question and cutoff.
Supporting proof
Proof 1Screen recording
Screen recording: the order-count answer saved to a dashboard and reopened outside the original conversation
Key moments
Open original ↗
Why this result

The product’s own dashboard mechanism reopened the unchanged answer outside the original conversation, with the question still identifiable. Trial status did not block saving or reopening. Reopening used the same browser session; persistence after sign-out, in a new browser or on another device is not established.

Also observed in this test case

How orders were counted. The monthly order-count explanation included cancelled orders and treated July, August and September month-to-date as the last three months. It also stated the time zone and last data sync.

Further dashboard actions. Beside the saved answer, Anomaly AI offered refinement and verification controls. The reopened dashboard also offered database refresh, scheduling, report generation and sharing.

Tested by Ayush Ghosh · evidence dated 2 November 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
Anomaly AI
Build or version
Not exposed by the hosted product
Plan or tier
Pro
Surface
Web app
Set up before the run
The monthly order-count answer through September 2, 2026 had to be saved with the product’s dashboard control and reopened outside the conversation that produced it.
Workspace status
TRIAL
Placement date time zone
Asia/Calcutta
Tested
2 November 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

LevelNameScope
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityReporting →
ScenarioThe user wants to keep an answer they just got →
ToolAnomaly AI →

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
16 November 2026First publishedAI Database Agents v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/anomaly-ai/the-user-wants-to-keep-an-answer-they-just-got · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-13

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recordinga912d982aee87637ceb8e63bb5c9dd891a81871f5e7192e4acac02f6ba419b15