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
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.
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
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
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
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
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
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
Every server had to select at least one Agent, so taking a server out of
all of them meant deleting its definition and typing it in again later.
An explicit empty targets list now keeps the server in the source and
writes it nowhere; the next sync removes the entries it had. A missing
list still inherits mcp.targets and is still refused when that is empty,
since a forgotten default is likelier there than intent. A disabled entry
keeps needing an Agent, because it has to turn the server off somewhere.
The empty list has to survive a save, or it would read back as inherited
and sync the server again, so targets are only left out when missing.
In the terminal, --target none writes the empty list, the Agent picker
accepts a confirmation with nothing selected, and mcp list names these
servers, which a plan alone would hide.
Refs #289
On a slow GitHub CDN the ~9MB release archive can take minutes, and a
bare spinner made upgrade look hung, prompting users to abort it.
Show bytes read / total for the CLI and UI asset downloads on a TTY.
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.
OpenCode also loads opencode.json and opencode.jsonc from a project's
.opencode directory. Skillshare looked only at the project root, so a file
kept there was ignored and sync created a second one beside it. It is
resolved the way Kilo Code's .kilo already is: an existing file is reused
wherever it is, a new one goes to the root, and more than one is refused.
Refs #289
Go takes a file's type from the Windows registry when it has one, and a
machine whose registry gets .svg wrong was served icons the browser
refused to draw. Only logos too large to inline are files at all, which is
why Antigravity's broke while the rest showed.
Refs #289
The reference did not mention that add without --target keeps the plugin in
Skillshare and installs it nowhere, listed as no targets, nor that remove
without --target drops the package once no Agent holds it.
Also corrects a claim that every conflict offers an import action. One held
by another Skillshare config that still exists offers none, because only
that config can release the entry.
Refs #288
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
The source recorded for binding Agents later was also compared on every
install, so adding a second distribution for another Agent under the
same package name was refused. It is only where later bindings come
from; installs are checked per Agent as before.
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.
yaml.Marshal defaults to 4 spaces, and only the config package forced 2.
Saving a plugin re-encodes the whole config.yaml, so installing one
reindented a user's entire file; skill/agent frontmatter and
audit-rules.yaml were written with 4 spaces too.
Route all YAML writers (config, registry, plugins, MCP, frontmatter,
audit rules) through one utils.MarshalYAML so they cannot drift apart.
Pi installs a package by its path, and a package.json with only a pi
field is a valid Pi package, but the missing name blocked Pi for it.
OpenCode also installs by path. A package.json name now only names the
plugin when no other manifest does.
A package.json name is the npm name, often scoped (@owner/pkg), so it
rarely equals the plugin name, and Pi and OpenCode install by path, not
by that name. The name check blocked both Agents for plugins that
support them, such as ones published as @owner/plugin.
One dangling link anywhere in a repository, often in the author's own
agent settings and unrelated to any plugin, made every plugin in it
uninstallable. Such links (broken, absolute, escaping the source, into
.git, or closing a cycle) are now left out of the digest and snapshot
and reported as a discovery warning. They are still never followed, and
sources without them keep the same digest, so existing bindings are
unaffected. Special files and the size limits still fail the source.
Plugin installs could only be checked against real Agents on the host.
The CLIs are installed on the dev-home volume so image rebuilds keep
them, and relinked into /usr/local/bin on every start so non-login
docker exec finds them. A failed install warns without blocking start.
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.
Pi prints its version to stderr, so the host showed an empty version.
The fallback applies only to --version with empty stdout, so commands
whose stdout is parsed never see stderr noise.
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.
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.
Skills and agents settings are pointers shared with the live config, so a
request rejected on a later field had already applied earlier ones, and the
next successful save wrote them to disk.
Tools disagree on agent frontmatter and some need another format entirely,
so an agent written for Claude is misread elsewhere. An `extension` on a
target's agents block reuses the extras transform mechanism to convert each
agent during sync.
Converted targets hold transformed output, so collect never pulls them back
into the source. Leftover symlinks from merge or symlink mode are removed
rather than written through, and a failed conversion drops the old output
so an unconverted agent never stays active.
The bundled opencode-agents extension keeps only fields OpenCode documents
and refuses agents that restrict their tools, since dropping those fields
would widen the agent's access.
Refs #267
Refs #241
The pages still said a disabled entry cannot target Claude Code, and that the
field is project mode only. Both are lifted: the entry is valid under an
mcp.projects root as well, and for Claude Code the switch goes to
~/.claude.json, where Claude Code keeps its per-project off list, leaving the
server definitions in that file alone. Only the global mcp.servers, where no
project is in scope, still refuses it.
The dashboard sentence was stale from an earlier change: the switch is its own
"Turn off a global server" button beside "Add server", shown in project mode
and on a project's MCP tab, not an option inside the add form.
All four locales follow, naming the buttons as the dashboard shows them there.
Refs #286
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.
Claude Code keeps its per-project off list in ~/.claude.json, the same file
its user-scope servers live in. The plan keyed desired entries by file path
alone, so one file could carry only one native target, and mcp.projects had
to refuse a disabled entry for Claude Code rather than write that list.
Key the plan by file and target instead. Apply already rereads the file per
plan, and sectionDigest hashes only the target's own section, so two plans
on ~/.claude.json fold in order without further machinery.
A change now carries the mcp.projects root it belongs to. Its path no longer
says, because a project's off switch is written outside that project folder,
and the dashboard needs the root to keep the switch out of the global server
list and to show a pending badge on the project it came from.
Codex stays refused. It merges the project file field by field, so a switch
for a server its global config lacks leaves an entry with no transport and
stops Codex loading its config at all.
Alongside this, the dashboard gets a named "Turn off a global server" action,
so adding a switch and adding a server are two choices up front rather than
one form that asks afterwards. Two older glitches go with it: a project's
target toggles sprang back while the list was still empty, and the expanded
config editor stayed open when a tab arrived from the URL.
Refs #286
The inline editor shares the row with the file list and assistant panel,
which leaves little room for long YAML. An Expand button opens the same
editor and panel in a near-fullscreen dialog. The dialog ignores backdrop
clicks and Escape so an edit in progress is never dismissed by accident.
Teams need to know that skills.lock.json is meant to be committed, which
commands move a pin, and how it relates to the config.yaml manifest.
Covers project-skills, install, update, uninstall, declarative-manifest
and project-setup, in English and the four translated locales.
config.yaml records which skills a project wants, but not which commit
each one resolved to, so two teammates running `install -p` a week apart
could end up with different skill contents.
Project mode now writes .skillshare/skills.lock.json next to the config.
`install -p` checks out the locked commit for skills and tracked repos,
and brings an already installed skill to the lock when they differ.
`update -p` and the dashboard move a pin only for skills whose commit
actually changed, so a stale local copy cannot roll the team back, and
uninstall drops the pin. A locked value is only honoured when it is a
full SHA for the same source, since it ends up as a git argument.
A skill installed into a group had its metadata written to the group
folder instead of the skills root, so it never reached config.yaml and
teammates running `install -p` did not get it.
Two paths left the skills root unset and fell back to the parent of the
skill: `install <git source> --into <group>`, because only Install
derived the root and InstallFromDiscovery did not, and config installs
of an entry with `group:`, in both project and global mode. Both now
resolve the root the same way.
The analyze numbers were drifting from what tools really see. Symlink-mode
targets expose the whole source folder, so .skillignore'd skills still load
but were left out; merge/copy targets often hold skills the user dropped in
by hand that skillshare never counted; and chars/4 undercounted CJK text by
roughly four times.
Route the CLI, TUI, web handler and sync summary through one
sync.TargetSkills so the three copies of the filter logic cannot disagree
again. Disabled skills stay in the discovery with Disabled=true and are
priced for symlink targets; unmanaged folders in a target are reported as
Local. Token estimates now charge one token per wide rune.
The dashboard keeps the chosen target in the URL so target and project
pages can deep-link into the analysis, lists project targets after own
targets with their tool icon, and tags local/disabled rows. Select gives
single-select icons a key to silence a React warning.
Installing from a known repo URL is the common path, so it now leads the
tab list and is where the dialog lands by default. The ?install=search
link still opens the search tab.
Keeps the sync reference in every locale in step with the English page,
which now explains why project sync removes leftovers after a target's
default path moves.
Refs #135
Both tools now document ~/.agents/skills and <project>/.agents/skills as
their skills locations and keep the old directories only for backward
compatibility. Writing to the old path next to `universal` makes them read
every skill from two places.
Global configs pin absolute paths, so they are unaffected and keep their
overlap warning. Project configs store target names only, so an existing
project follows the new default on its next sync while the links it created
in .goose/skills or .openhands/skills would stay behind and show up as
duplicates. Project sync now removes those leftovers from also_scans
directories that no configured target writes to.
That directory belongs to another tool, so the cleanup runs the prune with
ManagedOnly: only symlinks into the source and manifest-tracked folders are
removed. The flat-name heuristic would otherwise delete hand-made folders
such as `_drafts`. Targets with an explicit path are skipped, and --dry-run
only previews.
Refs #135