claude-config-panel 0.0.0-stage → 0.1.0

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/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Carles Galan
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,3 +1,447 @@
1
- # Temporary Holding Version
1
+ <div align="center">
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ # Claude Config Panel
4
+
5
+ **See everything Claude Code is configured to do — and what runs on its own.**
6
+
7
+ Your Claude setup is scattered across `~/.claude` and a `.claude/` folder in every repo.
8
+ There is no single screen that shows you all of it. This is that screen.
9
+
10
+ [![CI](https://github.com/Galan9999/claude-config-panel/actions/workflows/ci.yml/badge.svg)](https://github.com/Galan9999/claude-config-panel/actions/workflows/ci.yml)
11
+ [![License: MIT](https://img.shields.io/badge/license-MIT-D97757.svg)](LICENSE)
12
+ [![Node](https://img.shields.io/badge/node-%E2%89%A518-5B8C51.svg)](package.json)
13
+ [![Dependencies](https://img.shields.io/badge/dependencies-0-5B8C51.svg)](package.json)
14
+ [![Tests](https://img.shields.io/badge/tests-247-5B8C51.svg)](test)
15
+
16
+ </div>
17
+
18
+ ```bash
19
+ npx claude-config-panel
20
+ ```
21
+
22
+ Open <http://127.0.0.1:7337>. Node 18+. Nothing to install, no dependencies, runs only on your machine.
23
+
24
+ No Node? **[Try it in your browser](https://claude-config-panel.vercel.app)**: you pick the folders, they are
25
+ read in the tab, and nothing is sent or saved anywhere.
26
+
27
+ <div align="center">
28
+ <img src="https://raw.githubusercontent.com/Galan9999/claude-config-panel/main/docs/overview.jpg" alt="Overview: every piece of Claude configuration grouped by type" width="820">
29
+ </div>
30
+
31
+ ---
32
+
33
+ ## Why
34
+
35
+ `/config` and `/permissions` cover a slice of it, and only in the terminal. Everything else means
36
+ opening JSON files by hand. So three questions stay unanswered:
37
+
38
+ - **What do I actually have?** Settings, skills, agents, commands, hooks and scheduled tasks, global
39
+ and per repo, in one place.
40
+ - **What does this rule really allow?** `Bash(node *)` reads as harmless. It lets Claude run any
41
+ script on your machine.
42
+ - **What runs without me?** Hooks and scheduled tasks act while you are not looking. That is the part
43
+ of your configuration that deserves the most attention and gets the least.
44
+
45
+ ---
46
+
47
+ ## What it does
48
+
49
+ ### Explains every permission in plain words
50
+
51
+ Each rule is translated, and the ones that are wider than they look get flagged.
52
+
53
+ | Rule | What the panel says |
54
+ |---|---|
55
+ | `Bash(git *)` | Can run git with any argument, without asking. |
56
+ | `Bash(node *)` | …**Careful: that allows running any script**, so in practice it is a very broad grant. → `broad` |
57
+ | `mcp__…__slack_send_message` | Acts outward: can send or change something in that service. → `outbound` |
58
+
59
+ <div align="center">
60
+ <img src="https://raw.githubusercontent.com/Galan9999/claude-config-panel/main/docs/permissions.jpg" alt="Permissions translated into plain language, with broad and outbound rules flagged" width="820">
61
+ </div>
62
+
63
+ ### Says why a rule should be the shape it is
64
+
65
+ Every rule carries a *why it is like this, and what else it could be* panel: which family the
66
+ command belongs to, what the prefix still admits once you look past the program's name, whether the
67
+ rule is in the right file, and the narrower rule that does the same job.
68
+
69
+ | Rule | Verdict | Because |
70
+ |---|---|---|
71
+ | `Bash(find *)` | `reconsider` | `find . -exec <anything> {} \;` runs that anything. It is an interpreter rule wearing a different name. |
72
+ | `Bash(npm run *)` | `narrow it` | Grants whatever `package.json` says those scripts mean today, and the repo can change them. |
73
+ | `Bash(gh pr *)` | `narrow it` | Covers `gh pr view` and, in the same breath, `gh pr merge` and `gh pr close`. |
74
+ | `Bash(ls *)` | `redundant` | Plain read-only commands never needed a rule. |
75
+ | `Bash(npm test)` | `reasonable` | No wildcard: it approves this command line and nothing adjacent. |
76
+
77
+ The **Permissions guide** view holds the reference behind those verdicts — how a Bash pattern is
78
+ matched (a prefix string, no flag analysis), what `allow` / `ask` / `deny` / `defaultMode` /
79
+ `additionalDirectories` each do, the command families, and six questions to ask before adding a
80
+ rule.
81
+
82
+ ### Says who decides in auto mode
83
+
84
+ A permission rule is not the last word. In auto mode the prompt never reaches you: the action goes
85
+ to a classifier on Anthropic's servers, which decides from rules of its own. The settings view spells
86
+ that out next to the mode selector — whether this file can grant `"auto"` at all (only
87
+ `~/.claude/settings.json`, a managed policy or `--permission-mode auto` can; the same value in a
88
+ repo's settings is ignored), whether `autoMode.classifyAllShell` is suspending every `Bash` rule,
89
+ and whatever `autoMode.{environment, allow, soft_deny, hard_deny, deny}` the file adds.
90
+
91
+ ### Surfaces what runs on its own
92
+
93
+ Hooks and scheduled tasks in one table: what triggers them, what they run, with what time limit.
94
+ This is how you find out you have two Prettier hooks firing on every single write.
95
+
96
+ ### Lists your mods
97
+
98
+ A mod is a change Claude Code makes to its own interface or behaviour: a panel, a band, a status
99
+ line entry, a toast, a slash command, a hook on tool calls. They live in `~/.claude/mods/<name>/`
100
+ and run as you. The **Mods** section reads each folder (`plugin.json`, `hooks/hooks.json` and the
101
+ hooks module) and shows its description, version, whether your settings load it, the commands, the
102
+ tools for the model and the hook events it registers, what it draws on, and whether it runs
103
+ processes, touches files or calls a model. It reads names from the source; it never runs a mod and
104
+ it does not edit one.
105
+
106
+ ### Separates MCP servers and routines
107
+
108
+ **MCP servers** has its own section, grouped by where each one is declared (`~/.claude.json`,
109
+ `.mcp.json`, a project): the command or URL and the *names* of the secrets it needs, never their
110
+ values.
111
+
112
+ **Routines** gathers everything that fires on a schedule, each with its definition: the local ones
113
+ in `~/.claude/scheduled-tasks`, the cloud ones from your claude.ai account (name, cron, state, next
114
+ and last run, connectors and prompt, redacted), and session loops. `/loop` and session cron jobs
115
+ live in a running session's memory, not in a file, so only the ones that were active when the
116
+ snapshot was generated can be shown. Cloud routines are not on disk either: the artifact edition
117
+ shows them when whoever generates the snapshot adds them.
118
+
119
+ ### Draws your command pipelines
120
+
121
+ Nothing to declare or install: it is a naming convention. **Two or more files in the same commands
122
+ folder whose name starts with `<number>.`** are read as the phases of one process. The number only
123
+ sets the order — they need not be consecutive nor start at 1, so you can leave gaps for phases you
124
+ add later.
125
+
126
+ ```
127
+ .claude/commands/deploy/
128
+ 1.check.md
129
+ 2.build.md
130
+ 3.ship.md
131
+ ```
132
+
133
+ That is enough for the panel to render `/deploy:*` as an SVG diagram generated from the files
134
+ themselves — no Mermaid, no CDN — showing each phase's model, which subagents it spawns, and **how
135
+ many actions it can take outside your machine without asking**. No folder is hardcoded; it works
136
+ with whatever you name yours.
137
+
138
+ If your commands are not a sequence, the section tells you so and explains the convention. It never
139
+ invents a flow that is not there.
140
+
141
+ <div align="center">
142
+ <img src="https://raw.githubusercontent.com/Galan9999/claude-config-panel/main/docs/flows.jpg" alt="A four-phase command pipeline drawn from the command files" width="820">
143
+ </div>
144
+
145
+ It also flags **drift**: commands referenced in documentation that no longer exist, and paths
146
+ mentioned that are not there. Documentation that describes a command nobody can run is a trap, and
147
+ this finds it the day it breaks instead of months later.
148
+
149
+ ### Maps how your agents talk to each other
150
+
151
+ The **Agent map** draws every piece that can start, call or watch another one — commands, skills,
152
+ subagents, hooks, mods, routines, MCP servers, chats with a role — and the arrows between them, read
153
+ from the files themselves. One arrow style per kind of interaction:
154
+
155
+ | Arrow | Means |
156
+ |---|---|
157
+ | opens a chat | a mod opens a new session in its own window (`open`, `open_group`) |
158
+ | invokes | `/x` or `Skill(x)`: the instructions load into the same context |
159
+ | delegates | `subagent_type: x`: a subagent works in its own context and returns a summary |
160
+ | fires a hook | a hook runs on an event or watches a tool, and can block or inject context |
161
+ | schedules | a desktop routine, launchd, `/loop` or `/schedule` starts it without you |
162
+ | calls an MCP | `mcp__server__tool`: Notion, Slack, GitHub… |
163
+ | shared state | a coordinator's `state.json` or a `.sdd/` folder the phases leave for one another |
164
+
165
+ An arrow is drawn only when the text says it in a form Claude Code acts on. When it rests on a bare
166
+ mention — an agent's name in prose, "Notion" with no tool call — it is drawn faint and marked
167
+ **assumed**. Four tabs:
168
+
169
+ - **Flow** — only what interacts, left to right. *Trace from here* keeps what one piece sets in motion.
170
+ - **Static** — every piece, one column per kind.
171
+ - **Live** — the chats running now, with their role and phase, if a coordinator keeps a
172
+ `.sdd/_conductor/state.json` in one of the scanned projects (or `--sdd-state <file>`). Read-only.
173
+ - **Audit** — broken `/ns:cmd` references, unknown `subagent_type`, calls into a repo the caller never
174
+ loads, names shadowed between global and a project, subagents nothing reaches (or only prose
175
+ does), hook matchers that match no tool, routines that will not run.
176
+
177
+ Filter by kind and by **scope**: everything, global only, one repo, or a repo *as Claude sees it
178
+ there* (global + that repo). Zoom with a pinch or ⌘/Ctrl + wheel, drag to move.
179
+
180
+ <div align="center">
181
+ <img src="https://raw.githubusercontent.com/Galan9999/claude-config-panel/main/docs/agent-map.jpg" alt="The agent map's flow view: a routine starts a coordinator that opens chats and runs a four-phase pipeline, with subagents, hooks and MCP calls" width="820">
182
+ </div>
183
+
184
+ ### Shows who built what
185
+
186
+ Per piece: who created it and when, who touched it since, how many lines each commit changed, and a
187
+ link to the commit. There is a profile per person with everything they created and everything they
188
+ touched afterwards.
189
+
190
+ It merges the same human across identities — work email, GitHub's
191
+ `12345+user@users.noreply.github.com`, the `user@MacBook-Air.local` of an unconfigured laptop — and
192
+ shows you which identities it merged, so you can spot a bad merge instead of trusting it.
193
+
194
+ For anything outside git — `~/.claude` is not a repo, `settings.local.json` files are gitignored —
195
+ it says so instead of inventing an author from a file timestamp.
196
+
197
+ ### Tracks whether a skill changes anything
198
+
199
+ A skill that never fires is dead weight. A skill that fires and changes nothing is worse, because
200
+ it reads like coverage. `claude plugin eval` answers both by running each case twice — with the
201
+ skill and without it — and the **delta** between the arms is the only number that means something.
202
+ A case that passes in both arms is measuring the base model.
203
+
204
+ The **Evals** tab finds every bench on disk (a folder with `.claude-plugin/plugin.json` and an
205
+ `evals/` directory — a `.claude/` folder is not a plugin, so the bench lives outside the repo and
206
+ symlinks the skill in rather than copying it) and shows, per case: score with, score without, the
207
+ delta, and how many runs actually invoked the skill. It separates the two failure modes: a low
208
+ score means the skill is wrong, `0/3` fired means it never ran.
209
+
210
+ | Case | with | without | Δ | fired |
211
+ |---|---|---|---|---|
212
+ | `1-positivo-contencion` | 1.00 | 0.00 | **+1.00** | 3/3 |
213
+ | `2-negativo-rojo-real` | 1.00 | 0.33 | +0.67 | 0/3 — correct: it should stay quiet |
214
+
215
+ It also costs the next run out of that bench's own history rather than a guess, flags a case with no
216
+ grader and a symlink that no longer resolves, and lists which skills have a bench and which do not.
217
+ Each skill's own page carries its delta, which is where it matters: when you are deciding whether
218
+ to keep, rewrite or delete it.
219
+
220
+ #### Agents too, with three rules that are not the skill ones
221
+
222
+ A bench can measure a subagent, and the panel reads those the same way — but getting one to run at
223
+ all turns on three things that cost real money to discover:
224
+
225
+ **The agent file has to be a copy, not a symlink.** The opposite of the rule for skills. A symlink
226
+ under `agents/` is silently not loaded: the plugin still resolves, the suite still runs, and every
227
+ case scores zero exactly as if the agent had failed its own rubric. The only trace is in the
228
+ model's own words — `Available agents: claude, Explore, general-purpose, …`, with your agent
229
+ missing. The panel flags a symlinked agent as **not loaded**, and because a copy goes stale it
230
+ hashes both files and flags a **stale copy** when the bench holds an older version than the one
231
+ you are reading.
232
+
233
+ **The dispatch name carries the plugin prefix** — `my-bench:code-reviewer`, not `code-reviewer`.
234
+ The bare name fails with `Agent type not found`, and the model will decline to substitute a
235
+ generic agent rather than pass it off as yours.
236
+
237
+ **Run it with `--ablation none`.** The baseline arm has no plugin, so it cannot dispatch your agent
238
+ even in principle: its score is zero every time and the Δ measures the absence of the plugin, not
239
+ the agent. Without a baseline the score is read in absolute, and the panel labels it `no baseline`
240
+ rather than the `no Δ` it shows for a bench that has genuinely never been compared.
241
+
242
+ What is worth measuring also differs. For a skill you measure the trigger, because the model
243
+ decides whether to load it. An agent dispatched by a slash command never faced that decision, so
244
+ the `tool_used: Agent` grader is a check that it really ran, not a metric — and the score belongs
245
+ on what the agent's contract adds that the base model lacks.
246
+
247
+ ### Reads your audits, next to what they are about
248
+
249
+ Point an auditing agent at a scope, have it write its report, and the panel shows each finding
250
+ beside the piece it concerns. Pieces with findings are marked in the listings, and a finding that
251
+ names a piece without living in its file is cross-referenced to it.
252
+
253
+ Reports live in `~/.claude/audits/<scope-slug>/<timestamp>.json` — **outside** the configuration
254
+ they are about. A report is an opinion about the config, not part of it: inside the repo it becomes
255
+ one more piece to audit, one more thing to gitignore or commit, and the next run overwrites the
256
+ last. The **Auditor** tab lists every scope the panel can see, audited or not, with its run history,
257
+ and keeps reading an older in-repo `.claude/audit/findings.json` so nothing already written is lost.
258
+ Scopes are keyed by the folder that owns the `.claude`, so a monorepo package like `apps/web` gets
259
+ its own audit rather than disappearing behind the repo it sits in.
260
+
261
+ A report can also carry **questions**: the things no amount of file-reading settles. A permission is
262
+ not wrong for being wide, it is wrong when nothing you do needs it that wide — and only you know
263
+ which. Each question names the exact rule, says what the answer decides, and offers the plausible
264
+ answers. The tab hands you a prompt that walks them one at a time and opens a PR with whatever you
265
+ agreed to.
266
+
267
+ No automatic patches and no automatic PRs. A patch that applies itself invites you to accept it
268
+ without reading it, which is the opposite of the point.
269
+
270
+ <div align="center">
271
+ <img src="https://raw.githubusercontent.com/Galan9999/claude-config-panel/main/docs/diagnostics.jpg" alt="Audit findings with severity, what happens and what to do" width="820">
272
+ </div>
273
+
274
+ > The screenshots show a sample configuration, not a real one.
275
+
276
+ ### Lets you edit
277
+
278
+ Markdown rendered, JSON validated, every save backed up first.
279
+
280
+ ---
281
+
282
+ ## Usage
283
+
284
+ ```bash
285
+ npx claude-config-panel # scan the usual project folders
286
+ npx claude-config-panel ~/my-repos # scan a specific folder
287
+ ```
288
+
289
+ | Option | What it does |
290
+ |---|---|
291
+ | `--port <n>` | Port to listen on (default 7337) |
292
+ | `--depth <n>` | How deep to look for `.claude/` folders (default 5 — enough for `<repo>/apps/<package>`) |
293
+ | `--worktrees` | Include linked worktrees, skipped by default because they duplicate their repo's config |
294
+ | `--sdd-state <file>` | The SDD coordinator's `state.json` for the agent map's live view (default: the first scanned project with `.sdd/_conductor/state.json`; also `CCP_SDD_STATE`) |
295
+ | `--help` | Usage |
296
+ | `CLAUDE_CFG_ROOTS=/a:/b` | Folders to scan, via environment variable |
297
+
298
+ With no arguments it looks for projects with a `.claude/` folder in the usual places (`~/code`,
299
+ `~/dev`, `~/projects`, `~/Desktop`, `~/Documents`…). Ctrl+C to stop.
300
+
301
+ The first time, the panel opens on **Sources**, where you choose what it reads:
302
+
303
+ - **Everything on this computer** — scans your whole home folder (skipping `Library`, caches,
304
+ `node_modules` and worktrees), then you untick the projects you do not want.
305
+ - **Only the folders I choose** — one path per line.
306
+ - **Let Claude Code find them** — a prompt to paste into Claude Code that lists the folders holding
307
+ configuration and what each has, without opening or changing anything.
308
+
309
+ Each project shows what it holds before you include it. The choice is kept in your browser and put
310
+ back when the server restarts; nothing is written to disk.
311
+
312
+ ---
313
+
314
+ ## Security
315
+
316
+ > [!IMPORTANT]
317
+ > This reads **and writes** your Claude configuration. Every save leaves a copy in
318
+ > `~/.claude/backups/config-dashboard/` first, but it is worth knowing before you start editing.
319
+
320
+ - **Listens on 127.0.0.1 only.** Never exposed to the network.
321
+ - **Checks where every request comes from.** Binding to localhost is not protection from your
322
+ browser: any open website can fire requests at it. With `content-type: text/plain` that would be a
323
+ simple request, no preflight, and the write would land even though the attacker cannot read the
324
+ response — and the first piece in the inventory is `~/.claude/settings.json`, where a hook runs by
325
+ itself in your next Claude session. So `Host` is validated (which also closes DNS rebinding),
326
+ `Origin` is validated, and `application/json` is required, forcing a preflight.
327
+ Regression tests live in [`test/server.test.mjs`](test/server.test.mjs).
328
+ - **Writes only to config files found during the scan.** Any other path is rejected.
329
+ - **Serves static files from `ui/` with no subfolders and no `..`**, so there is no path traversal.
330
+ - **Validates JSON before writing.** A malformed file never reaches disk.
331
+
332
+ Do not expose it beyond your own machine: it reads your Claude configuration, which can hold paths,
333
+ connector tokens and the contents of your scheduled tasks.
334
+
335
+ Thanks to **Lluís Filella** for catching the unauthenticated `POST`.
336
+
337
+ ---
338
+
339
+ ## The findings format
340
+
341
+ For an audit to be worth more than a read-through, its output needs a contract:
342
+ [`schema/findings.schema.json`](schema/findings.schema.json), validated by
343
+ [`src/findings.mjs`](src/findings.mjs).
344
+
345
+ <details>
346
+ <summary>Example report</summary>
347
+
348
+ ```json
349
+ {
350
+ "version": 1,
351
+ "generatedAt": "2026-10-21T16:40:00.000Z",
352
+ "tool": "auditor-config",
353
+ "scope": { "path": "~/repos/backend", "kind": "repo" },
354
+ "summary": "Drop Bash(bash *) from allow.",
355
+ "findings": [{
356
+ "id": "wildcard-bash-permission",
357
+ "severity": "alta",
358
+ "category": "permiso-amplio",
359
+ "title": "Bash(bash *) allows running any script",
360
+ "path": ".claude/settings.local.json",
361
+ "line": 4,
362
+ "what": "The rule lets any file be executed.",
363
+ "proposal": "Replace it with the three concrete invocations actually in use.",
364
+ "autofix": { "kind": "quitar-permiso", "file": ".claude/settings.local.json", "rule": "Bash(bash *)" }
365
+ }],
366
+ "notChecked": []
367
+ }
368
+ ```
369
+
370
+ </details>
371
+
372
+ Validation is strict on purpose: whatever produces this is a language model or a third-party tool.
373
+ Two rules that are not cosmetic:
374
+
375
+ - **`id` must be stable across audits.** That is what decides whether a finding opens a new ticket or
376
+ already has one.
377
+ - **A `proposal` starting with "review" is rejected.** It has to say what to do.
378
+
379
+ The format does not depend on this panel. Any auditor can emit it, and `cc-audit --format json` is a
380
+ candidate for an adapter.
381
+
382
+ ---
383
+
384
+ ## Development
385
+
386
+ No dependencies, runtime or dev. Everything it uses ships with Node: the server is `node:http` and
387
+ the tests are `node:test`.
388
+
389
+ ```bash
390
+ git clone https://github.com/Galan9999/claude-config-panel
391
+ cd claude-config-panel
392
+ npm start # run the panel
393
+ npm test # 185 tests
394
+ ```
395
+
396
+ <details>
397
+ <summary>Project layout</summary>
398
+
399
+ ```
400
+ bin/claude-config-panel.mjs CLI entry point
401
+ src/
402
+ cli.mjs Arguments, help, startup message
403
+ paths.mjs ~/.claude paths
404
+ fsutil.mjs Tolerant reads, frontmatter, script docs
405
+ git.mjs GitHub remote, repo root, worktree detection
406
+ history.mjs Authorship and changes, via git log
407
+ flows.mjs Numbered command pipelines and drift detection
408
+ findings.mjs Audit findings schema and cross-referencing
409
+ audits.mjs The audit store in ~/.claude/audits: runs, history, slugs
410
+ evals.mjs Eval benches, per-case deltas, coverage and run cost
411
+ discover.mjs Filesystem walk and piece catalogue
412
+ mods.mjs ~/.claude/mods, through the artifact scanner's reader
413
+ server.mjs HTTP routes, saving, backups
414
+ ui/
415
+ index.html The page
416
+ style.css Palette, with dark mode
417
+ app.js Navigation, listings, detail, editing
418
+ markdown.js Markdown renderer
419
+ permissions.js Translates a permission rule into a sentence
420
+ advice.js Why that rule, and the narrower one that would do
421
+ util.js HTML escaping and helpers
422
+ mods.js Reads what a mod registers (shared with the artifact scanner)
423
+ test/ Tests for the pure functions and the HTTP contract
424
+ ```
425
+
426
+ </details>
427
+
428
+ The interface lives in real `.html`, `.css` and `.js` files served as static assets.
429
+ `ui/markdown.js`, `ui/permissions.js` and `ui/advice.js` are DOM-free ES modules, so the Node tests
430
+ import exactly the same code the browser runs.
431
+
432
+ ## The artifact edition
433
+
434
+ `artifact/` is a version that runs as a page, without Node — [hosted on Vercel](https://claude-config-panel.vercel.app),
435
+ where nothing is saved, or as a claude.ai artifact, where each person's snapshot is kept privately: each person drops their folders and
436
+ the snapshot is read in the browser and kept in their own private space. It has the same views plus
437
+ **Mods**, **MCP servers** and **Routines**, lists pieces by kind and grouped by place (skills, agents,
438
+ commands, hooks declared in settings, hook scripts, scheduled tasks), and speaks **English, Spanish
439
+ and Catalan** (selector in the sidebar; a string not yet translated shows in English). The scanner
440
+ is shared with an optional Node collector. `node artifact/build.mjs` builds `artifact/dist/`, the
441
+ folder that gets published.
442
+
443
+ ---
444
+
445
+ ## License
446
+
447
+ MIT