Commit Graph
449 Commits
Author SHA1 Message Date
Willie 3d08cbc670 fix(plugins): name a git failure's cause only when git names it
Git opens every HTTPS failure with "unable to access", a bad certificate
or a 403 included, and a missing git-lfs says "command not found". Those
were reported as a network problem or a missing source and sent the user
to the wrong fix; they now fall back to the general failure.

Discovery of a managed plugin is also cached per plugin, since two
plugins of one source can have snapshots at different commits.
2026-09-27 23:08:39 +08:00
Willie c25eb4f708 fix(plugins): open managed plugins from their snapshot and explain slow reads
Opening a plugin cloned its whole source again to learn which Agents
can take it, which took tens of seconds per row. A managed plugin
already has a reviewed snapshot; it answers when its digest still
matches, and the network is used only otherwise.

A failed clone said only that git failed. Git's output is sorted into
an unreachable source or a missing one without passing it on, since it
can hold credentials. The dashboard translates those, notes when a read
or an Agent's CLI is slow, and says when the browser is offline.
2026-09-27 23:03:21 +08:00
Willie 6bf0777603 feat(ui): tell global and project targets apart on the Skills page
Project targets (`<project>@<tool>`) drew the same icon as the global
tool, so a skill synced to claude plus two projects showed three Claude
icons and the Targets column could not say which was which.

The icon stack now holds global tools only, followed by a count of the
projects the skill reaches; hovering lists global tools and each
project's tools, naming projects it misses. The Target filter groups
global tools and projects, with one entry per project. In the tree
view the Targets row shows where a single skill actually goes, tagging
a `targets:` that narrows it. Without projects the page is unchanged.

Refs #297
2026-09-27 18:59:37 +08:00
Willie 5eb1838886 feat(ui): manage a shared AGENTS.md from one panel
The shared AGENTS.md tab split its controls between a list and a
separate detail page, so connecting a target, editing the file and
fixing drift meant moving between pages and repeating the same
target list twice.

Everything now lives in one panel next to the file list: a short
preview, one switch per target, connect-all and restore-all, and
multi-select with a bulk toolbar. Editing opens a large dialog with
the readers and length warnings beside it. Every change goes through
a confirm dialog, and old detail-page links redirect to the panel.

The delete confirmation no longer says the file is deleted, because
the server only removes it from the list and keeps it on disk.
2026-09-27 10:45:25 +08:00
Willie 86fb63fd4b docs: document sharing AGENTS.md from the dashboard
The shared AGENTS.md workflow is dashboard-only, so users had no written
reference for how shared files attach, what restore puts back, or where
drift backups go. Adds a how-to page in every locale, documents
single-file extras and the target `instructions` key, and brings the
translated extras collect section up to date with English.
2026-09-27 04:17:41 +08:00
Willie b8291895e1 feat(ui): share one AGENTS.md across tools from the dashboard
Claude Code now reads AGENTS.md, but every tool still keeps its standing
instructions in its own file (CLAUDE.md, GEMINI.md, AGENTS.md), and Claude
has no user-level AGENTS.md at all. Keeping several tools on the same
instructions meant copying text between those files by hand.

Each target page gets a tab named after the file it reads, with its read
order, an editor, and a convert flow from CLAUDE.md to AGENTS.md. In global
mode the Extras page gets an AGENTS.md tab where several shared files can
coexist and each target picks one or keeps its own. Shared files are
single-file extras: tools that follow @imports get a managed import block
and keep their own lines, others get a link in place of their file.
Projects get small shims instead, since every tool there reads ./AGENTS.md.
Custom targets can declare which file they read.

Restore records the target's state when it is first attached (file,
symlink, or no file) and always returns to it. Edits made after attaching
are kept as drift backups instead of becoming the restore point, so sync,
reapply and mode switches can no longer lose the user's original file.
2026-09-27 03:02:51 +08:00
Willie 9dab28fc19 fix(git): undo a pull's partial checkout and explain permission errors
When git cannot finish a pull's checkout (for example, it may not unlink
a root-owned file), it stops without undoing the files it already wrote,
and with no MERGE_HEAD there is nothing for merge --abort to undo. The
remote's copies then showed up as local changes: the dashboard blocked
the next pull and suggested committing them, which would push the stale
remote content back as a new commit.

A failed pull now restores paths that were clean before it started and
now hold exactly the upstream version, leaving the user's own edits
alone. The dashboard reports permission failures with a
permission_denied code and shows the chown command that gives the
source folder back to the current user.
2026-09-27 02:10:12 +08:00
Willie 779ec26ff5 fix(upgrade): elevate only the binary replacement with sudo
When the binary lived in a root-owned directory, upgrade re-ran the whole
command under sudo. The built-in skill download, UI asset cache, and oplog
then landed in the user's home as root-owned files, and a later git pull
of the skills source failed with "unable to unlink old
'skillshare/SKILL.md': Permission denied".

The sudo child now only receives an internal --replace-binary=<version>
flag that downloads and swaps the binary. The parent waits for it and
does everything else as the invoking user. The needs-password hint shown
by the CLI and dashboard drops its sudo prefix, since a fully root
upgrade reproduces the same breakage.
2026-09-27 02:10:00 +08:00
Willie 5da935e201 feat(ui): compact the Skills and Agents toolbar
Six labelled selects, each reading "All" most of the time, plus a
two-button expand/collapse group made the toolbar wrap and hard to scan.

- Filters are chips: an unset one shows only its name; a set one fills
  in, shows its value and has a clear button.
- Group and sort, which change rarely, share one icon menu.
- Expand/collapse all is one button that flips with the tree's state.
2026-09-26 22:36:31 +08:00
Willie 9effc9bb61 feat(ui): mark disabled tree items with their icon
The tree showed "Disabled" as hover text on each disabled skill, which
repeated what the dimmed row already said and crowded the hover slot.
A disabled item now swaps its icon for a power-off icon (with an
accessible name), and the hover text is kept only for folder counts.
2026-09-26 22:36:31 +08:00
Willie 2be314a1dd feat(ui): filter and group skills by folder
Skills installed with --into land in folders, but the list and cards
views could only filter and group by source, so there was no way to
look at one folder at a time or see the folders side by side.

Add a Folder filter next to Targets and a Folder option to Group. A
skill's folder is its parent path, a tracked repo counts as one folder,
and skills at the source root group under "Root". The filter is hidden
when everything lives in one folder. Agents get the same controls.
2026-09-26 21:25:32 +08:00
Willie a7e009bb9e feat(ui): rework the skills tree as a tree with a detail pane
Turning a whole folder or tracked repo off meant ticking every skill
in it, and the tree rows mixed table columns with indentation.

The tree view is now an explorer tree beside a detail pane. Click a
folder, repo or skill to select it; Cmd/Ctrl-click adds, Shift-click
selects a range. The pane turns the whole selection on or off with one
switch, sets its targets (tracked repos included), and lists each skill
with its own switch. Counts and disabled markers show on hover, and the
divider between the two sides can be dragged.

Enable/disable toasts now replace each other through a new toast `key`,
so quick on/off clicks no longer leave an outdated "Enabled" on screen.

Refs #295
2026-09-26 21:02:36 +08:00
Willie e259d3c116 fix(plugin): keep a failed host's installed list empty, not null
When an Agent's plugin inventory failed (for example OpenCode with both
opencode.json and opencode.jsonc present), the inventory call overwrote
the host's installed list with nil, which the API encoded as null. The
Plugins page read its length unguarded, so one misconfigured Agent
crashed the whole page.

Host.fail now restores an empty list, covering every inventory path
that reports through it, and the dashboard reads a null list as empty
so a single Agent can no longer take the page down.

Refs #296
2026-09-26 13:11:00 +08:00
Willie bf32112032 feat(git): show pending remote commits and auto-merge metadata conflicts
Two machines sharing a source repo kept stopping at the same two places.
The Git page had no way to know the remote moved until a push bounced, so
it now fetches once on open and labels Pull with the commit count (status
itself stays offline because the sidebar polls it). And both machines
rewrite .metadata.json on every install or update, so nearly every
diverged pull conflicted there; those conflicts are now merged per entry,
keeping the later installed_at, while any other conflict still stops the
pull and names the files.
2026-09-25 02:22:35 +08:00
Willie 51af1d30ba fix(git): recover when two machines push to the same source repo
Once both machines committed, the UI push was rejected and the follow-up
pull failed with "Need to specify how to reconcile divergent branches",
leaving no way out without a terminal. Pull now merges explicitly and
aborts a conflicted merge so a later commit-all cannot push conflict
markers; a rejected push returns push_rejected so the UI offers Pull.
2026-09-25 02:18:00 +08:00
Willie 2acd184445 feat(ui): show each target's MCP servers on its Targets page
A target's page covered its skills and agents only, so seeing which MCP
servers an Agent gets meant reading across the MCP page's matrix. A
target with an MCP config file now has an MCP tab, in global and -p
mode, with a row per server that saves as it is clicked, and the
Targets list counts those servers beside the skills.

MCP sync writes every target's files at once, so the tab names its
button for that. Its confirm dialog, like the MCP page's and the
project sync dialog, now lists one row per Agent file the way the
Skills sync dialog does, and still says why an MCP entry conflicts.

Each save previews first and sends that revision, so a second click
racing it was refused and rolled back the first; the toggles now wait.
A switch that names no targets no longer gets saved with Agents that
cannot turn a server off, which the backend refused.
2026-09-23 00:38:44 +08:00
Willie 265f9ee9b9 feat(ui): show Pi adapter settings on the MCP server row
Direct tools and other adapter settings were only visible on hover, so
checking which tools a server exposes to Pi meant pointing at every row.
They now sit on a line under the endpoint. Other adapter settings only
say that they are set, since they may hold anything.

Refs #289
2026-09-22 19:35:36 +08:00
Willie 72e87c0d62 fix(ui): import a project's MCP conflict from that project's files
Import from an Agent on a project's conflict read the Agent's global
file and wrote to the global source, so the project's own entry could
never be taken over from there. It now reads that project's file and
imports into the project.

The MCP page also crashed on a cold load: a hook ran after the loading
return, so the first render with data called one more hook than before.

Refs #290
2026-09-22 19:35:32 +08:00
Willie 55b5e2aaff feat(ui): point out MCP servers not yet managed by skillshare
Servers added to an Agent directly never showed up in the dashboard, so
they could only be found by opening Import for each Agent in turn. The
MCP page and each project's MCP tab now note which Agent files hold
servers skillshare does not manage, and Import opens on that file; a
project's import reads the file in that project's folder.

Refs #290
2026-09-22 19:08:51 +08:00
Willie 223bde5bf3 feat(mcp): stop managing a server without touching config files
Removing a server always ended with its entries cleared from the Agent
config files on the next sync, so there was no way to hand a server back
to the Agent. Stop managing drops it from the source and forgets which
entries it wrote; the files stay as they are and sync leaves them alone.
Available as `mcp remove --keep-files`, in the remove wizard and as a
third choice in the dashboard's remove dialog.

Refs #290
2026-09-22 19:08:51 +08:00
Willie 82f88c4ab9 fix(ui): list project targets on the skill and agent detail page
The Skills and Agents lists count project targets in their icon stack,
but the detail page showed only global targets, so the two disagreed.
The detail page now lists each project the resource syncs to and links
to it, since project filters are set per project, not per target.
2026-09-22 17:44:59 +08:00
Willie 8032bdce48 fix(ui): preview in-place sync from the diff
The Skills and Agents sync dialogs previewed with a dry-run, which reports
every existing link as linked again, so they showed changes on targets
that were already in sync and disagreed with the Sync page and the
project dialog. They now read the same diff as the pending dots.

Refs #289
2026-09-22 17:36:43 +08:00
Willie 2ed30eb1f8 feat: sync one project from its page
A project's pending changes could only be written by a full sync, which
also touched global targets and every other project. Sync project on the
project page previews and writes just that project's skills, agents and
MCP; the API takes a project root to scope the resource sync and the MCP
apply.

Refs #289
2026-09-22 15:17:11 +08:00
Willie 0587f32f95 feat(ui): sync skills, agents and MCP from their own pages
Syncing meant leaving the page for Sync and reviewing every part at once.
Skills, Agents and MCP now each have a sync button that previews and
writes only that part in a dialog, and the Go to Sync spots after an
update, uninstall or collect open the same dialog. Pi adapter settings
are shown on hover so they can be checked without opening Edit.

Refs #289
2026-09-22 15:16:40 +08:00
Willie 9d8c7aa4de fix(ui): keep Pi adapter settings when Pi is unticked
Unticking every Agent dropped directTools and piOptions from the source,
so ticking Pi again came back with the adapter reset. The settings now
stay until the adapter itself is changed.

Refs #289
2026-09-22 15:16:26 +08:00
Willie d8c53c1576 fix(ui): keep the account Agent toggle in a fixed order
The available-target list comes from a Go map, so the Agents in the
add-target dialog's account mode changed order on every load. Sort them
by name like the known-target list, which puts claude first and pi last.

Refs #289
2026-09-22 11:28:01 +08:00
Willie bb57a9af9c feat(targets): add account targets for a second Claude, Codex or Pi config directory
A target declared with `agent` and `config_dir` is another config directory of a
built-in Agent, such as a second Claude account. Its skills and agents paths are
derived from the Agent's defaults at load time, so the config only records the
directory. The same target name works for MCP (written in the Agent's format into
the account's own file), for plugins (the Agent CLI runs with CLAUDE_CONFIG_DIR,
CODEX_HOME or PI_CODING_AGENT_DIR) and for `mcp import --from`. Removing such a
target warns when MCP config still names it instead of failing later at sync.

The dashboard gains an "another account" mode in the add-target dialog and lists
accounts next to the Agents on the MCP and plugin pages.

Refs #289
2026-09-22 11:21:35 +08:00
Willie 8ebba4a0f8 fix(ui): show where a project turns a server off as Agents, not fields
The row listed the native field written per Agent in a narrow right-aligned
column, which was tiring to read and meant nothing to someone who has not seen
those files. It now shows the Agents' logos, keeps a sentence only for what
needs a reason, and an old entry with its own Agent list gets a one-click way
to follow the project instead of an instruction.

Refs #289
2026-09-22 02:33:08 +08:00
Willie e4964b6c31 feat(ui): edit piOptions in the MCP server dialog
The dialog rebuilds a server from its fields, so without one for piOptions any
edit from the dashboard would drop what the config holds. It reuses the snippet
editor and refuses text that is not a JSON object, or that sets a field
Skillshare writes itself, before anything is sent.

Refs #289
2026-09-22 02:33:08 +08:00
Willie 626d48fe0a fix(ui): offer only replace for a changed off switch, and name its project
A project's off switch that was edited by hand in the Agent's file shows
up as a conflict with "Import from Agent" next to it. Import reads the
Agent's global file, which holds the server and never the project's
switch, so it brought in something unrelated and the conflict stayed.
Only replacing the entry settles it, so that is the one button offered.

The conflict row also says which project folder it is in: one server
can conflict in several, and two such rows shared a React key.

Refs #289
2026-09-22 02:01:36 +08:00
Willie f1f9ef13ed fix(mcp): leave Pi out of a switch where the project uses another extension
Pi reads one config file per project through one extension. A switch
took pi-mcp-adapter from the global server, so in a project whose own
servers use pi-mcp-extension it put two extensions into one file and the
whole plan failed. From the dashboard that was an error toast on
flipping a switch that had nothing to do with Pi.

Pi has no per-project switch with pi-mcp-extension, so the switch now
skips Pi there and still reaches the other Agents. The project page
says the same: Pi is listed among the Agents that keep loading it.

Refs #289
2026-09-22 02:01:36 +08:00
Willie 1ae5f82b2c fix(mcp): show where a project's off switch really applies
The project page marked a global server "off here" while an Agent with
no per-project switch, such as Cursor, kept loading it in that folder,
and nothing said so. The row now names those Agents.

A switch saved with its own list of Agents does not follow the project.
When that list no longer matches, the row says so and how to fix it.

Two displays worked the targets out on their own and disagreed with
what sync writes: the list of project-only servers counted Pi for a
switch without pi-mcp-adapter, and the terminal manager listed every
inherited target for a switch. Both now use the rule sync uses.

Refs #289
2026-09-22 01:56:03 +08:00
Willie cea405bfa0 fix(mcp): let a project's off switch follow the project's targets
The dashboard stored, in each switch-only entry, the Agents it applied to
at the moment the switch was flipped. Changing the project's targets
afterwards left that list behind: it kept an Agent the project had
dropped and missed one it had added, and nothing on the page said so.
Getting it right depended on doing things in one order.

A switch that names no targets is now worked out on every plan: the
Agents the project uses that have a per-project switch and, under
mcp.projects, that the global server of that name is written to. Pi
takes the global server's piExtension. The dashboard saves the switch
that way, so the result no longer depends on the order of edits.

An entry that lists its targets is still taken as written, and an
unsupported Agent in that list is still an error. One that inherited its
targets used to fail on an Agent without a switch; it now skips it.

Refs #289
2026-09-22 01:17:59 +08:00
Willie 3f46161ef4 fix(ui): line up the stop-managing button in the playful theme
The button is pulled left by its padding so that its icon sits under the
headings. That holds while a ghost button has no border, which is the
clean theme. The playful theme gives ghost buttons an outline, and there
the same pull made the outline stick out past the content above it. The
pull is now a class that the playful theme undoes.
2026-09-22 00:57:53 +08:00
Willie 9a724c3e88 fix(ui): ask before a project drops its own MCP targets
Switching a project back to the global targets saved at once and threw
away the list the project had picked. Nothing on the page said so, and
the only way back was to tick every Agent again. The switch now asks
first and names the Agents that would be dropped. A project with no list
of its own has nothing to lose, so it still switches without a prompt.

Refs #289
2026-09-22 00:55:03 +08:00
Willie bc58d75dea fix(mcp): say a switch-only entry turns the server off, not adds one
Turning a global server off for a project writes an entry that holds
only the switch. The Sync page listed it as "New server entry", and as
"Server entry will be removed" when the server was turned back on, so a
review read as servers coming and going.

The plan now marks those changes. It reads the entry itself rather than
the source, because once the switch is removed the source has nothing
left to say about it. The Sync page uses the mark for OpenCode, Kilo
Code and Pi as well as for Claude Code's off list.

Refs #289
2026-09-22 00:52:52 +08:00
Willie e91b6ac602 fix(ui): turn a global MCP server off only for the project's Agents
Turning a global server off from a project wrote the switch for every
Agent the server reaches, so a project that uses OpenCode and Pi also
got a Kilo Code file and an entry in Claude Code's off list. The switch
now goes to the Agents the project itself uses.

Claude Code keeps that off list in ~/.claude.json, the file that also
holds the user-scope servers. The Sync page grouped both under the one
path and said "Server entry will be removed", which read as deleting the
global server when it only turns the server back on in one project. The
off list is now its own group that names the project, and its rows say
whether the server is turned off or back on there.

Refs #289
2026-09-22 00:45:58 +08:00
Willie 477daf47aa fix(ui): say in the dashboard language that a snippet cannot be read
Pasting something that is not a config showed the server's English error,
worded for a sync: "invalid JSON/JSONC; target was not changed". A paste
has no target to change, so the message was also beside the point.

The errors a snippet or file can produce are now translated and say what
to do: check the syntax, or paste the part that holds the servers.

Refs #289
2026-09-21 23:36:12 +08:00
Willie 97444507bf fix(ui): let a pasted MCP server have no Agent selected
The add dialog's paste tab still asked for at least one Agent while its
form tab no longer did. A pasted snippet is a new server like a typed one,
so it may stay in Skillshare only, and says so instead of warning.

Importing from an Agent keeps the requirement: it takes over the entry
that Agent has, which needs somewhere to write.

Refs #289
2026-09-21 23:30:46 +08:00
Willie bd3a9cf228 feat(ui): let an MCP server have no Agent selected
The dialog refused to save without an Agent, and both the global list and
a project's list refused to untick the last one. With servers now allowed
to stay in Skillshare only, those blocks are gone: the dialog explains what
saving with no Agent means, unticking the last Agent says that the next
sync removes the server everywhere, and such a server is tagged in the list.

With empty defaults an empty selection looked inherited and left targets
out, which the server refuses; the empty list is now always sent. A
project's list of global servers leaves out one no Agent receives, as there
is nothing there to turn off. A switch-only entry still needs an Agent.

Refs #289
2026-09-21 23:21:24 +08:00
Willie 8ec1234d14 fix(ui): localize status and Kilo messages
Route resource and extras status labels through the locale dictionaries. Translate the Kilo project environment-reference error while preserving its project path and server name.
2026-09-21 22:26:09 +08:00
Willie ff4264eb5a fix(mcp): offer a way out of a conflict left by a removed config
A conflict said the entry was managed by another Skillshare config even
when that config was gone, so the dashboard offered no resolution and the
message named a file the user could not find. Such a conflict now reports
the entry as left over, and an explicit import or replacement takes it over.

Only a missing file counts. One that cannot be read may sit on a drive that
is not mounted, where the owner is still there.

Refs #288
2026-09-21 21:20:46 +08:00
Willie e0c1111b79 feat(plugins): add a plugin without choosing Agents yet
Adding a plugin forced at least one target, so keeping a plugin in
Skillshare for later meant installing it somewhere and then deselecting
every Agent by hand.

A package now records its source, so it stays managed with no Agent
bound. Agents are bound later from the same source, installing it as it
is then. Removing the last Agent keeps such a plugin; removing the
plugin itself drops it. In the terminal picker, confirming with nothing
selected records it, while Esc still cancels.

The plugin list also shows the installed version as a tag, and an
update check shows old -> new for plugins whose source has moved on.
2026-09-21 17:18:03 +08:00
Willie f271c93c32 fix(plugins): install marketplaces the way each Agent reads its catalog
One broken or external entry used to fail the whole marketplace, and
valid Claude plugins were rejected because skillshare expected more than
Claude does. Checked against the real Claude and Codex CLIs:

- A bad entry now marks only its own row, with a translatable reason.
- An external entry yields to a catalog that points inside the source.
- Claude plugins without plugin.json are read from their catalog entry
  and default folders, including a root SKILL.md as the only skill.
- Claude entries keep their own definition (strict, skills, lspServers,
  version, ...) in the catalog written for Claude, so entries sharing a
  folder no longer install identical content.
- When catalog and manifest names differ, Claude still installs under
  the catalog name; Codex refuses, so other Agents are blocked.
- When catalogs place the same plugin in different folders per Agent,
  each Agent installs from its own folder.
- The add dialog no longer preselects a plugin that cannot be installed.
2026-09-21 15:50:30 +08:00
Willie 0a16894265 fix(ui): show a spinner while the MCP config preview loads
An empty dialog gave no sign whether the preview was still loading or
had never been requested, so a slow first open looked broken.
2026-09-21 15:50:19 +08:00
Willie 6a13e960a1 feat(ui): let the analyze tab count only skillshare-managed skills
Local skills in a target showed their internal synced/<org>_<uuid> path,
and they inflated the always-loaded and on-demand totals with skills
skillshare does not manage. Local rows now show their folder name (full
path on hover), and a toggle, remembered per browser, limits the list
and the totals to managed skills.
2026-09-21 15:50:19 +08:00
Willie 4660e8133d fix(ui): let the project MCP tab scroll with the page
The rail layout gives its list a viewport-height scroll box, which suits the
MCP page but nests a second scroll area under the project page's header and
tabs, and its narrow padding clipped Playful borders.
2026-09-21 14:05:29 +08:00
Willie 203c40013a feat(ui): tag targets that convert agents in the targets list
The extension was only visible inside a target's Agents tab, so a converted
target looked like any other in the list.

Refs #267
2026-09-21 13:36:46 +08:00
Willie 1ef855e0e6 feat(ui): set an agent target's extension from the target page
Choosing an extension switches the agents mode to copy and locks the mode
picker, matching the rule the CLI enforces.

Refs #267
2026-09-21 13:31:44 +08:00
Willie 56f1cf8100 fix(ui): restore the type-checked build
tsc -b fails on three counts, which the dashboard image build turns into a red
CI. Two came in with the mcp.projects off switch, one is older.

MCPRemoveDialog's inScope predicate now takes a change rather than a path, but
the type it names was never imported, and MCPPage still handed it the old
path-based predicate. That call site has to ask the change for its scope
anyway: a project's Claude Code off switch is written to ~/.claude.json, a
global path, so matching on the path alone would count it as a global change.

ConfigPage passed its tab straight to AssistantPanel, whose mode has never
accepted the extensions tab. Only the branch that excludes that tab renders
the panel, so the value cannot occur; say so at the call site.
2026-09-21 11:08:04 +08:00