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

Can Basedash save an answer and reproduce it when reopened?

Basedash saved the monthly-order answer as a dashboard chart and reproduced it in another account's session. The counts remained 11 for June 2026, 18 for July 2026 and 27 for August 2026, totalling 56.

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

For the three complete months before September 2, 2026, monthly order counts were: June 2026 11, July 2026 18, August 2026 27

Transcribed from Proof 1 · Screen recording at 0:01

Expected vs. Found
✓Expected: Reopening a saved answer reproduces the same answer and makes it identifiable as the same question.Found: The new session retained the chart's title and original counts: June 2026, 11; July 2026, 18; August 2026, 27; total, 56.
Supporting proof
Proof 1Screen recording
Screen recording: the monthly-order answer, saved dashboard and reopened chart
Key moments
Open original ↗
Proof 2Screen recording
Screen recording: another account reopens the saved monthly-order chart in a separate session
Key moments
Open original ↗
Why this result

Reopening had to preserve the answer and identify its question. Basedash's own dashboard feature reproduced the chart and values in a second account's new session, with a title naming the measure and period.

Also observed in this test case

How orders were counted. The monthly-order chart's footnote says counts include cancelled orders, group orders by placement date in Calcutta local time, and exclude September's partial month.

Tested by Ayush Ghosh · evidence dated 14 October 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
Basedash
Build or version
Not exposed by the hosted product
Plan or tier
Free trial
Surface
Web app
Set up before the run
The monthly-order answer had to be saved with Basedash's own dashboard feature, then reopened in a new session using a second account.
AI context
Standing rule removed before the run
Tested
14 October 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 →
ToolBasedash →

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
17 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/basedash/the-user-wants-to-keep-an-answer-they-just-got · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-06

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 recording22737153b7a123964bfeb4f093c16645ce738a65d56fadcac7e7eddf8a698e99
Proof 2 · Screen recording920122ff2361003c50b0424f36f9566985e3f5640dfbce201d2bd27c4d1100b7