Find where a room is located.
The intention is included in the agent’s input prompt alongside environment details and task instructions.
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0
Open Room 101, inspect its immediate parent, visit North Building, and return to compare the displayed location context.
AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0
Inspect Room 101’s full displayed ancestry, visit North Building, and return to the room.
01 · Given
Restore the data and starting state.
An administrator is signed in, and the Locations list contains the distinct locations Cedar Technologies > North Building > Room 101, with each child linked to its immediate parent.
02 · When
Perform the interaction.
Open Room 101 from the Locations list, inspect the breadcrumb and Parent panel, follow North Building in that panel, then use browser Back to return to Room 101.
03 · Judge
Rationale: In Snipe-IT, this room's placement is represented by a chain of parent locations, independently of its Company attribute. A user locating the room can open its details from Locations and use ancestor links to inspect the surrounding location context. Showing only the immediate parent forces another page visit to recover the outer context; displaying the ancestor chain on the room page supports orientation and navigation. That structural context should be the same after visiting a parent and returning, because it follows the stored relationships rather than browsing history. Different visible hierarchy presentations can provide this context.
Require
On Room 101, show the complete Cedar Technologies > North Building > Room 101 ancestry in structural order without leaving the page, with identifiable ancestor navigation targets. Preserve that ancestry after visiting North Building and returning.
Allowed
- The ancestry may appear in the top breadcrumb, the location information panel, or an equivalent visible hierarchy aid; duplication in both areas is optional.
- Separators, icons, spacing, and wrapping may vary if the ancestor order and navigation targets remain clear.
- This case does not require changes to location-name uniqueness or reproduction of duplicate room names.
Model
HarnessDeepSeek Flash
DSH
33.9M in · 175.5k out · 34.0M total
DSH · 132 steps · $0.28 · 20m 27s · 34.0M tokens
DSH
132
$0.28
20m 27s
33.9M
175.5k
34.0M
GPT-6 Astra
Codex
1.5M in · 6.7k out · 1.5M total
Codex · 30 steps · $2.58 · 7m 53s · 1.5M tokens
Codex
30
$2.58
7m 53s
1.5M
6.7k
1.5M
GLM-5.3 Flash
ZCode
37.8M in · 82.7k out · 37.9M total
ZCode · 334 steps · $1.22 · 1h 02m · 37.9M tokens
ZCode
334
$1.22
1h 02m
37.8M
82.7k
37.9M
Claude Opus 5.5
Claude Code
5.7M in · 25.3k out · 5.7M total
Claude Code · 83 steps · $2.43 · 8m 46s · 5.7M tokens
Claude Code
83
$2.43
8m 46s
5.7M
25.3k
5.7M
Qwen3.8 Max
Codex
20.8M in · 81.5k out · 20.8M total
Codex · 207 steps · $6.18 · 58m 46s · 20.8M tokens
Codex
207
$6.18
58m 46s
20.8M
81.5k
20.8M
Kimi K3
Kimi Code
20.7M in · 63.6k out · 20.8M total
Kimi Code · 212 steps · $7.60 · 1h 02m · 20.8M tokens
Kimi Code
212
$7.60
1h 02m
20.7M
63.6k
20.8M