@sansynx/erroratlas 0.1.2 → 0.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -0
- package/dist/worker/assets.js +1 -0
- package/dist/worker/index.js +18 -1
- package/dist/worker/ui.js +99 -51
- package/package.json +1 -2
- package/public/sequence.png +0 -0
package/README.md
CHANGED
|
@@ -4,6 +4,21 @@ ErrorAtlas is hosted debugging memory for coding agents.
|
|
|
4
4
|
|
|
5
5
|
Developers do not clone this repo, create Supabase projects, deploy Workers, or manage ErrorAtlas infrastructure. They install the npm MCP client, generate one hosted MCP key, run Supermemory locally, and let their coding agent search and publish verified fixes.
|
|
6
6
|
|
|
7
|
+
## Working flow
|
|
8
|
+
|
|
9
|
+
<p align="center">
|
|
10
|
+
<img src="https://erroratlas.sansynx.workers.dev/public/sequence.png" alt="ErrorAtlas working flow" width="100%">
|
|
11
|
+
</p>
|
|
12
|
+
|
|
13
|
+
```txt
|
|
14
|
+
1. Developer signs in at the hosted dashboard.
|
|
15
|
+
2. Dashboard generates one MCP key.
|
|
16
|
+
3. Developer installs @sansynx/erroratlas in their project.
|
|
17
|
+
4. Coding agent connects to the local ErrorAtlas MCP server.
|
|
18
|
+
5. MCP searches Supermemory local plus hosted ErrorAtlas fixes.
|
|
19
|
+
6. After a verified fix, MCP stores sanitized incidents and playbooks remotely.
|
|
20
|
+
```
|
|
21
|
+
|
|
7
22
|
## End-user flow
|
|
8
23
|
|
|
9
24
|
1. Open the hosted dashboard:
|