Adopting the portable root plugin.json replaced the whole Codex target
info, dropping the interface.logo read from .codex-plugin/plugin.json.
Codex still overlays that native manifest, and the portable one rarely
names a logo, so the add/list UI fell back to a generic icon.
Refs Codex review on #396.
The polling instructions read as applying only after an `@codex review`
comment, so an agent could open a pull request and hand Codex's initial
findings back to the user instead of following them up itself.
A portable root plugin.json without a version left the Codex binding's
version empty, which skips the post-update version check, so an update
could advance the snapshot while Codex still ran an older copy. Codex
reports 1.0.0 for such a manifest, so expect that instead.
Refs Codex review on #396.
Codex 0.159 installs from a portable root plugin.json (agent-plugins.org
schema) ahead of .codex-plugin/plugin.json, and reports 1.0.0 when that
manifest has no version. Skillshare preferred .codex-plugin/plugin.json,
so updating a package that ships both (ponytail 4.10.3) failed with
"native update returned version 1.0.0; expected 4.10.3" on every sync.
Two agents that flatten to the same name matched the same manifest entry
and were both counted, so status could report 2/2 with one output on
disk. Each manifest key now satisfies one agent.
Refs Codex review on #392.
Counting an extension output as synced from its output hash alone missed
the common case: the user edits the agent in the source and runs status
to see whether a sync is due. The output still matched the manifest, so
status, doctor and the dashboard reported no drift although the next
sync would regenerate it.
Sync now records a SHA-256 of the source each output was converted from
in the manifest (sources), and status counts an output only when both
the output and that fingerprint are current. Outputs recorded by earlier
releases have no fingerprint and count as current until the next sync
records one, so upgrading does not show the 0/N the report was about.
Refs #391, Codex review on #392.
When a "!" rule in .skillignore.local overrode a single disable, the handler
returned 409 before its only ops log call, although AddPattern had already
written the pattern to .skillignore. The shared file changed with no trace in
the log. Log the attempt with status "error" and the reason before returning.
Disabling a skill only checked that its path was written to .skillignore.
A "!" rule in .skillignore.local is applied after that file, and an
unanchored one such as "!feature-radar" re-includes every path segment with
that name, so the skill stayed enabled while the dashboard reported success.
The dashboard also never showed the .local file, so nothing explained why.
Single and batch toggles now re-discover after writing and report an item
that did not reach the requested state as failed, naming the overriding
file; the batch toast shows the first failure's reason. GET /api/skillignore
and /api/agentignore return the .local file, and Settings > Files shows its
rules above the editor.
The tree pane's folder switch showed a partial state by only centering the
knob on the off-colored track. On a 34px track that looked like a stuck or
broken off switch. Give the mixed state a half-tone track and a dash in the
knob, the way an indeterminate checkbox reads.
An agent target with an extension writes each agent under output_ext
(reviewer.toml) with transformed content, and the manifest tracks that
output name. status, doctor and the dashboard's Sync tab counted synced
agents by looking for the source name and comparing with the source
content, so every converted agent was missing: status showed 0/N with
drift, doctor said the same, and the Sync tab kept them pending after a
successful sync.
For an extension target, count an agent as synced when the manifest
tracks an output with the same stem and that file still matches its
recorded hash. Matching by stem avoids loading the extension spec in
status paths. doctor keeps reporting leftover broken links for these
targets.
Refs #391
Installing a repo whose root is a skill copies the whole repo into the
source, including any .claude/skills/ the author keeps for their own
development. Install discovery already skips target dotdirs, but the
source walk used by sync, check, and the dashboard only skipped .git,
so those dev-only skills surfaced as nested skills and were synced to
every target.
Share the skip set through sourcewalk and apply it in both source
walks. Only dotdirs nested below the source root are skipped: host-style
paths directly under the root (.cursor/skills/*) stay visible because
they drive target inference.
The global block still offered "a decision with its reason" and "a
pitfall you confirmed" as things that belong in it, so a project
decision matched both blocks. The examples are now per scope: the global
ones name user preferences, decisions that apply across projects, and
pitfalls in a tool; the project ones stay project-bound. Both rules take
the examples as a parameter instead of a string replacement.
Refs Codex review on #387.
An agent that reads both a global and a project guidance block saw the
same body twice, with two "save it here", and had to guess whether a
user preference or a project decision went to the shared folder or the
project one. Each block now says what belongs in it: the global block
points project notes at a project memory when one exists, and the
project block keeps project notes and says that notes about the user,
their tools, or other projects do not belong in it. The project block's
examples follow suit, so it no longer names "a stated user preference".
The active rule's two overlapping sentences on when to save are merged
into one, and the plugins reference describes the older Codex.app path
without reference to current events.
Rewrites the generated notes as user-facing entries with examples, drops
the duplicate Performance line that the #384 merge commit produced, and
syncs the website changelog.
#385 documented the new Source link info row and its --json check in
the English doctor page only; the ja, ko, zh-Hans and zh-Hant pages now
carry the same row and paragraph.
* fix(plugin): find the Codex CLI the desktop app ships
Plugin commands ran the bare name `codex` from PATH, so a machine with only
the Codex desktop app, or a scheduled job started with a minimal PATH,
reported the CLI as missing. The account-only `cli` override did not help:
the default codex target cannot set it, and an absolute path in a config
shared between macOS and Windows is wrong on one of them.
When `codex` is not on PATH, look in Homebrew's folders and the CLI the app
installs (Codex.app on macOS, %LOCALAPPDATA%\OpenAI\Codex\bin on Windows).
SKILLSHARE_CODEX_CLI overrides the search on one machine without touching
the synced config. The missing-CLI error now lists every place searched, in
the CLI and the dashboard.
Refs #338
* docs(plugin): note where Skillshare finds the Codex CLI
The plugin reference and the sharing guide still said every native CLI must
be on PATH, and the built-in skill told agents a missing CLI has no
fallback. Codex now has one, plus a machine-local override that agents
should prefer over a path in a shared config.
Refs #338
* fix(plugin): look for the Codex CLI inside ChatGPT.app
Since the Codex desktop app merged with ChatGPT, macOS installs it as
ChatGPT.app, so an app-only Mac with a minimal PATH still reported Codex as
missing. Try ChatGPT.app before Codex.app in /Applications and
~/Applications, the order Codex's own desktop-app finder uses.
Refs #338
* fix(plugin): run the packaged CLI entrypoint of the ChatGPT app
ChatGPT Desktop 26.924 removed Contents/Resources/codex and ships the CLI
at the entrypoint its package manifest declares, codex-cli/bin/codex, so a
current app-only Mac still reported Codex as missing. Try that entrypoint
first in each app bundle and keep the old path for earlier builds.
Refs #338
* fix(plugin): find the Codex CLI from the Windows installer
The official PowerShell installer puts codex.exe in
%LOCALAPPDATA%\Programs\OpenAI\Codex\bin and adds it to the user PATH. A job
started without that PATH missed it, the same gap Homebrew's folders cover
on macOS. Try it before the desktop app's copy.
Refs #338
* fix(plugin): keep an account's cli even when it is codex
The Codex search ran whenever the executable was the bare name codex, so an
account that set cli: codex could get SKILLSHARE_CODEX_CLI or the app's CLI
instead, against the documented rule that an account's own cli is kept.
Search only when no account cli is set.
Refs #338
Implements rollout steps 1 and 2 of proposals/274-skillfollow.md. Nothing follows a link or parses .skillfollow yet.
Step 1: doctor reports first-level symlinks and junctions in the skills source as info, in text and JSON, without following them.
Step 2a: internal/sourcewalk owns traversal of the skills source. Thirteen raw walks move onto it with identical behavior, and a go/parser ratchet fails the tests on any new unclassified walk.
Step 2b: internal/sourcefs wraps an os.Root opened at the skills source and refuses any write whose path has a link component. The six write sites the proposal found in review move onto it, including the cross-device copy fallback, and a second ratchet covers raw os write calls. The only behavior change is that an explicit path crossing a link inside the source is refused instead of written through.
Refs #274
Release-As: 0.24.3
The --update-mode help described passive as only pointing facts out,
which dropped the on-request saving that the generated rule, dashboard,
and docs all keep.
Refs Codex review on #384.
The active rule asked for one fact per file, while init still creates
LEARNED.md as a multi-lesson log and the docs tell users to have agents
update it. The rule now says which goes where: a fact or decision gets
its own file linked from INDEX.md, a lesson from a failure gets a new
heading in LEARNED.md.
Refs Codex review on #384.
- The LEARNED.md starter said to update only on request, which
contradicted the active memory guidance; it now defers to the guidance.
- website/AGENTS.md hardcoded a command-page count that had drifted and
omitted the Desktop App navbar item.
- wiki/testing.md gave `bash -c` and `bash -lc` as the rule in different
places; it now says which container needs which, and why.
- Migration-relative wording in wiki/architecture.md and an unexplained
"Always use" in the targets reference are stated as current rules with
their reason.
The generated guidance block defined "what is worth saving" the same way
agents' built-in memory does, but never said how the two relate, so agents
with their own memory kept saving there and left the shared folder alone.
The active rule now says to save here instead of tool-specific memory,
gives a note format and an INDEX.md line shape, and both modes read
INDEX.md at the start of each task instead of "when relevant". The
passive rule asks agents to point out facts worth keeping so the user
can ask for them to be saved.
Dashboard mode descriptions, the CLI help, and the website pages are
updated to match. Test fixtures that anchored on "Read only" follow the
new wording.
* chore(main): release 0.24.2
* chore(release): synchronize release metadata
* docs(changelog): describe the 0.24.2 download speedup for users
Release Please lists the raw commit subject; the changelog explains user-visible changes in prose with an example, like earlier entries.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
* perf(upgrade): download release assets over parallel ranges
release-assets.githubusercontent.com throttles each connection on some
networks. The 9.6 MB darwin_arm64 archive took 122-171 s over one
connection but 25 s as 8 ranges, each on its own connection, with an
identical checksum. `skillshare upgrade` and the first `skillshare ui`
of a new version both waited minutes on that download.
DownloadToFile probes with `Range: bytes=0-0`; a 206 answer splits the
file into ranges fetched in parallel from the redirected URL, and a 200
answer streams the single response as before, so servers without range
support cost no extra request. Size limits and checksum verification are
unchanged.
The UI asset download is about 2 MB now, so the docs no longer say 1 MB.
* fix(upgrade): keep the caller's transport for parallel ranges
Each range built its client from http.DefaultTransport, so a caller's
custom transport (private CA, authenticated proxy, custom dialer) only
applied to the probe. The ranges then failed or bypassed the caller's
network setup even though the probe succeeded. Each range now copies the
caller's client with a clone of its *http.Transport, which keeps those
settings and still gives the range its own connection. A transport that
cannot be cloned is shared as is.
Adds proposals/274-skillfollow.md: an opt-in .skillfollow file that lets discovery follow declared first-level links in the skills source, so a tracked repo can live in the user projects directory. Without a .skillfollow, behavior does not change. The proposal answers the three requirements set in #274: a single source walker with a ratchet test, a three-part link ownership contract, and git staging and update rules for followed repos. Writes to the source go through an os.Root handle. Windows junction behavior was verified on a real machine.
Refs #274
Narrowing the side columns made the English Field/Structure/Changes tabs
overflow the 240px panel. Split the tabs evenly with tighter padding,
trim the file list further and give the expanded dialog's panel more
room.
The file list and field panel took more width than they needed and left
the YAML editor cramped. Narrow both side columns so the editor gets the
extra space.
* chore(main): release 0.24.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.24.1 for users
Replace the generated commit list with what each change means for users: the memory update modes with the CLI example, the config layout, the Pi project override, the audit config-key fix and the dashboard hooks count.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
77727bd5 added hooks to the global and project dashboards, between MCP and
Plugins, but the ui reference still listed the counts without them in
every locale.
* fix(mcp): turn off a global server for Pi with its project override
Since Pi 1.0.1, a .pi/mcp.json entry without command, url or type
overrides only enabled, exposure and toolExposure of the global server
with that name, and Pi's own /mcp writes {"enabled": false} for it.
Skillshare still wrote the global server's command (or url without the
query) next to enabled: false. Pi reads that entry as a project server
that replaces the global one, so turning it back on in Pi's /mcp only
dropped enabled and started the server without its args, env or
headers, and a url server lost its query. It also needed the global
server, so project mode refused pi in a disabled entry.
The switch is now the override alone. It needs nothing from the global
server, so project mode accepts it; a switch written by an earlier
release is rewritten on the next sync, and an identical override Pi
already wrote is unchanged instead of a conflict. The dashboard counts
Pi as an Agent with a per-project switch. Pi before 1.0.1 reports the
override as invalid, as the docs now say.
Closes#378
* fix(mcp): compare the whole Pi override before calling it the switch
Codex review on #379: an unmanaged .pi/mcp.json override such as
{"enabled": false, "exposure": "direct"} has the same ownership hash as
the switch sync writes, because that hash leaves out Pi-only fields like
exposure and toolExposure. Sync then reported it as unchanged, although
it differs from the switch and the docs promise a conflict. The check
now compares the whole entry, so only an exact {"enabled": false} is
unchanged; Pi fields a person adds to a switch this config already owns
are still kept, as for any managed Pi entry.
* docs(mcp): say which Pi overrides of a switch conflict
Codex review on #379 read "the override differs from the disabled
entry" as covering a switch sync already owns, where Pi settings added
in Pi, such as exposure, are kept: managed Pi entries keep Pi-only
fields by design (withAgentFields, piOwnedFields), and exposure does
nothing while the server is off. Turning the server back on in Pi
changes enabled, which the ownership hash covers, so that is a conflict.
The docs now say so: an exact {"enabled": false} is no conflict, Pi
settings added to an owned switch are kept, re-enabling in Pi
conflicts, and a differing override sync did not write conflicts.
TestPiSwitchOwnedBySync pins both owned-switch cases.
Config files written by the CLI were marshaled straight from the Go
structs, so sections ran together and plugins, hooks and mcp landed
above sources. Programmatic writes of the global and project config
now sort sections like the dashboard and separate them with a blank
line, keeping the original order when sorting would break a YAML alias.
Also documents one worktree and throwaway container per branch task.
Release-As: 0.24.1
* feat(memory): let each agent choose passive or active note updates
Shared memory guidance only told agents to update notes when asked, so
anything worth keeping was lost unless the user remembered to request it.
Some users want agents to maintain the notes themselves, but because the
notes are shared across every tool, blind writes would fill them with
noise.
Add an active mode whose guidance limits saves to facts that will matter
in later sessions, asks the agent to propose a note when unsure, to update
an existing note instead of duplicating it, and to report what it saved.
Passive stays the default and its block is byte-for-byte unchanged, so
existing connections remain configured.
The mode is recorded in each block's marker, so agents can differ. Agents
that read the same file share one block; the dashboard switches them
together and the API rejects conflicting modes for one file. The CLI
prints either block with `extras memory instructions --update-mode`
(`--mode` already means an extra's sync mode).
* feat(memory): review guidance changes as a unified diff
The side-by-side Before/After panes made users scan two windows to find
the one block that changed. A single Git-style diff shows only the
removed and added lines in context, with removals listed first.
* fix(memory): flag targets that read guidance in both update modes
A tool that imports several shared instruction files can read a passive
block in one and an active block in another. The status showed only the
best-ranked block, so the target looked configured in one mode while the
agent still received the other, and switching modes rewrote just one
file. Report such a target as needing attention instead, so the user
sets the tools on those files to one mode.
* fix(memory): refuse mode switches that would split a target's guidance
A target can read intact blocks in more than one file, such as its own
file and an imported shared file. Switching its mode rewrote only the
file the status pointed at, leaving the other block in the old mode and
creating the contradiction the mixed_modes state reports. Skip such a
switch as multiple_blocks so the user removes the extra block first.
Document guidance modes, mixed_modes and multiple_blocks in the
architecture topic, which still described a single implicit mode.