Shared configs can register roots that exist on other machines. Replace the per-root warning flood with one count and a hint to project list, which already exposes each missing folder in text and JSON. Keep root skipping and sync JSON unchanged.
* fix(config): honor OMP skills directory overrides
OMP reads global skills below PI_CODING_AGENT_DIR, but unpinned built-in
targets still selected the default home. Resolve that runtime default
without changing the canonical template used to derive named accounts.
Keep account scan paths independent of the override and document explicit
path precedence in target guidance and its existing translations.
* fix(config): preserve inferred OMP paths across saves
Saving an unpinned OMP target serialized its resolved skills path, so a
later agent-directory override no longer selected the native location.
Track this fallback with the existing derived-path marker so config saves
preserve its inferred status while explicit paths remain pinned.
Cover save/reload after environment changes and filter edits, and fold
redundant account and project-alias checks into their existing cases.
* docs(config): clarify when OMP skills paths stay fixed
Initialization and target addition save their selected destination, while
an OMP entry with no configured skills path follows later environment
changes. Clarify that distinction in public and built-in target guidance
and all four existing translations.
Keep project alias coverage in its existing owner test and remove
redundant OMP matcher and generic save assertions.
* test(config): normalize explicit OMP account paths
The explicit-path fixture combines a native temporary root with a forward
slash suffix. Clean the actual path for comparison so mixed separators
match the native expected path on Windows, retaining the original path
in failure output.
* test(config): use portable OMP whitespace override fixture
Windows normalizes a directory component ending in a space during native
absolute-path resolution. Use a leading-space component to preserve the
check that override values are not trimmed without depending on trailing
space filename behavior.
* fix(config): preserve default OMP home in account shells
Keep plain OMP skills on the canonical home when its environment override
matches a declared account, so the unfiltered default target cannot bypass
account filters. Share account-aware defaults with discovery and dashboard
selection, and keep canonical account templates separate from runtime homes.
Require an OMP install before automatic detection because Pi shares the same
override. Trim surrounding whitespace, ignore relative overrides, and retain
explicit saved paths. Cover account filtering, aliases, symlinks, saves,
discovery, and existing environment-selected file homes with regressions.
Feature PRs have arrived with a self-ticked "maintainer approved" box on
issues the maintainer never answered, and with large AI-generated diffs
the author could not stand behind. Make approval a label only the
maintainer can add, and state what an AI-assisted contribution owes
reviewers: an author who has read the diff, answers reviews personally,
does not split changes to dodge the size guideline, and makes only
checkable claims.
The Scope line and the end of Step 5 described fix mode differently:
one applied "verified" findings (which can include PLAUSIBLE) and ran the
testing topic's checks, the other applied only CONFIRMED findings and ran
the narrowest check. Keep the rule in Step 5 and point Scope at it so the
reviewer has one rule to follow.
A pathless deepseek-harness or gitlab-duo target resolves its skills
path from DSH_HOME, GLAB_CONFIG_DIR, or XDG_CONFIG_HOME, and the docs
promise it keeps following those overrides. decodeConfig filled the
omitted path in, though, and the next save (editing filters, changing
mode) wrote it back as an explicit path, so later environment changes
were ignored.
Mark a default that came from targetConfigHome as derived, reusing the
mechanism that already keeps config_dir paths out of the saved file.
Closes#661
Release-As: 0.27.1
* Add --all flag to plugin update and enable agy
Add -a/--all to skillshare plugin update so users can update all
tracked plugins in a single command without tying slow target CLI runs
to skillshare update --all or sync --all.
- Reject --all outside plugin update or when combined with a plugin
name or --source-ref
- Share source repository discoveries and discovery errors across the
Preview and Apply lifecycle via Service.WithDiscoveryCache so multi-
plugin marketplaces are cloned at most once per command
- Isolate source, manifest, and target failures per binding when --all
is active so healthy plugins update while partial failures exit
non-zero and leave failed bindings unchanged in config.yaml
- Skip unfiltered OMP bindings during --all updates so sibling targets
on the same package still update without failing the batch
- Enable plugin update for antigravity-cli while skipping disabled
plugins when agy extensions list reports an entry as disabled
Closes#653
* Add plugin update --all to docs and completions
Advertise -a/--all for skillshare plugin across all five shell
completion scripts and document the bulk update workflow and
antigravity-cli update support in the user and built-in skill docs.
- Add --all and -a to plugin completions in bash, zsh, fish,
PowerShell, and Nushell with TestPluginCompletionsIncludeAllFlag
- Document update [NAME | --all], -a/--all, and antigravity-cli source
updates in website/docs/reference/commands/plugin.md (and its
zh-Hans, zh-Hant, ja, and ko translations), sharing-plugins.md, and
quick-reference.md
- Document plugin update --all and antigravity-cli enablement checks in
skills/skillshare/references/plugins.md
* Require known enabled state for native updates
Require a matching EnabledKnown && Enabled inventory entry before
updating copilot or antigravity-cli bindings, and align the localized
plugin workflow pages with the English docs.
- Skip copilot and antigravity-cli updates in Service.Preview and
refuse reinstallation in applyNativeTarget when the binding is absent
from native inventory or not known to be enabled
- Cover absent native inventory in
TestAntigravityCLIUpdateRespectsEnablement
- Synchronize plugin update [name | --all] and Antigravity CLI update
guidance across the ja, ko, zh-Hans, and zh-Hant copies of
quick-reference.md and sharing-plugins.md
The desktop app shows this web UI in a cross-origin iframe and cannot read
its location. After an auto-sync reload it can only return to a route it
knows, so the user lands on the dashboard (runkids/skillshare-app#88).
When embedded, post { type: 'route-change', path } to the parent on every
router location change, where path is pathname + search relative to the
router basename. Standalone pages post nothing.
Use the target data already loaded by the dashboard so account logos do not depend on the slower all-targets request. Keep the all-targets mapping for additional targets.
* docs(proposal): isolate tracked update audits before publication
Concurrent readers can observe rejected revisions before rollback. Propose candidate auditing and exact-revision publication across tracked update entry points without prescribing the staging mechanism. Related to #645.
* docs(proposal): record completed tracked update isolation
Link the implementation in #647 and record private clone staging and exact-revision in-place publication without a multi-file atomicity guarantee. Preserve the proposal as a historical record rather than describing the pre-fix behavior as current.
---------
Co-authored-by: suainam <18585322+suainam@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* fix(update): audit tracked candidates before publication
Prevent rejected tracked-update bytes from becoming readable through published target links by staging and auditing a private candidate before updating the active checkout. Publish the exact approved revision without a second upstream pull.
Preserve sparse state, audit metadata, followed checkouts, and compatible edits. Recover staged and unstaged changes after failed forced publication, including deletions, renames, and sparse exclusions. Cover the boundary deterministically and align error messages and localized documentation.
* fix(update): preserve local bytes across Git line-ending conversion
Overlay dirty worktree bytes after staging candidate patches so core.autocrlf does not silently rewrite local edits. Cover staged, unstaged, and cancelled worktree changes while retaining their index state.
Make permission-failure coverage explicitly POSIX-only and compare private checkout contents to their original bytes. Align red-team assertions with candidate rejection and register private temporary cleanup with the raw-write guard.
* test(install): normalize checkout after configuring line endings
Windows fixtures initially inherit core.autocrlf=true. Reset the isolated checkout after selecting the subtest setting so changing it to false does not turn untouched upstream files into local edits.
Dashboard sync and project sync JSON scanned the agents source again just
for the ignore summary. Carry the full discovery snapshot through sync so
the response describes the agents that were synced, including ignored ones.
Skills-only syncs keep the existing fallback scan.
Cover the handler and project JSON paths when the source changes after
discovery. Check syncProject returns ignored agents and an empty discovery
stays non-nil through execution, so neither path silently rescans.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Use the existing YAML parser and serializer so folded descriptions, quoted text, and nested metadata survive repeated editor saves without accumulating escapes or losing structure. Keep legacy headers editable and render nested object fields as read-only JSON.
Add regression coverage for the MinerU workflow reported in #637 and document editor behavior. Verified UI tests, lint, build, make check, and an isolated browser save/reopen flow.
Add global project list, show, add, edit, sync and remove so setup scripts
can register repositories without editing YAML or opening the dashboard.
Keep dry runs read-only and report completed work when a target fails.
Reuse the shared project service and sync runners. Include command docs,
translations, completions and regression coverage. Quote overlap hints for
their shell and log partial project syncs consistently with ordinary sync.
Return nonzero exit status for failed skill and agent checks while preserving JSON results. Propagate agent remote errors and prioritize dashboard check failures over the up-to-date summary.
Add regression coverage and document exit status in all command reference locales. Related to runkids/skillshare-app#85.
Keep local-edit statuses wide enough so they do not collide with update actions. Wrap update rows on narrow screens and show row actions on touch devices.\n\nReuse the shared dialog for mobile navigation, close it before blocked or successful keyboard navigation, and keep the language picker and tour within the visible mobile UI. Include locale labels, responsive layout documentation, and tour-step regression coverage.\n\nFixes #638.
The handler test used the default test config directory, so it passed
without the oplog routing fix. Select a config in a folder named
skillshare so list, stats and clear prove they use the state-dir log.
Refs #609
SKILLSHARE_CONFIG can select a global config in a directory named
skillshare or .skillshare. Treating it as a project config puts logs and
a .gitignore beside the shared config and labels global logs as project logs.
Exclude selected and read-only global config paths from project routing.
Share the check with the log command so readers and writers agree.
Run the legacy config regression explicitly in Windows CI so it is exercised
without enabling unrelated tests that still need Windows fixes.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Pass --json to agy plugin list and parse the top-level JSON array returned by the Antigravity CLI. Keep fallback handling for empty text output and legacy wrapped envelopes.
Closes#639
* chore(main): release 0.26.4
* chore(release): synchronize release metadata
* docs(changelog): describe 0.26.4 for users
The generated entry lists commit subjects; users need to know what each change does for them and how to use it.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Nested packages sat in a grey inset panel and the folder tree drew one
straight line per level, so neither showed which row a child hangs from.
Both now use one faint spine under the parent with a rounded elbow into
each child that stops short of its checkbox or icon, in an opaque colour
so overlapping strokes leave no darker seam.
Opening and closing a package or folder now grows and shrinks instead of
jumping; collapsed content is inert while it shrinks, and reduced motion
turns the animation off. Nested row actions line up with top-level rows,
and a selected folder's block keeps straight sides.
* fix(ui): warn that uninstalling a package removes its nested skills
Uninstalling a skill moves its whole folder to the trash, so the skills
nested inside it go too, but the confirmation listed only the one skill.
It now counts them in the title, marks the package row and adds a note.
Selecting a package together with its nested skills (select all does this)
also sent every name to the server, which trashed the package first and
then failed on each child whose folder was already gone. The dialog now
sends only the outermost selected skills.
The success toast uses the same count as the title; it reported the
server's per-name count, which read as fewer removals than confirmed.
* fix(ui): keep nested skills of a linked folder root in uninstall
A linked folder whose root is itself a skill can only be unlinked, so the
server refuses to trash it. Collapsing the selection to that root dropped
its selected children from the request and none of them were removed.
A linked root no longer counts as holding its children: they are sent on
their own and the root row does not claim to remove them.
* feat(ui): show skill descriptions in the list and let expand all open packages
Reviewing a large library meant opening each detail page just to read
what a skill does (#627, proposal in #631). The resources list response
now carries each skill's and agent's frontmatter description, read in
the same pass as manual-only, and the list shows it truncated under the
name with the full text on hover.
The read now decodes the frontmatter once for both fields. An unquoted
": " in a description is invalid YAML, so a failed decode falls back to
the line scanner instead of dropping the description and manual-only.
Editing a skill refreshes the list too, so the new description shows
right away.
Expand all / Collapse all also opens and closes nested-skill packages
from #624; before, it only touched source and folder groups.
Closes#627
* feat(ui): redesign list packages as an inset panel with a description switch
The chevron-in-a-column nesting read as a second, unrelated table and gave
no room for the descriptions #627 asks for. A count pill after the package
name now opens its skills in one quiet inset panel, with deeper packages
indented under a faint guide, so the hierarchy stays readable at any depth.
The rest closes the gaps left against #627: a Show > Descriptions switch
keeps the compact list one click away, keyboard focus reveals the full
description, a search opens only the packages holding a match without
overwriting what the user left open, and the selection bar says how many
selected items are out of view. Only the name opens the detail page, since
whole-row clicks were easy to trigger by accident once rows held more text.
* fix(ui): keep linked-folder matches when searching a folder group
Searching while grouped by folder took package ancestors only from skills
whose folderOf matched the group key, but groupByFolder keys a linked
folder's skills by the link name. Every skill in a linked folder fell out
of its own group, so the header counted a match and drew no row. The
ancestor pool is now each folder group's unfiltered skills, keyed by
groupByFolder itself, which always contains the group's matches.
* fix(ui): keep the .ss-r .nm.m rule the design token export reads
Merging it into :is(.ss-r, .ss-nr) .nm.m removed the exact selector that
scripts/design/tokens.py looks up for the row name type scale, so the
design token tests failed in CI.
A package that ships its own SKILL.md plus nested skills used to list
every child as a peer, so one large package could fill the page and hide
which skills belong together (#624, proposal in #625).
The list view now puts each skill under the nearest skill whose folder
holds it, within its current group. Packages start collapsed with a
nested count, a search opens them so matches stay visible, and paging
counts top-level rows so a package is never split across pages.
Selection, select-all and bulk actions still work per skill.
Closes#624
Record the independently requested local use case from #627 for maintainer discussion. Keep adoption optional and leave runtime behavior and the hierarchy-first scope unchanged.
* docs(proposals): describe expandable skill package rows
Large skill libraries flatten package roots and nested skills into peers. Propose path-based list hierarchy and outline optional list context controls while preserving install and sync semantics.
* docs(proposals): narrow skill hierarchy to maintainer feedback
Keep the first implementation focused on real directory ancestry, defer other list ideas, and define root-entry pagination so expanding a package does not split its children across pages. Prefix the proposal filename with its tracking issue.
NewSandbox now resolves its root, so these tests no longer need to
canonicalize macOS /var temp paths themselves. The leftovers were no-ops
that suggested the sandbox could still hand out symlinked paths.
On macOS, TMPDIR sits under /var, a symlink to /private/var. Sandbox
paths kept the unresolved form while the CLI reports canonical paths,
so tests needed per-case EvalSymlinks workarounds. NewSandbox now
resolves its root once.
RunCLIInDir and RunCLIInDirWithInput pass an explicit Env, so os/exec
does not set PWD and the child inherits the test process's PWD. The CLI
then falls back to getcwd and reports the canonical path even when
invoked through a symlinked directory, unlike a real shell. Set PWD to
the requested dir so the helper matches shell behavior.
The affected integration tests now create explicit symlink aliases so
they keep covering aliased working directories and config paths.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Node exposes native localStorage without usable storage when no backing file is configured. Disable native Web Storage for test workers only when the runtime exposes it, allowing jsdom to populate browser storage and preserving Node 24 behavior.
* feat(check): show what changed in a skill since install
#622 made a hand-edited skill visible as modified and kept update from
overwriting it, but there was still no way to see the edits before
deciding to keep or discard them (#621).
LocalChanges compares the skill's files with the hashes recorded at
install, fetches the source at the recorded commit only when a recorded
file changed, and diffs each file against it, so the diff shows the
user's edits even after upstream moves on. A skill without a recorded
commit is refused rather than diffed against HEAD, which would show
upstream changes as the user's.
It backs `check <name> --diff`, GET /api/resources/{name}/local-changes,
and the dashboard: the Modified locally dialog on the skill page lists
the diffs, and the Updates tab links a modified skill to it. update's
skip hints now point at --diff. The route looks up the exact record and
refuses non-local names, so a nested or ../ path cannot borrow a
top-level skill's record or read outside the source. The file diff
helper moved to textdiff so the CLI and server share it.
* fix(install): diff local changes against the full installed commit
entry.Version holds the short SHA from `rev-parse --short`. A targeted
fetch needs the full SHA, so checkoutCommit fell back to fetching every
branch and tag with --unshallow: viewing one edited skill could download
the repository's whole history, and fail when the commit is only
reachable by its full SHA.
Use entry.Commit, the full SHA install records, when it is the same
commit as Version; a Commit left from an older install, or a legacy
record without one, falls back to Version.
* test(install): keep checkout line endings when editing in LocalChanges test
On Windows git checks the installed copy out with CRLF, so overwriting
SKILL.md with LF content made every line differ and the expected diff
failed. Edit the installed file in place, as an editor would, and compare
the diff without carriage returns.
* feat(update): flag and protect skills edited since install
A skill installed from a repository and then edited by hand looked
exactly like an untouched one: check said up to date, and update either
reported it current or silently reinstalled it over the edit (#621).
Install already records each file's hash, so check now compares a
remote skill's files with those hashes and reports "modified", and
update skips such a skill until --force (CLI single, --all/--group,
dashboard). --force, the dashboard's Force Retry on the skipped row, or
the confirmation on the skill page discards the edit and reinstalls.
Two hash paths had to be made reliable for this to be trusted: the
dashboard's folder-wide target edit refreshed hashes by basename, so a
nested skill looked edited after skillshare's own change, and a skill
whose files cannot be hashed now counts as modified instead of being
overwritten.
* fix(server): keep earlier local edits when a target change rewrites SKILL.md
Changing a skill's targets in the dashboard rewrites its SKILL.md, and
both the folder-wide and the single-skill handler then re-hashed the
whole directory as the new baseline. An edit the user had already made
to any file in the skill was absorbed into that baseline, so the skill
stopped counting as modified and the next update overwrote the edit
without --force.
Both handlers now move only SKILL.md's recorded hash, and only when the
file still matched it before the rewrite. skillshare's own target edit
no longer reads as a local change, and an earlier edit still does. The
whole-directory refresh helpers lost their last callers and are removed.
* fix(ui): offer a tracked repo's Update only when a check finds it behind
The Dashboard showed Update on every tracked repo, so a clean repo looked
like it had an update. Clicking it only reported "already up to date" and
the button stayed, which read as an update that would not apply.
The last update check is now kept in the shared query cache, the repo row
shows Update only for a repo that check found behind, and a pull that
succeeds drops the repo from that result so the Update button and the
Needs attention row both clear.
* fix(ui): drop the Dashboard update check when the Dashboard unmounts
Moving the check into the shared query cache kept it for the cache's
10-minute gcTime. An update made elsewhere (the Skills Updates tab, a
single skill update, the CLI) never corrected it, so returning to the
Dashboard still showed the repo behind in Needs attention and offered its
Update button. The old component state was discarded on navigation;
removing the query on unmount restores that for every update path at once.
The skill and CLI version checks keep separate 24-hour caches. The CLI
check refetches once the installed version catches up with its cache, but
the skill check did not, so right after a release the dashboard, status
and doctor could offer the CLI update while calling the built-in skill up
to date. Both ship in the same release, so a cached CLI release newer than
the cached skill version now means the skill cache predates the release.
Importing one plugin per click closed the dialog each time, so the user
had to reopen it and scroll back to the next row. Ticked rows are now
imported in turn while the dialog stays open, and a blocked or failed row
stays ticked for a retry. Installs with resource filters still go through
the single reviewed import, because their preserved native fields need to
be seen first.
Release-As: 0.26.4
* fix(install): use frontmatter names for generic skill directories
Resolve meaningful defaults for generic containers while preserving explicit names, tracked paths, existing update destinations, and directory-based source selection. Fall back on unsafe or colliding names to prevent overwrites.
Cover global and project installs, local and Git sources, naming overrides, tracked reports, collision safety, and updates. Closes#616.
* fix(install): preserve names during source-based updates
Resolve source-based updates against existing metadata before choosing destinations. Reject ambiguous or colliding update targets before writes, and reserve case-insensitive discovery names across filesystems.
Add global/project regressions for local and Git source updates, legacy destinations, grouping, and upstream-added collisions.
* fix(install): retain update ownership and selection checks
Only allow a metadata-verified same-source update to bypass destination conflicts. Reject occupied fallback destinations for both local and Git sources unless overwrite is explicitly forced.
Resolve destinations after skill selection so unrelated conflicts do not block filtered updates. Cover cross-source and unmanaged destinations, selected/excluded updates, and collision aborts in global and project modes.
pnpm 12 fails install when a dependency's build script hasn't been
approved. The pnpm 12.6.0 bump recorded ui's approvals but not the
website's, so devcontainer setup stops at the website install with
ERR_PNPM_IGNORED_BUILDS. Allow @swc/core's native setup and skip the
core-js postinstall banners.
The conflict notice placed its action buttons beside the sentence. With
a project target the "Edit app@claude's project" label is long, so two
buttons squeezed the sentence into a narrow column of short lines. Put
the actions on a row under the sentence, indented like the comparison
table, so the sentence uses the full width.
The hint under a folder conflict linked every target it named to its
target page, but a project target's settings can only be changed from
its project. Link those names to the project editor, as the button
above already does, and drop "on the target page" from the sentence so
it no longer points at the wrong place.
Refs #612
The Sync page offered "Stop syncing skills" for every target a folder
conflict asked to stop. For a project target that button opened the
skills-off dialog, whose preview and update calls the server refuses
with 400 because project targets are configured through their project.
Link those targets to their project's editor instead, and say so in the
doctor docs.
Fixes#612
Replace advisory-matching module versions and their required transitive
versions. Keep application source and test assertions unchanged.
Local candidate build, vet and vulnerability scans pass; retained upstream
and custom UI packaging failures are disclosed in the pull request.
* feat(targets): support OpenCode config directory accounts
OpenCode v2 introduces support for custom configuration directories
via OPENCODE_CONFIG_DIR, storing opencode.json and agent directories.
Previously, skillshare rejected OpenCode accounts configured with a
custom config directory because OpenCode was missing config_dir and
was excluded from accountAgents in hooks and MCP services.
- Define default config_dir (~/.config/opencode) in targets.yaml
- Add OpenCode to account agents and register OPENCODE_CONFIG_DIR
across hooks and MCP service handlers
- Route OpenCode account MCP configuration to opencode.json inside
the account config directory
Resolves#593.
* fix(targets): add OpenCode to schemas, completions and docs
Add opencode to the targetConfig.agent enum and config_dir description
in schemas/config.schema.json so configurations containing OpenCode
account targets pass schema validation.
Include opencode in the target --agent completion scripts for Bash,
Zsh, Fish, PowerShell, and Nushell.
Update website documentation and built-in skill references to describe
OpenCode accounts and OPENCODE_CONFIG_DIR management alongside other
account agents.
* fix(targets): support plugin accounts and overlap
Add OpenCode account recognition and OPENCODE_CONFIG_DIR resolution to
the plugin service so plugin sync works for OpenCode account targets.
Introduce TargetScanPaths to resolve cross-runtime scan paths using
TargetConfig.Agent for account targets while retaining the account's
own primary directory. Update path overlap detection, doctor checks,
and LeakedSkills to warn about leaked skills for account targets.
Update localized docs (zh-Hans, zh-Hant, ja, ko) and plugin references
to document OpenCode account targets and OPENCODE_CONFIG_DIR. Update
the available targets handler test to expect OpenCode's configDir.
* fix(targets): isolate OpenCode accounts and scan paths
Reject OPENCODE_CONFIG overrides when operating on OpenCode accounts
and clear OPENCODE_CONFIG in the account execution environment so
plugin operations target the account directory.
In TargetScanPaths, remap config-root paths to the account directory
while preserving external scan paths like Codex's ~/.agents/skills.
* fix(plugins): use account target in OpenCode update probe
Pass c.Target instead of a hardcoded "opencode" when probing whether
OpenCode supports plugin updates, ensuring account-configured CLI
binaries and account environment variables are used during preview.
* test(mcp): isolate XDG_CONFIG_HOME in account test service
Isolate XDG_CONFIG_HOME to the temporary test directory in
agentAccountService to prevent runner environment variables from leaking
into TestAccountEnvOverrideDoesNotPruneDefaultHome when testing OpenCode
account shell overrides.
---------
Co-authored-by: Willie <egg358358@gmail.com>