File size: 2,054 Bytes
3ccf493
 
ad31690
 
3ccf493
 
ad31690
 
3ccf493
ad31690
 
3ccf493
 
ad31690
 
 
 
 
 
 
 
 
 
 
 
 
b077b95
 
 
ad31690
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
---
title: Agent Failure Atlas
emoji: 🧭
colorFrom: yellow
colorTo: indigo
sdk: static
app_file: index.html
fullWidth: true
pinned: false
license: apache-2.0
short_description: Private, client-side analysis of AI-agent trace failures.
---

# Agent Failure Atlas — Static Space

A browser-only showcase for the Open Agent Failure Atlas.

- Trace files are parsed and analyzed locally in the browser.
- The Space makes no model calls and does not upload user-provided traces.
- It supports Hugging Face Session Trace Simple Format (STS), one-row normalized datasets, and OpenAI-style message JSONL.
- The complete Python CLI, native adapters, release tooling, and tests remain in the main repository.

## Public artifacts

- [GitHub](https://github.com/Solasticeaistudio/agent-failure-atlas)
- [Benchmark Dataset](https://huggingface.co/datasets/solsticestudioai/agent-failure-atlas-benchmark)
- [DeltaStore Trace Explorer](https://huggingface.co/spaces/solsticestudioai/deltastore-trace-explorer)
- [DeltaStore Replay Traces Dataset](https://huggingface.co/datasets/solsticestudioai/deltastore-replay-traces)
- [DeltaStore browser app](https://solsticestudioai-deltastore-trace-explorer.static.hf.space/)

## Deploy

Create a Hugging Face Space using the **Static** SDK, then upload the contents of this directory to the root of the Space repository. The YAML front matter above configures `sdk: static` and `app_file: index.html`.

No build step or server dependency is required.

## Local verification

```bash
python -m http.server 8000
# Open http://localhost:8000

node --test tests/core.test.mjs
```

## Scope

The browser implementation mirrors the six deterministic detector families used by the Python MVP:

- scope and unauthorized-tool violations
- approval bypass
- prompt injection in tool output
- runaway repeated actions
- silent or unhandled tool failure
- secret exposure

The bundled 20-session result is a synthetic software smoke benchmark. A perfect fixture score does not establish real-world detector accuracy or model safety.