* chore(main): release 0.30.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.1 for users
The generated entry listed the Release-As commit as a change and used
commit subjects. Replace it with what users see: the Hubs refresh button
and the parallel plugin update check.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The Hubs page keeps a hub's skill list for two minutes and does not
refetch on window focus. The server reads the index fresh on every
request (git hubs are re-cloned), so after someone pushes an updated
skillshare-hub.json the only way to see it was to wait or reload the
whole page.
A refresh icon button next to the filter refetches the list on demand.
It spins and is disabled while loading; the current list stays on screen,
and a failed fetch shows the existing error note above it. Your own
(draft) Hubs are local and do not get the button.
* perf(plugin): check every plugin at once and skip sources that did not move
The Plugins page's update check read every Agent CLI, cloned and hashed
every source, and asked npm about every package one after another, so it
grew with each plugin added. A single Agent CLI that stopped answering
held the whole page at "Checking for updates" with no way to tell which
plugin was stuck.
The check now asks every Agent and checks every plugin at the same time.
Plugins share one read of each Agent and each source, so an Agent with
many plugins is still asked once, and a plugin waits only on its own
Agents, including when proving its own leftover installs. Before downloading a remote source with no pinned ref, the
check asks the remote which commit its default branch points at with
`git ls-remote` and reports no update when that is the installed commit.
A check of three unchanged GitHub plugins on two Agents went from 4.3s
with three clones to 0.6s with none.
The dashboard reads the check from a new stream, GET
/api/plugins/check/stream, that sends each plugin as soon as it is
checked. The page marks rows as they arrive and counts progress in the
header. The stream stops waiting after 60 seconds: a plugin bound to an
Agent that has not answered by then shows "Check failed" with the
reason, and plugins on other Agents are unaffected. There is no limit on
how many plugins run together, because plugins waiting on a hung Agent
would otherwise hold every slot and starve the rest.
A cancelled command did not return when the Agent CLI was a shim that
starts the real client, such as an npm, mise or volta wrapper: killing
the shim left the child holding its output, so the command waited until
the child exited and no timeout took effect. Commands now stop waiting
for output two seconds after they are cancelled; a command that exits on
its own while a helper keeps its output open still counts as answered.
* fix(ui): offer every update the Plugins page shows in the update dialog
The header counted updates from the per-plugin marks, but the update
dialog offered only the targets in the last completed check's plan. Two
cases left the header saying Update N with nothing to tick in the dialog:
a first check that broke off after finding an update never set the plan,
and a recheck that could not reach an Agent kept that Agent's earlier
update while the plan said blocked.
The dialog's plan is now derived from each plugin's last answer together
with the kept updates, so a kept update stands in for the blocked or
missing answer and both always agree. A broken-off check also keeps the
answers it did receive.
* chore(main): release 0.30.0
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.0 for users
The generated entry listed commit subjects. Users need the migration step for the new host rule and what each fix changes for them.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
DNS rebinding lets a page point its own domain at the user's machine,
which makes its requests same-origin to the dashboard, so the CSRF
guard cannot refuse them. Only the MCP, Hooks and Plugins routes
required a localhost or IP Host, so such a page could still install,
sync and push. That rule also blocked those three pages for people who
run the dashboard behind their own reverse proxy (#809).
The dashboard now answers every route only at localhost, an IP address,
the --host name, and origins given with --trusted-origin or
SKILLSHARE_UI_TRUSTED_ORIGINS. Configuration stays outside config.yaml
so the dashboard cannot widen its own trust through its config API. A
trusted origin must match the Host with its scheme, and an Origin
header, when sent, must be that origin. A refused browser gets a page
with the exact setting to copy, the API gets it in the error, and the
server log names each refused Host once.
BREAKING CHANGE: a dashboard opened by a domain name, such as a reverse
proxy, a Tailscale or mDNS name, or a Docker service name, now returns
403 on every page until that address is trusted, for example with
`skillshare ui start --trusted-origin https://skills.example.com`.
Release-As: 0.30.0
A web page can submit a form or a no-cors fetch to the local dashboard
without a CORS preflight, and the handlers accept a text/plain or empty
body. Only the MCP, Hooks and Plugins routes checked where a request
came from, so any site the user visited could add targets, install,
sync, commit, push or upgrade, whenever the browser let the request
reach localhost.
Every POST, PUT, PATCH and DELETE now needs Fetch Metadata, when sent,
to say same-origin, and Origin, when sent, to match the Host. A client
that sends neither, such as curl, is unchanged, because a page cannot
make a browser omit both on a cross-origin request. The update stream
runs updates over GET, as EventSource only opens GET, so it gets the
same check.
The nginx example now forwards $http_host, which keeps the port, since
a proxy that drops it would now fail every change, not only MCP.
The Hooks page uses the same DNS rebinding guard as the MCP page
(requireLocalHooks), so through a domain name or a reverse proxy its
requests return 403. The reverse proxy note only mentioned MCP, so a
user behind a proxy had no warning that Hooks would fail too.
The Claude manifest fallback from #806 offered Codex more than it can
install:
- A Claude package whose only parts are ones Codex does not read, such
as agents, was offered to Codex with no components, so Codex would
install an empty plugin.
- When Codex's own catalog pointed at a folder it rejects, the whole
candidate could be replaced by the Claude catalog's folder, which now
carries a Codex fallback. Codex reads only its own catalog, so it
would never install from that folder.
#806 also stopped every Agent from using a later catalog's folder when
the first one was rejected. Only Codex needs that, since only Codex
reads one catalog exclusively, so other Agents get the old behaviour
back.
Codex accepts Claude plugin manifests natively, but discovery omitted
Codex for packages such as Matt Pocock's skills. Select that supported
fallback without rewriting package resources or invocation policies.
Match native root and manifest precedence, retain rejected own-catalog
packages, and add discovery and snapshot regression coverage.
Refs #805
* chore(main): release 0.29.2
* chore(release): synchronize release metadata
* docs(changelog): write user-facing notes for 0.29.2
The generated entry listed commit subjects, including a docs-only
commit, without saying what users can now do or what the audit fix
prevents.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The dashboard reference walked through each Targets page control but
not the search box #799 added above the include/exclude preview, which
is also shared by project pages and the Extras Edit target dialog.
Release-As: 0.29.2
The #796 wording attached "including direct-file and agent audits" to the
special-target error, so the sentence read as a repeated list and no longer
said that links to ordinary files keep text scanning in those audits. The
translations had dropped that scope entirely. Split it into two sentences
and restore the scope in every locale.
A named pipe can block collection, integrity hashing or uncached skill
metadata reads indefinitely. Require resolved regular files at each read
boundary while preserving symlink accounting and integrity evidence.
Cover the paths with bounded FIFO regressions and generated filesystem
cases, and update the Nix vendor hash and integrity-rule documentation.
* chore(main): release 0.29.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.29.1 for users
The generated entry only listed commit subjects; spell out what changed for people who share config.yaml, how to keep a project machine-local, and the branch picker fix.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: sim <sim@example.invalid>
* fix(projects): save new projects in config.yaml again
v0.29.0 wrote every project add, edit and remove to a machine-local
registry, so a project added on one machine never reached config.yaml
or the other machines that share it (#792). Most people share one
config.yaml and expect a new project to follow it.
config.yaml is the default again. Machine-local storage stays as an
explicit choice: --machine-local on add, or projects_storage:
machine-local for every new project, with --shared to override it.
The new share command moves a local project into config.yaml, and
localize still copies one to this machine. Edits and removals stay in
the layer that owns the project; removing a local copy of a
config.yaml project keeps config.yaml's version unless --shared asks
to remove both, so one machine cannot silently drop a project for
the others. Exclusions written by v0.29.0 are left as they are.
The dashboard picks storage once, in the Add project dialog, and
offers the two removal choices only where both copies exist. Moving a
project between layers stays a CLI command, so the detail page keeps
one job.
Closes#792
* fix(projects): recheck both layers after a confirmation, sync the saved key
remove and share ask before taking the config lock, then compared only
the merged entry after locking. A share or localize from another
terminal moves a project between layers without changing that entry, so
a remove confirmed for this machine's copy could then delete config.yaml's
declaration for every machine, and a confirmed share could overwrite
config.yaml settings changed meanwhile. The recheck now compares the
owning layer and config.yaml's declaration too (ProjectLayerState).
Re-adding a project that v0.29.0 hid restores config.yaml's own key,
which can be spelled differently from the folder given to add (~/app
versus an absolute path). add --sync looked the project up by the given
spelling and failed with "project not found" after saving it; it now
syncs the key that was saved.
* test(projects): make the layer tests hold on Windows
The mutation-sequence test looked the shared project up by
filepath.Join, but the fixture spells config.yaml's key $ROOT/app;
on Windows the two spellings differ, so the lookup found nothing.
It now asks the config for the key it uses.
The remove save-failure test blocked the local registry, but removing a
config.yaml project now writes config.yaml. On Linux the registry check
still failed with ENOTDIR first, which hid the mismatch; on Windows that
reads as a missing file and the save went through. The test now blocks
config.yaml, as the edit save-failure test does, and its hook no longer
shadows the config path with the target path.
---------
Co-authored-by: sim <sim@example.invalid>
A skill installed from a non-default branch of an SSH or other-host
remote (git@host:o/r.git, Gitea, self-hosted HTTPS) could not switch
back to main: the Branch picker was greyed out with "This source can
only use its default branch" (#787). The picker reused /api/hub/refs,
which only lists refs for GitHub, GitLab and Bitbucket web URLs because
a hub entry pins its ref in the URL. Reinstalling from a branch does
not need that; the update endpoint already accepts any git source.
/api/hub/refs now takes anyGit, which lists a non-pinnable git source's
refs while still reporting pinnable=false. The detail page asks for it
under its own query key; the hub editors keep the old request, so they
run no extra ls-remote for sources they cannot pin.
Closes#787
Co-authored-by: sim <sim@example.invalid>
* chore(main): release 0.29.0
* chore(release): synchronize release metadata
* docs(changelog): describe 0.29.0 for users
The generated entry listed PR titles. It now says what each change
does for a user, with examples, folds the #785 follow-up into the
unreleased --min-severity feature it fixed, and credits the
contributors. Both changelog copies match.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: sim <sim@example.invalid>
Co-authored-by: Willie <egg358358@gmail.com>
Checking every user-visible change since v0.28.4 against the docs
found these gaps:
- ui.md: GET /api/audit now returns warnings and incomplete; an
incomplete scan warns instead of reporting all clear and appears
under Needs attention; a project branch switch records the branch in
.skillshare/config.yaml. Also fixes a lowercase sentence start.
- audit-engine.md: Markdown and SARIF carry the per-resource coverage
counts added in #756.
- audit-rules.md: the files row pointed at a "File Scoping" section
that does not exist; it now links to File Applicability.
- log.md: project localize logs a localize action.
- built-in skill: how an unreadable followed source link is reported.
Translations are updated to match.
* feat(audit): show unfollowed source links in Markdown and the TUI
When a followed source link could not be read, only text output (and
JSON's warnings/incomplete fields) said so. A Markdown report looked
like a full scan, and the TUI covered the warnings printed before it
opened, so a partial scan read as complete there. Item 25 of #746 asks
for incomplete status to stay visible in human reports, including
under --min-severity.
Markdown now ends its summary with a "Source links not followed"
section, led by an "Incomplete scan" line when a link could not be
read. The TUI summary line starts with the count in the warning
colour. JSON and SARIF are unchanged.
* feat(ui): mark a partial audit scan on the dashboard
The audit API dropped the source-link warnings the scan collected, so
the dashboard showed a scan that skipped an unreadable followed link as
complete. Item 25 of #746 asks for incomplete status to stay visible in
every human report, the dashboard included.
GET /api/audit and the stream's done event now carry warnings and
incomplete with the same meaning as `audit --format json`, and the
Audit page shows the count beside the Skills/Agents tabs.
* feat(ui): stop calling an incomplete audit scan all clear
After a scan that skipped an unreadable followed source link, the
Audit page still toasted "no dangerous content" and the Dashboard's
Quick Scan toasted "All clear", while the home page showed nothing,
so a partial scan still read as a clean one there.
Both toasts now warn that the scan is incomplete, and the home page's
"Needs attention" list gets a row linking to the Audit page. One
helper words the note for the Audit page label, both toasts and the
row.
---------
Co-authored-by: sim <sim@example.invalid>
With --min-severity set, the TUI dropped every result without visible
findings, so clean skills disappeared from the list and the tab count
shrank, while text and Markdown output kept them. The rule now lives in
audit.HiddenByFloor and both the TUI and text output use it: a floor
hides only a result whose findings all fall below it and that is not
blocked.
The dashboard severity buttons label themselves with the English
severity, matching the badge they show, so the six translated label
keys added for them are gone. AuditPage.test.tsx again asserts the
exact coverage line and count instead of any three digits, and drops a
rendered test that only checked translated labels. The audit-engine
paragraph about --min-severity now appears in all four translations.
Co-authored-by: sim <sim@example.invalid>
Reduce audit report noise without changing full findings, risk scores, severity gates or machine output. Reuse existing severity ordering and dashboard selection, and keep visible/hidden counts and incomplete-scan status explicit in human reports.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Willie <egg358358@gmail.com>
* feat(audit): inspect bundled hooks and settings
Bundled declarations can schedule commands and broaden permissions outside SKILL.md, while ordinary scanning skips hidden settings. Inspect the four explicit paths with bounded root-confined reads and structured findings so existing audit policy can review their potential execution.
Keep activation conditional and redact arbitrary arguments before reports. Register rule metadata through the existing structure analyzer and cover benign twins, parse gaps, source links, policy overrides, CLI/API output and a synthetic E2E runbook.
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
* refactor(audit): parse bundled hook commands with a shell parser
The hand-written lexer for hook commands grew six similar quote and
paren scanners, and each review round found another shell form it
missed (comments after line continuations, nested backticks, `time -p`).
Parsing with mvdan.cc/sh/v3/syntax follows quoting, comments,
substitutions, loops, functions and heredocs the way bash does, so the
analyzer walks every call in the syntax tree instead. The wrapper table
(sudo, env, timeout, xargs, bash -c, git) and the POST and destination
rules are unchanged, now applied to unquoted argv words. A script fed to
a shell on stdin (`bash <<'EOF'`, `bash <<<`) is parsed like `bash -c`.
Statements before a syntax error are still inspected. bash runs some
forms the parser rejects (an array element assigned before a command),
so a rejected command also gets a word-level network check next to its
coverage gap, rather than dropping to MEDIUM.
The dependency adds about 0.26 MB to the release binary; vendorHash
follows the new go.sum.
* fix(audit): bound nested shell parsing and skip stdin data
A script nested in a substitution was inspected twice, once by reparsing
the outer shell's argument and once by walking the outer syntax tree, so
each `bash <<< "$(...)"` or `bash -c "$(...)"` level doubled the work and
a hook under 1 KB could stall an audit. Results are now remembered per
script text and depth, and one hook command may parse at most 1 MiB of
source in total, since deep nesting still costs quadratic time with the
cache alone. Past the budget the command is classified word by word and
gets a coverage gap, as a rejected command does.
Stdin was also treated as a script whenever a shell had a heredoc or
here-string, but `bash -c 'cat' <<<` or `bash ./script.sh <<<` hands it
to something else as data, which turned a lifecycle hook into a false
HIGH. Stdin is now parsed only for `-s`, or when there is neither `-c`
nor a script file operand. Option values (`-euo pipefail`, `-O extglob`,
`--rcfile f`) are not mistaken for a script file.
---------
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: sim <sim@example.invalid>
* feat(ui): show a skill's branch and switch it from the detail page
A skill installed with --branch looked the same in the dashboard as one
from the default branch, and moving it to another branch meant a manual
reinstall from the CLI (#783).
The list, tiles, tree pane and Updates tab now tag the branch a skill was
installed from. The detail page lists the source's branches; picking one
confirms, then reinstalls through POST /api/update with a new `branch`
field, so the audit gate and the local-changes check still apply and a
branch without the skill leaves the install in place.
In project mode, reconciling config.yaml only added missing skills, so a
reinstall from another branch (the switch, or install --branch --force)
left config.yaml naming the old branch while the lock pinned the new
commit. Reconcile now moves the declared branch with the record.
Closes#783
* fix(update): make branch switches install the requested branch safely
Codex review of #784 found four ways a switch could misreport or lose work:
- A root skill installed as a full clone took the pull fast path on later
switches, pulling its current branch instead of the requested one. The fast
path now applies only when the checkout is already on that branch.
- A branch whose skill folder lacks SKILL.md replaced the skill with a plain
folder. A staged update now refuses a candidate without SKILL.md when the
installed copy has one, and keeps the install.
- Reconciling config.yaml from local metadata could rewrite a teammate's
newer branch declaration back to a stale one on an unrelated install. The
generic reconcile change is reverted; the switch updates only the switched
skill's declaration.
- The config editor cache kept the old branch after a switch, so a later save
could undo it. A successful switch now invalidates the config query.
---------
Co-authored-by: sim <sim@example.invalid>
Keep machine-specific project changes out of shared configuration while preserving shared registrations and making their origin visible. Handle missing replicated roots and preserve startup maintenance for mutating commands.
Extension and size filters could hide native executables and Python bytecode
inside document, image and cache paths. Classify bounded headers before those
filters, retain source boundaries, and report opaque and oversized file counts
separately from auditable text.
Keep archive signatures and uncertain headers informational rather than claiming
runtime analysis. Honor analyzer selection for file and dashboard scans, and
cover renamed payloads and benign twins with synthetic fixtures and fuzzing.
Implements item 7 of #746.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: sim <sim@example.invalid>
Existing URL and code-execution signatures miss cloud metadata access and
language-specific deserializers. Add scoped static evidence and inspect safe
YAML and torch options within each call so safe siblings cannot hide risks.
Validate and preserve file applicability across overrides, scans and rule
listings. Collect PHP scripts and propagate rule-load errors so malformed
filters cannot silently disable global scanning. Document the policy and
limits with paired regressions, fuzzing and an isolated CLI runbook.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: sim <sim@example.invalid>
Co-authored-by: Willie <egg358358@gmail.com>
Required local references can currently escape a skill bundle or fail silently
when written as images and explicit code paths. Resolve them within the declared
root without reading external targets, retain dangling-link compatibility, and
share the findings and rule controls with doctor. Keep metadata and integrity
fallback reads within the same root so they cannot reopen skipped symlinks.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Willie <egg358358@gmail.com>
Long blank spans and repeated filler can move meaningful instructions out
of view during skill review. Add four padding signals under the static
analyzer with Markdown exemptions and original-source line mapping.
Reuse rule overlays so global and project toggles and severity/confidence
overrides also govern this file-level detector. Cover threshold boundaries,
benign examples, optimized scans, reports and CLI rule controls.
Implements item 17 of #746.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Willie <egg358358@gmail.com>
* feat(herdr): hide disabled rows and group In sync by source
A source with many disabled skills buries the few rows that need
attention, and a long In sync list gives no sense of where skills
came from.
- Disabled rows are hidden by default; "Show disabled · n" lists them
again and the choice is kept. A disabled hook with pending changes
stays visible because it still needs a sync.
- In sync skills and agents can be grouped by their source repository
(By source) or shown flat (List); a source with one row stays a
plain row, and a filter opens every group.
- Opened plugin and MCP rows show their source, version and targets
instead of an empty detail area.
* refactor(herdr): move the panel's logic out of main.js into testable modules
The bugs fixed in #773, #774 and #775 sat in main.js code that imports
Herdr, so node could not test it: the detached-job polling, the busy
state, and perform's op chain. Only model.js's parsing had tests.
Each concern now lives in a module that takes Herdr's functions as
arguments, so herdr/tests runs it:
- jobs.js runs skillshare: short reads as one exec, longer work
detached and polled, with the sweep of old job folders and one
JOB_MINUTES limit shared with SWEEP.
- channel.js carries requests, notices and one lock per machine
through shared values. The install dialog used to check only a
global busy string and then run without the lock; it now takes
that machine's lock. Holders refresh the lock before each command
and an untouched lock expires after a minute, because a dialog's
task ends without cleanup when it closes.
- operations.js holds what each request runs and the conflict
handling of a pull; perform only takes the lock and shows progress
and the result.
- loader.js reads the Resources data and the Machines cards, and runs
status alongside the snapshots.
The skillshare layout is now published at herdr.dev/layouts, where one
agent prompt installs it without copying files by hand. Offer that path
first in the Herdr guide (all locales) and the panel README, and keep
the manual steps for anyone who wants to merge blocks into their own
layout.
* feat(herdr): add Hooks tab with confirmed entry actions
Show hook declarations and planned changes alongside the other resource kinds, reusing sync --all. Keep nested roots and cleanup status read-only, and confirm enable, disable and remove before saving.
Cover inventory states and scoped action arguments with fixtures; update panel documentation and translated kind lists.
* fix(herdr): preserve hook diagnostics and cleanup failures
Keep inactive reasons and plan warnings visible independently of file actions. Retain an inventory status row when cleanup preview fails after the final declaration is removed, and format root conflicts without an empty target prefix.
Add producer-shaped regression fixtures and document confirmed actions and CLI/dashboard conflict recovery across the panel guides.
* fix(herdr): separate hook notices from named resources
Keep diagnostic notices visible and filtered without inflating entry counts or groups. Propagate root-wide conflicts to affected entries and preserve inactive reasons independently of file alignment.
Show full nested root identities and offer scoped Sync for unnamed native writes. Cover projection and scoped snapshot reads with fixture-only tests, and align panel guides and translations.
* fix(herdr): distinguish unknown hook status from pending sync
Show entries with missing previews outside sync groups and report each scope error once. Preserve disabled state beside runtime diagnostics and omit unchanged targets from pending summaries while retaining expanded details.
Regress the confirmed presentation failures before fixing them, consolidate overlapping fixtures without dropping distinct checks, and align panel guides and translations. Keep source action eligibility because the CLI previews each changed draft.
* chore(main): release 0.28.4
* chore(release): synchronize release metadata
* chore(release): write user-facing notes for 0.28.4
The generated entry listed commit subjects, including the release
request, the withdrawn release commit and fixes to the Herdr panel that
was never released before. Readers need what changed for them: the Nix
flake, Nix-aware upgrades, the new panel and the agent source fix.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* fix(update): keep an agent's source when updating it
After the first `update agents`, an agent's recorded source became
`/agents/<name>.md` with type `unknown-subdir` and no repo URL, so
`check agents` stopped looking upstream and later changes never arrived
(#777).
The batch path rebuilt the repository source from the clone URL, subdir
and branch only, leaving Raw and Type empty, and the metadata written
back was built from that empty Raw. The fallback reinstall and the
dashboard update kept the agent's full source as Raw while clearing the
subdir, so the written source repeated the agent path.
AgentRepoSource now rebuilds the repository source once, by cutting the
agent path off the recorded source, and all three paths use it, so the
source written back is the one install recorded.
Agents whose metadata was already rewritten have no repository left in
it and need to be installed again.
* fix(check): compare each agent at its own branch and report unchecked agents
Agent update checks gave wrong answers in several cases next to #777:
- Agents from one repository were compared with the first agent's
version, so an older agent sharing a repo with a current one never
showed its update.
- The installed branch was never sent to the remote, so an agent pinned
to a non-default branch was compared with the default branch head.
- A tracked agent repo records its full commit while the remote hash is
abbreviated, so a fresh clone always read as update_available; its
checked-out branch was also ignored.
- `update agents` printed "All agents are up to date" and exited 0 when
agents could not be checked at all: an unreachable remote, unreadable
metadata, or a source erased by the #777 bug.
Each agent is now compared with its own version at its own branch, and
an agent whose source the old bug erased reports an error asking for a
reinstall, since its metadata no longer names a repository. Update lists
the agents it could not check and exits non-zero, counting them apart
from agents that failed to update. The docs describe the error status
and the reinstall fix.
* fix(update): repair dashboard-doubled agent sources and share the update flow
Review of the previous commits found gaps in recovering agents that
earlier updates broke, and in how the two update handlers report them:
- A dashboard update before the #777 fix appended the agent path to its
source a second time. Those agents keep their repo URL, so check offers
an update, but discovery then failed on the doubled path. Every copy of
the path is now cut, and the update writes the source back correctly.
- On the dashboard, an agent whose source the CLI bug erased failed with
"invalid source: source cannot be empty". AgentRepoSource now returns
the same reinstall error check shows, and both use one detector.
- When every tracked agent was such an erased agent, no remote was asked,
so the "Checking agents" spinner was never stopped and drew over the
error rows. It is now stopped once the check returns.
- The global and project handlers repeated the check-and-update flow,
and the project copy had already drifted (no dry-run log entry, spinner
in --json). Both now run one shared flow.
Tests cover the erased agent next to an updatable one in global, --json,
--dry-run and project mode, and the doubled and erased sources in
AgentRepoSource.
The 0.28.4 Release PR (#767) merged, but GitHub's incident kept its
search index from listing the merged PR, so no tag or draft was made.
0.28.4 should now also ship #778, which the merged release commit
cannot include. Restoring the 0.28.3 manifest and changelog lets
Release Please open a fresh 0.28.4 Release PR over the full range.
Release-As: 0.28.4
* chore(main): release 0.28.4
* chore(release): write user-facing notes for 0.28.4
The generated entry listed commit subjects, including the release
request and fixes to the Herdr panel that was never released before.
Readers need what changed for them: the Nix flake, Nix-aware upgrades,
and the new panel. Also syncs the skill version and website changelog,
which the Release Please run skipped after GitHub rejected its push.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* feat(ui): show the install's own upgrade command in the update dialog
The update dialog always offered `skillshare upgrade` for the terminal.
On Nix that command only prints advice, and Homebrew users are better
served by `brew upgrade skillshare`, so the right command appeared only
after a click on Update returned an error.
/api/version now detects the install method, reports its command as
upgradeCommand, and looks up the latest version the way the CLI update
notice does for that method. The dialog shows that command, or the
existing "update your Nix configuration and rebuild" text when a Nix
configuration provides skillshare, so no new translations are needed.
* fix(ui): keep `skillshare upgrade` in the update dialog, add only a Nix note
Review of the previous commit found three regressions:
- `skillshare upgrade` already runs `brew upgrade` on Homebrew and also
updates the built-in skill. Showing `brew upgrade skillshare` (or the
nix profile command) instead broke the case where only the skill is
outdated: the shown command updates nothing.
- /api/version looked up the latest version through `brew info` on
Homebrew, inside the request with no timeout. Homebrew's auto-update
could stall the dialog, and a server without brew on PATH never showed
an update.
- The rendered dialog tests only checked shown text, which
wiki/frontend.md says to leave to screenshots.
The dialog keeps `skillshare upgrade` and the GitHub lookup. /api/version
reports nixUpgradeCommand only for Nix installs, and when a newer CLI is
pending the dialog adds the existing Nix advice under the command. The
decision lives in nixUpdateNote, unit-tested in upgradeError.test.ts.
#764 changed how upgrade and doctor treat Nix-store binaries but only
tested the version and server layers. A later edit to upgradeCLIBinary
could start replacing a store binary, or drop the note the dashboard
matches for its 409, without any test failing. Two package variables
let the tests fake the executable path and the latest release.
The ui.md pages said /api/upgrade refuses Nix installs. It still
updates the built-in skill and answers 409 only when a newer CLI is
waiting, and the dialog shows `skillshare upgrade` until clicked.
Herdr users run several agents side by side and had to leave it to see
which skills need an update or a sync. The panel brings that view, plus
install, update, uninstall, audit hand-off and source repository sync,
into a Herdr layout node so it survives space switches.
Install audits its own shallow clone first, because install --json names
a blocked skill without its findings; a block shows them before anything
is written. Pull conflicts show both versions side by side, and
.metadata.json merges per entry with the same rule as MergeMetadata so
installs from both machines are kept.
model.js has no Herdr imports, so make test-herdr covers it in make check
and CI. Docs gain a learn/with-herdr page with translations and a README
highlight, and the context router loads herdr/AGENTS.md with frontend.
* feat: add Nix flake and stop self-upgrade of Nix-store installs
Add flake.nix with packages, overlays.default, checks and a formatter,
building nix/package.nix with the unit tests in the Nix sandbox. The
version comes from the Release Please manifest, so releases need no Nix
edit. A Nix workflow runs `nix flake check` on non-docs changes.
`skillshare upgrade` now detects binaries under /nix/store/ and prints
`nix profile upgrade skillshare` instead of replacing a read-only store
path; update notices and doctor suggest the same command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(upgrade): give Nix installs the right update path everywhere
The first flake commit sent every /nix/store binary to `nix profile
upgrade`, failed a plain `skillshare upgrade` with exit 1 even when the
CLI was current, and left the dashboard with a generic 500.
- Tell `nix profile` installs (the profile manifest lists the store path)
from NixOS, Home Manager and overlay installs, which are told to update
their configuration and rebuild. Detection lives in one helper shared by
the update notice, doctor, upgrade and the dashboard.
- `upgrade` on Nix reports "already up to date" or prints the hint and
exits 0; the built-in skill still updates.
- The dashboard runs the upgrade so the skill updates, then answers
409 `upgrade.nix` with the command when a newer CLI waits on Nix. The
UI shows localized text for it in all 11 locales.
- Installs skip the unit tests; the flake's checks enable them. postPatch
lowers only the go directive's patch version and fails evaluation with
a clear message when go.mod needs a newer Go minor. CI also builds the
package on macOS.
- Docs, translations, the built-in skill reference and the release topic
describe the new behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A returning machine can retain an old runtime link after shared plugin intent changes source. Review its verified scoped cleanup together with replacement, then remove the old link before installing the new source while retaining shared cache and settings.
Preserve the original recipe identity when cleanup of a pending-only installation fails, so retries still reconcile the replacement. Add filesystem-backed regressions, Hegel ownership properties and a two-machine native CLI runbook.
Since v0.19.12 the docs say a project's skills/.metadata.json is
gitignored, but no code ever wrote that rule, so `git add .skillshare`
picked it up (#759). The file records this machine's installs (hashes,
timestamps) for folders that are themselves ignored; teammates already
share config.yaml and skills.lock.json, so committing it only adds noise
and merge conflicts.
ReconcileProjectSkills runs after every project install (CLI, search,
dashboard, move, trash), so it now adds the rule for the skills and
agents sources, at the path ProjectGitignoreTarget computes. Projects
initialized earlier and custom sources get it on their next install.
AdoptMovedProjectSkills is untouched, so `sync -p` still leaves
.gitignore alone (#547). Global mode keeps committing its metadata.
The docs that list the project .gitignore contents now name the
metadata files, and project-skills explains the one-time
`git rm --cached` for projects that already committed it.
Closes#759
prompt-injection-1 reported a JS `ignore: ['**/*.test.vue']` option and a
Python `root: Path, lang_filter: set[str] | None = None` parameter as
CRITICAL prompt overrides, which blocked `update --all` for vuejs-ai and
dotnet skills. The #376 exclusion only covered scalars, root paths and
ignore objects.
The exclude now also accepts an inline ignore array of quoted items
without spaces, and a typed root parameter whose types are capitalized or
builtin names, followed only by further `name: Type` parameters. Both are
limited to the key whose real configs use them, so `admin: Execute`,
`system: Path, Ignore` and comma-joined word lists stay CRITICAL.
Closes#749
* feat(audit): detect narrow prose risk directives
* fix(audit): honor link confidence and narrow refusal rule
Apply configured confidence to Markdown link findings and require safety-related evidence in anti-refusal directives to avoid ordinary compliance false positives.
* fix(audit): address prose and confidence review feedback
Narrow prose matches, preserve overrides when enabling rules, and expose effective confidence to rule consumers. Expand Markdown coverage and synchronize the audit guidance.
* fix(audit): retain scheduled payload detection
Keep detecting directives that schedule a payload while excluding ordinary payload processor terminology.
* fix(audit): preserve prose detection recall
Recognize concise disclosure and safety override directives while retaining benign exclusions. Share the confidence default and cover replacement overlays.
* fix(audit): detect quantified refusal directives
Retain detection when a directive refers to any or every user request while preserving benign security discussion.
* fix(audit): distinguish execution errors from findings
Return a separate exit code for audit errors so CI can tell an incomplete scan from a threshold finding. Preserve partial reports and give scan errors precedence when both occur.
* fix(audit): keep list and abort exit codes consistent
Preserve audit execution-error classification when list delegates to audit, so both global and project actions exit 2. Treat declining a large scan as a clean cancellation before any scanning or error logging.
Cover both paths with real terminal regressions and keep the documented exit-code contract aligned across translations.
Finder writes .DS_Store into any folder it opens, and Explorer writes
Thumbs.db and desktop.ini. These counted as skill content, so opening an
installed skill in a file manager made check report it as modified, hid
update_available, and made update skip it unless run with --force, which
also lowers the audit threshold.
Skip them when hashing a skill, drop hashes earlier versions recorded for
them (from .metadata.json and from legacy sidecar migration), and keep
audit integrity from reporting them. Their content is still audited.
Closes#743
The project MCP tab now shows which Agents load an enabled global server
(cc4c9e43), but the reference only described the logos on servers that
are off. Document both before 0.28.2 ships.
Adding a server a user already set up in another project meant typing it
in again. The project MCP tab's Add server dialog now has a "From another
project" tab that fills the form from a server another mcp.projects root
has. The copy leaves out that project's targets, so it follows this
project's Agents. Off switches are not offered.
Closes#678
* fix(trash): keep install metadata when restoring from the trash
Uninstall pruned a skill's, tracked repo's or agent's entry from the
central .metadata.json, and only the files went to the trash, so a
restore brought back a remote install as a local one: update and check
no longer knew its source (#679).
Uninstall now saves the entries it prunes, with their audit acceptances
and target overrides, beside the trash entry, re-keyed to the trash
name so they match where restore puts the item. uninstall.Restore and
RestoreAgent merge them back after the files return, and every restore
path (CLI, trash TUI, dashboard) goes through them; the dashboard
passes its cached store so it does not go stale. The saved copy is
taken with the same rule RemoveByNames uses and copies each entry, so
legacy repo-group entries are kept and re-keying never touches the
live store.
In project mode uninstall also drops the skill's .gitignore rule and
lock pin, so a skill restore reconciles the project skills afterwards.
trash.Delete removes an entry with its saved metadata, and replaces the
direct RemoveAll calls in delete, empty and the 7-day cleanup. Items
trashed before this change have no saved metadata and still restore as
local.
* fix(trash): keep live records of another path when restoring metadata
A legacy store keys a grouped skill by its basename, so the saved copy of
frontend/foo was keyed "foo". If a different skill was installed as
root-level foo while frontend/foo sat in the trash, restoring it replaced
the root skill's record and lost its source.
Extract now writes full source-relative keys (legacy repo-group entries
keep theirs, since their Group is not their path), and Merge keeps a live
entry whose key names a different path instead of overwriting it. Merge
is shared by skill and agent restore, so both are covered.