* feat(omp): add native Oh My Pi support
Support OMP skills, instructions, MCP, code hooks and guarded extension selection using its verified native contracts rather than Pi aliases.
Add reviewed marketplace plugin installation, cache-preserving scoped removal and fresh-cache reinstall. Align Pi/OMP extension cards and localize inventory guidance while keeping native ownership and read-only constraints.
Include regression coverage, isolated E2E runbooks, documentation and verification policies. Native plugin updates and unverified runtime platforms remain guarded.
Refs #409
* fix(omp): guard runtime ownership and localize inventory guidance
Native install recursively replaces its runtime destination, and a missing cache manifest could leave the real runtime link installed after removal. Bind and recheck an absent reviewed destination, and recover removal names only from verified scope-local links.
Localize fixed backend reasons and warnings across dashboard locales while preserving paths and external diagnostics. Restore the reviewed source in the existing reinstall fixture and record real native verification.
* fix(omp): allow forgetting natively removed plugins
A different plugin can retain node_modules after native uninstall deletes this installation. When its cache, registration and known runtime state are absent, forget only the stale Skillshare binding instead of demanding runtime-name proof for unrelated files.
Extend the existing removal recovery test with a failing-before-fix case that verifies the binding is dropped and unrelated native lock bytes and plugin files are preserved. make check passes.
Separate user-owned followed Git checkouts into linked_repos in check and resources responses so the Updates tab renders information instead of tracked errors or retry actions. Refuse dashboard updates before Git runs, including force retries and descendant skills, while leaving managed repositories unchanged.
Keep one follow policy per list and status operation and report its skipped links without hiding healthy inventory. Send JSON diagnostics to stderr and expose sourceLinkWarnings in the dashboard resources response, reusing the sync warning formatter.
The sticky band stacked the title and the filters on two rows and padded
both ends by 24px, which left a large empty strip above and below the
filters. Merging them into one row removes the gap.
Refresh reloads every memory query (the note list and note contents), not
just the sidebar, so it belongs with the page-level actions next to
"New note". Next to the search box it crowded the sidebar and pushed past
the note tree's edge.
The Syncing column described what a target gets as one line of text,
and the whole row led to the Skills tab, so reaching a target's MCP,
Hooks or instruction file took an extra click and a search for the
tab. Each part is now its own link into that tab, and the connected
shared AGENTS.md shows up by its file name, so the list says at a
glance which targets are not connected yet.
* feat(memory): add a refresh button and keep short facts in INDEX.md
Agents write shared memory notes from outside the dashboard, so the note
list and content went stale until the page was reloaded. A refresh button
in the note header refetches both.
The active guidance also told agents to create a separate file for every
durable fact, which produced one-sentence files. Short facts now go
directly under Notes in INDEX.md; only multi-paragraph notes get a file.
* fix(ui): keep the memory refresh button available without a selected note
The button lived in the note header, so a search with no matches hid it
and the list could not be refreshed to pick up a note an agent had just
written. It now sits next to the search box.
The pending-changes bar was a full-width sticky box, unlike the floating
toolbar used for bulk selection elsewhere in the dashboard. Reusing
.ss-bulk keeps both bars consistent across Clean, Playful, and dark themes.
Codex review on #400: the previous fix preferred Pi's installed version
only for npm packages. Pi reads the package.json of every installed
package, git and local ones too, and plugin import records the version it
saw, which a later pi update does not rewrite. An imported git package
moved from 1.0.0 to 1.1.0 kept showing 1.0.0. On a Pi target the page now
prefers what Pi reports for any package, and falls back to the recorded
version.
Codex review on #400:
- Now that Pi reports an installed npm package's version, plugin import
records it in config, and nothing rewrites it after a pi update. The
Plugins page preferred that recorded version, so an imported package
kept showing its import-time version. For an npm package the page now
prefers what Pi reports installed, and falls back to the recorded one.
- When the package reached the checked version before the update ran,
the update preview had a noop change and the apply an unchanged
outcome, but only update changes took an Agent off the checked list, so
the stale old -> new tag and Update button stayed until another check.
A noop with an outcome that is not failed now clears it too.
Codex review on #400:
- The private-registry check read npm's config by hand, and each round
found another place npm reads it from: the lowercase environment, the
global npmrc, and now a globalconfig or prefix set in the user .npmrc.
Rather than chase npm's rules, the check now asks npm itself:
`npm config get registry @scope:registry` in the folder Pi runs npm in.
Any registry other than npmjs, or npm not answering, leaves the package
to Pi. The hand-written .npmrc reading is gone.
- When an apply stopped before any Agent ran, such as on a stale preview,
the result had no outcomes, and the page took every planned update off
its list, hiding the row's Update action. Only an Agent the result
reports done comes off now.
Codex review on #400:
- The Plugins page kept only one version per plugin from a check, and
only when the change had one, then hid the row's Update button when an
Agent already had that version. A source plugin whose content changed
without a version bump, or whose manifest has no version, so lost its
Update action once the check dialog closed. The page now keeps what the
check found per plugin and Agent, with or without a version, and an
applied update takes those Agents off; the version only shows what the
update brings.
- The private-registry check did not read npm's global config, so a
registry set only in $PREFIX/etc/npmrc still sent the package name to
npmjs. It now reads the file npm_config_globalconfig names, else
$PREFIX/etc/npmrc with the prefix from the environment or the npm on
PATH, and leaves the package to Pi when it can't tell where that file
is.
- Reading the package version made a package.json whose version is not a
string fail to decode as a whole, which dropped its pi manifest and the
extensions it declares. The version is decoded on its own now, so an
odd one is only skipped.
Codex review on #400:
- The update check asked the public npm registry about every unpinned Pi
package, even when the environment or an .npmrc sends the package, or
its scope, to another registry. A public package with the same name
could then hide a real update or offer an unrelated version. The check
now reads the npm registry settings for the package and its scope from
the environment, Pi's npm folder and the user .npmrc, and falls back to
checking in Pi when any of them names another registry.
- The row's Update button disappeared as soon as any Agent had the
version the check found, so with one Pi target behind and another up to
date, the one behind lost it. The row now compares each selected Agent
with that version on its own, and updates only the ones behind.
The Plugins page listed every binding a run touched, one row each, so a
single failure sat among a dozen "unchanged" rows, and the preview did
the same. Failures now come first, Agents that ended the same way share
a row, and what stayed the same folds into one Unchanged line that opens
to one row per plugin, with Pi packages apart. Logos stay only on the
rows that need a look.
An npm package in Pi recorded no version and no source, so it showed no
version and Check updates could only say to check in Pi. The installed
package.json now gives its version, on the Plugins page and in a Pi
target's Extensions tab, and check compares that version with npm's
latest. A newer version gets an Update button on the row and in the
check's result; it updates that one package with pi update <source>,
not pi update --extensions, which would also update packages the
preview never listed. update leaves a package already at npm's latest
alone, and records no version, so the dashboard keeps reading what Pi
installed. The two check messages that were English in every locale now
have keys.
Release-As: 0.24.5
The Import dialog listed everything an Agent reports as installed,
including what Skillshare itself installed there (a Pi plugin shows up
as its state path) and what was already imported. Importing either one
again changes nothing, and the path does not say which plugin it is.
Each Agent's list now skips entries whose ID a package already binds to
that Agent, counts only what is left, and says when everything there is
already managed.
A plugin Skillshare installs from a Git source and binds only to Pi
landed in the "Pi packages" list, which is meant for packages Pi
installs itself (npm:/git: identifiers with no recorded source). The
list now also requires that neither the package nor any binding has a
source, so such plugins stay under "Managed by Skillshare".
The Pi target's Extensions tab titled those same plugins by their
local state path (local:.../skillshare-<hash>/content), which does not
say which plugin it is. The server already returns the plugin name as
managedBy; use it as the card title, keeping the path in the tooltip
and details.
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.
* 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
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.
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.
* 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.
* 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.
The dashboard listed every resource type except hooks, so a source with
hooks looked as if it had none. Hooks now sit between MCP and Plugins,
matching the sidebar, in both the global and project dashboards.
The Extensions tab lists the packages Plugins syncs to Pi, but a sync
refreshed only the plugin list and config. With a two-minute stale time,
a package removed from Pi stayed listed on the tab until the cache aged out.
Turning on a file that only a "-path" rule kept off wrote "+path", so the
row ended with a rule pinning it on and a separate Remove rule button that
did nearly the same thing. When removing the row's own rule gives the state
the switch wants, the view now says so (unruled) and the switch removes the
rule. Remove rule stays only where the rule is redundant. The prediction
uses the same rule edit, evaluation and guard as the write, so the preview
and the result agree.
Extension cells had a 300px minimum, so a wide page packed six to a row.
At that width the rule and status line wrapped over several lines in
Chinese, splitting words such as 待處理 across lines. A 440px minimum
keeps the line on one row and still fits several cells per row.
* feat(ui): accept a pasted npx skills add command in the install dialog
Skill pages commonly publish an install line such as
`npx skills@latest add owner/repo --skill=name`. Pasting it into the
source field used to send the whole command to discovery, which failed.
The field now reduces such a command to its source, and discovery of that
source preselects only the skills named with --skill. Flags that choose
install locations (-g, -a, -y, --all, --copy) are dropped because targets
decide those in skillshare.
* fix(ui): read owner/repo@skill and match skill names case-insensitively
Two gaps against how upstream npx skills reads the same command:
- `npx skills add owner/repo@skill` (the form find-skills emits) kept
`repo@skill` as the repository name, so discovery tried to clone a repo
that does not exist. The shorthand is now split into source and skill.
- A --skill value differing from the discovered name only by letter case
matched nothing, and the dialog fell back to selecting every uninstalled
skill. Names are now compared case-insensitively, as upstream does.
* refactor(ui): move pasted-command preselection rules into one function
What a pasted --skill means for the default selection was split between
the parser and InstallDialog: the source check and the fallback when
nothing matched lived in the component, and both sides relied on an
empty skills list meaning "no pick". requestedSkills now owns all of it
and returns null for "keep the default", so those branches are covered
by unit tests instead of only by a manual check in the browser.
* fix(ui): keep backslash-escaped spaces in a pasted skills add command
`npx skills add /tmp/my\ skill` works in a shell, but the tokenizer split
it into `/tmp/my\` and `skill`, so discovery got a path that does not
exist. Words are now read shell-style: quotes group, and a backslash
escapes whitespace, a quote or a backslash. Other backslashes stay as
written so a pasted Windows path such as C:\Users\me keeps its separators.
* fix(ui): skip option values and keep quoted Windows paths in pasted commands
Two more ways a valid npx skills add command reached discovery with the
wrong source:
- A --metadata value or --subagent names placed before the repository
were read as the source. Option values now follow upstream's
parseAddOptions: --metadata takes one value and --subagent, like
--agent, takes bare words up to the next flag.
- "C:\Users\me\my skill\" lost its trailing backslash because `\"` inside
quotes was read as an escaped quote. Backslash escapes now apply only
outside quotes; pasted skills commands do not quote quotes.
* fix(ui): keep @ in local paths of a pasted skills add command
`npx skills add ./repo@draft` was split as owner/repo@skill shorthand, so
discovery read ./repo and looked for a skill named draft. Upstream checks
for a local path before the shorthand; paths starting with . or ~ now
keep their @ (absolute and drive paths already did).
* fix(ui): preselect nothing when a pasted --skill is not found
When a pasted command named a skill that discovery did not list, the
dialog fell back to selecting every uninstalled skill, so one-skill
command could turn into a batch install. This is reachable because
discovery names a skill after its directory while upstream matches the
SKILL.md name. An explicit request with no match now preselects nothing
and leaves the choice to the list; upstream fails in the same case.
* fix(mcp): explain Pi project overrides in import and sync conflicts
Since Pi 1.0.1, /mcp in Pi writes a .pi/mcp.json entry with only
enabled, exposure or toolExposure to override the global server of that
name. Skillshare treated it as a broken server: import reported
"requires exactly one of command or url", and a project server with the
same name hit a conflict that told the user to import it, which import
always refused, so the user was left without a way forward in the CLI.
Import now names the entry as a Pi project override with nothing to
import. Sync reports the conflict as an override to replace or remove
with /mcp in Pi, and the dashboard offers only Replace for it. Sync
behavior is unchanged; detection matches Pi's own isOverride (no
command, url or type).
* fix(mcp): limit Pi override detection to project imports
Codex review on #371: importing Pi's global ~/.pi/agent/mcp.json, or a
pasted snippet, also reported a connection-less entry such as
{"enabled": false} as a project override and pointed to /mcp in a
project. Pi gives that shape override meaning only in a project's
.pi/mcp.json; elsewhere it is an invalid server. importNative now takes
the scope, so global and pasted imports keep the usual "requires exactly
one of command or url" problem.
* fix(mcp): classify a synced entry turned into a Pi override
Codex review on #371: when an entry this config synced to .pi/mcp.json
was later changed into a connection-less Pi override, the ledger still
marked it managed, so the generic "Agent configuration changed; import
it" conflict won and the dashboard offered an Import that project import
now refuses. The override case now comes first and covers a managed
entry whose content changed as well as an unmanaged one, so both offer
only Replace.
* fix(mcp): classify Pi overrides before every import-offering conflict
Codex review on #371: the prune conflict ("Pi setting changed since
sync; import it") still came before the override case, so a synced
server whose cleared Pi field Pi had replaced with an override again
offered an Import that project import refuses. Rather than chase each
earlier case, the override case now opens the switch. An entry owned by
another live config keeps its own message, since only that config can
release it.
* fix(mcp): treat a removed owner's entry like any other Pi override
Codex review on #371: an entry whose ledger owner was a removed config,
later turned into a connection-less Pi override, still got the orphaned
conflict, which offers an Import that project import refuses. Skillshare
never writes a connection-less Pi entry, so the override case now covers
every such entry except one a live config owns, which only that config
can release. It still skips an entry recorded at its current hash, which
is what Replace leaves, so Replace settles the conflict; a test now
covers that.
* feat(pi): edit extensions on any Pi at or above the verified minimum
Pi 1.0.1 was released and every user who updated found the Extensions
tab read-only, because the gate matched an exact list of versions. The
package contract has not changed between patch releases, so the gate now
accepts any plain X.Y.Z at or above PiMinVersion (0.99.2), the oldest
version with executed evidence. Older, prerelease or unparsable versions
stay read-only.
The version matrix now also records Pi 1.0.1, which passes every check.
The evidence test requires PiMinVersion to be recorded and every recorded
version to pass, instead of matching an exact list.
The read-only reason is renamed to unsupportedVersion and the API returns
minVersion, so the dashboard says which version is needed.
The Pi MCP project switch keeps writing the global command or url: from
1.0.1 Pi accepts a switch-only entry, but it is skipped by older Pi and
warns at every start where the global config lacks the server. Its
rationale in comments and docs is updated to say so.
* fix(docs): update Pi extensions design records for the minimum gate
Codex review on #367: the design records still described the exact
version list (PiVerifiedVersions, unverifiedVersion, "exact versions
only"), so a contributor relying on them would implement or validate the
old contract. implementation-report.md now states the current gate and
evidence, and phase-0.md gains a dated minimum-version update that the
older paragraphs point to, keeping the history intact.
* chore(design): export dashboard tokens for design tools
Mockup tools read a design system's tokens.json rather than our CSS, so
designs drifted from the dashboard's Clean theme. The script derives the
tokens from components.css, and CI runs its test so a new color
variable without a usage note fails instead of silently going missing.
* feat(plugin): add npm packages from pi.dev through Pi
Pi packages on pi.dev are npm packages, which Plugins could not add:
it only took local or Git sources, so users had to install them with Pi
and import them. `plugin add npm:<package>` now hands them to
`pi install` for Pi targets and records the binding like an import.
Skillshare can't fetch or review an npm package, and Pi runs its install
scripts, so the preview says so, discover refuses npm sources, and only
targets that run pi itself take them. Pi keeps one entry per package
name, so another version replaces it in place and keeps its extension
filters; Skillshare records the new entry so a reinstall restores them,
and refuses a package another Skillshare package already manages, since
removing one would remove both. Pinned versions are skipped on update
because pi update keeps them.
The dashboard accepts npm sources, a pasted `pi install` command or a
pi.dev address, lists only Pi targets, and the Pi Extensions tab links
to adding a package with that target selected. Pi packages show Pi's
mark in the plugin list.
A blocked change now keeps its own reason when the Agent's CLI is also
missing, and the message key always matches the message the CLI prints.
* fix(plugin): keep npm package names and accept pi by path
The default name of an npm package went through the file-path rule, which
cut its last dot segment as an extension: npm:foo.bar was recorded as foo,
and adding npm:foo.bar@1.2.3 later derived foo.bar and was refused as
another package managing the same Pi entry. npm names are now taken from
the package spec.
A Pi account whose CLI is an absolute path to pi was treated as running
another executable, so it could not take npm packages. It now uses the
same path- and platform-aware check as the Pi Extensions tab.
* docs(wiki): add a pull-requests topic for Codex review rounds
Handling Codex's review was only known from practice: confirm each
finding, fix it with a failing test first, reply in its thread, ask for
another review, and follow up until it answers. Writing it down keeps
agents from resolving threads, amending pushed commits, or stopping at
the 👀 that only means the review is still running.
* feat(ui): give the Extras AGENTS.md and Memory tabs one layout
The two tabs shared a page but looked like different products: the header
shifted between them, notes sat in a joined box with an icon toolbar, and
agents showed as an icon strip in a side card. Switching tabs felt jarring.
Memory now follows the AGENTS.md layout: a sticky list column with search,
the note's name with Edit and a More actions menu, the same preview box,
and Use with agents as one row per tool under the note. Long notes open
collapsed like shared files do. The AGENTS.md list gains a search box and
the same sticky column. The Memory tab label stays English in every locale,
like AGENTS.md. Docs and screenshots follow the new layout.
* chore(docs): add a script that serves the Memory screenshot homes
The Memory how-to screenshots came from demo homes that were never
recorded, so reshooting them meant rebuilding the data by hand. The script
rebuilds the fresh and the populated home inside the devcontainer, serves
each behind the Vite dev server, and hands the port back to air afterwards.
* fix(plugin): refuse npm sources Pi can't resolve
validNpmSource accepted specs such as npm:foo/bar, npm:foo@ and names
containing "..", which Pi's own parser rejects. They passed preview, and
Apply recorded a pending binding before pi install failed, leaving an
entry every later sync retried. Validate with the same grammar the Pi
settings reader uses, which also covers a scope without a package name.
* fix(ui): show the default name when adding an npm package to Pi
The name field for an npm source was blank, so it looked like a name was
missing. Leaving it empty records the package name without its version or
scope, as the git flow already shows; the field now shows that name as its
placeholder.
The empty state told users to add packages in Plugins, but Plugins only
accepts local or Git sources, so packages from pi.dev (npm:) dead-ended
there. The tab already lists every package in the target's Pi settings,
including ones installed with Pi itself, so say that, and point to
importing in Plugins for Skillshare management. The plugin docs now say
the same in every locale.
* fix(ui): keep memory connection states current and compact
Disconnecting a target on the AGENTS.md tab did not refresh the memory
tab, so for up to two minutes the target still showed as configured and
could not be selected in the connect dialog. The guidance query now
never serves a cached copy and refetches when the dialog opens.
The side panel listed every target with its file path, which grew taller
than the notes beside it. It now shows the same logo stack as Hooks and
only lists targets that need a fix. The connect dialog uses the bordered
target list from the AGENTS.md connect confirmation, and the review step
gives before/after the same fixed height.
* fix(ui): show why a memory target needs attention without hover
The reason a target is broken (modified, malformed, not synced, ...)
was only in a title tooltip, which keyboard and touch users cannot
open, while the connect dialog disabled the row with a generic
"Needs attention". Show the specific reason as the row's status text in
both the side panel and the dialog.
* feat(pi): manage individual extensions per target
Keep package lifecycle in Plugins while letting global, account, and project Pi targets configure individual extensions with reviewed, lossless changes. Project overrides save only project settings and never grant trust.
Bind edits to native version contracts, settings snapshots, source ownership, and discovery; preserve unrelated resources and enforce renewable native locks, stale rejection, and backups. Verify Pi 0.99.2 and 1.0.0 without running extension factories.
Simplify configured-state UI and distinguish Skillshare-managed packages from native tool registrations, with localized guidance and regression coverage. Closes#342.
* fix(pi): address project extensions review findings
Keep exact project delta rules visible when their extension files are missing so users can remove stale rules without changing global settings or trust.
Show the project Extensions tab only when its generated Pi target resolves. Cover missing and agents-only projects, absent targets, and another project target with regression tests.
* fix(pi): recognize official Windows account launchers
Accept pi.cmd and pi.exe account launcher names on Windows, including case-insensitive and native Windows paths, before probing the existing exact-version gate. Preserve POSIX behavior and never probe unrecognized forks or stacked launcher suffixes.
Add platform-name and account-gate regressions covering verified, unsupported, and missing CLI versions. Focused race tests, make check, and Windows amd64/arm64 test cross-compilation pass; real Windows runtime remains unverified because the UTM guest is stopped.
* fix(pi): align rule removal and backup descriptions
Offer Remove rule only for owned exact +/- rules, not project delta globs that the apply path cannot remove. Keep supported glob rows switchable and cover delta and deltaOnly forms with RED/GREEN regressions.
Describe retained artifacts as extension-list and file-hash records rather than complete settings backups in English, all four website translations, and the implementation report.
* fix(pi): discard records for aborted extension applies
Require a validated preview and owned native lock before recording an extension change. Discard only the newly created record if final revalidation, lock ownership, or the atomic settings write fails; retain successful history and propagate cleanup errors with the original failure.
Keep discovery revalidation after record I/O so cleanup does not weaken the write-boundary guard. Cover global and new/existing project settings with nine RED/GREEN regressions, including injected commit failures. Align English and translated docs with the retained-record lifecycle.
* fix(pi): retain anonymous global packages in projects
Keep ordered anonymous registrations separate from the proven-identity map so unsupported query-bearing sources remain visible as redacted read-only packages, rather than being dropped or associated with a project override.
Preserve first-global-entry precedence for known identities. Add RED/GREEN coverage for string and object registrations, query/userinfo redaction, project entries, zero-write refusal, ordering, and continued editing of known packages.
* fix(pi): deduplicate only proven project identities
Exclude unresolved identities from project duplicate tracking. Preserve each anonymous registration as sourceUnknown instead of pretending unrelated query-bearing URLs are the same package.
Cover mixed string/object anonymous project sources, redaction and zero-write refusals, retained anonymous globals, and last-project-entry precedence for known packages. Verify known project entries remain editable.
* fix(pi): guard unresolved package precedence
An unresolved earlier global registration may own a later known package, and an unresolved later project registration may supersede an earlier known entry. Keep those potentially shadowed entries and inherited deltas Unknown/read-only instead of offering edits to ignored registrations. Do not infer identities by dropping credentials or queries.
Cover both ordering directions for global, inherited, project-owned, and delta views with RED/GREEN tests. Execute native query identity and dedupe evidence on Pi 0.99.2 and 1.0.0 through core and CLI-bundle contracts, now 28 scenarios and 87 assertions each. Align docs and evidence while retaining independent anonymous entries.
* fix(pi): propagate unreadable source ambiguity
Treat badSource entries as unresolved instead of letting an unreadable source expose editable later global registrations. Preserve the same uncertainty in inherited globals and before unreadable later project entries.
Add twelve global/inherited/project regressions for null, empty, whitespace and invalid UTF-8 sources. Native core and CLI-bundle evidence confirms invalid UTF-8 can decode to and own the same identity as a later valid source on both supported Pi versions; the executed contracts now pass 29 scenarios and 90 assertions.
* feat(pi): preserve filtered imports and reclaim stale locks
Adopt native object registrations without changing their configured resources. Keep lossless entries in scoped private state, retain current rules across lifecycle operations, restore filters before native installation, and preserve pending retries after failures.
Reclaim only unchanged empty directories after the native stale threshold, retaining renewed, replaced, nonempty and non-directory locks. Verify exact supported Pi contracts and keep unsupported cases read-only.
* docs(pi): record filtered import verification after branch sync
Document the current merged UI test count and repeated checks while retaining the native and visual verification limitations.
* docs(pi): clarify stale acquisition exception
Keep the lock safety summary consistent with the approved acquisition policy while preserving strict ownership for renewal and release.
* fix(pi): keep legacy npm fallback installations unknown
A missing user-scoped managed npm root cannot prove a package is absent because native Pi may use a legacy global npm or pnpm root. Keep it read-only without probing host-global state, while retaining missing-state behavior for project npm packages.
* fix(pi): preserve project precedence and batch restore ownership
Retain empty winning overrides when deleting them could expose older resource filters. Advance filtered restore batches only to exact writes made by the same Apply, while rejecting external changes and retaining failed native retries. Match Pi strict-false autoload semantics instead of treating null as a delta.
* feat(push): add --pull for two-way sync in one command
Users editing skills on several machines have to remember push on one and pull on the other, and a push from a machine that is behind fails until they pull first. push --pull commits local changes, merges the remote with the same merge semantics pull uses, pushes, and syncs the git root scope.
A conflict stops before anything is pushed and keeps the local commit; a target sync failure after a successful push is reported separately so the user knows the remote is already updated. It never rebases or force-pushes. commit rejects --pull instead of silently ignoring it, since both commands share the argument parser.
* docs(push): document push --pull across guides and translations
Cover the new flag on the push reference, the cross-machine sync guide, the quick reference, the daily workflow and the cross-machine recipe, in English and the ja, ko, zh-Hans and zh-Hant translations, plus the built-in skill's sync reference.
* fix(push): print the scope's sync command when --pull sync fails
A bare 'skillshare sync' retry hint defaults to skills and may pick project mode, so it does not redo an agents, extras, or root sync. Derive both the sync and the hint from one per-scope list.
* fix(pull): sync extras for the root git scope
The root scope versions skills, agents and extras, but pull and push --pull only synced skills and agents, so merged extras changes never reached their targets.
* fix(server): sync extras after a root-scope pull
The root scope versions extras too, but the dashboard pull only synced skills and agents, so merged extras never reached their targets. Matches the CLI fix.
* feat(ui): add a Sync both ways action to Git Sync
Mirrors skillshare push --pull: commit local changes, merge the remote and sync targets, then push, in one click. A pull conflict stops at the existing review before anything is pushed.
* feat(ui): confirm Sync both ways and list what it will do
Sync both ways commits, merges and pushes in one click, so ask first and show the concrete outcome (files to commit, remote commits to merge, scope, push target, conflict behavior) before changing anything.
* fix(ui): make Sync both ways match push --pull
It skipped target sync when the pull was already up to date, stopped on an empty remote instead of pushing, and the pull dropped extras warnings. Add alwaysSync and a remote_empty code to /api/pull and surface all extras warnings.
* feat(extras): add shared Markdown memory management
Store user-managed notes in extras/memory for global and project scopes.
Add CLI operations, a nested dashboard browser, versioned edits, and
backup-backed deletion and recovery.
Connect selected agents with reviewed, marked reading guidance while
preserving existing instruction files and routes. Add explicit INDEX
linking, conflict draft comparison, and copy-content previews.
Document the workflow in five website locales with English screenshots
and translate dashboard copy across all eleven locales. Native automatic
memory remains separate from this shared file overlay.
Validation: make check; 22 UI tests; TypeScript and ESLint; production UI
build; six isolated CLI E2E steps; five-locale website build; explicit
Claude-write/fresh-Codex-read smoke test.
* feat(memory): support dashboard note moves and redesign browser
Add version-checked rename and folder moves without replacing existing notes.
Back up the old path and preserve content and permissions while refreshing
selection, search, index warnings, and backup links.
Integrate the two-pane Memory browser and compact agent controls. Refresh all
English screenshots and document move/link/history behavior in five locales.
Validation: make check, scoped UI tests, TypeScript, ESLint, UI production build,
five-locale website build, locale parity, and visible Chrome workflow checks.
* fix(memory): recheck reviewed files before committing changes
Preserve external edits detected after note backup or draft preparation, and create new notes exclusively. Revalidate each guidance file before writing, report stale partial failures, and correct the built-in move/rename documentation.
* fix(memory): repair initialization and preserve note recovery scope
Detect missing starter files before dashboard note creation and refresh the index after initialization. Honor requested backup paths, include external project memory sources in recovery scope, and log initialization failures after partial mutations.
* fix(memory): protect guidance creates and match Windows history paths
Create new reviewed instruction files exclusively to preserve competing writes. Match Windows history links with native backup paths while keeping POSIX names and backup API paths intact.
* fix(memory): require configured extra for external backup access
Keep project backup scope inside the repository unless a valid memory folder extra enables its external source. Cover listing, version preview and restore denial without changing configured-source recovery.
* fix(memory): lock backup scope validation through restore
Validate project memory backup access under the restore write lock so concurrent extra deletion cannot revoke access between validation and writing. Hold read locks across scoped backup reads as well.
* feat(check): detect changes at local install sources
Skills installed from a local path (for example a skill shipped inside an
app bundle) could already be refreshed with `update`, but `check` always
reported them as "local source", so users had no signal that the source
had changed after an app update.
`check` now re-hashes the files at the recorded source path and compares
them with the hashes stored at install/update time. It reports
update_available on a difference, up_to_date on a match, and an error
naming the path when the source is gone. The path is resolved the same
way `update` resolves it before re-copying, so a successful update always
brings the status back to up_to_date. The CLI and both Web API check
handlers share the comparison in internal/check.
Refs #206
* fix(check): avoid false local-source updates and show check errors
Review follow-ups for local-source change detection:
- The dashboard installs the root of a directory that also holds child
skills as its SKILL.md alone, so hashing the whole source reported
update_available right after a clean install. Compare only the files
such an install copies, recognized by recorded hashes that contain none
of the child skills present in the source.
- A relative source path resolves against the cwd of the install, which
is not recorded, so checking from another directory reported a missing
source. Relative sources are no longer compared.
- The dashboard dropped the new check `message`, so a missing source only
showed a generic "Check failed". Carry it into the status tooltip.
* revert: restore video files accidentally removed in 1fb13b75
The review-fix commit picked up unrelated staged deletions under video/. They belong to separate work and are not part of this change.
* fix(ui): show where pull conflict versions differ
The pull conflict dialog showed both versions in short 208px panes with no
marking, so users had to scroll and compare long files by eye to find what
actually conflicted.
Panes now use 55vh, lines that only one side has are tinted, each side
scrolls to its first difference, and the header counts differing lines.
* chore(docs): move ai-context router config into wiki/
The router config describes wiki topics, so it belongs next to the pages it
maps; docs/ reads as public documentation. The script is synced with the
upstream router, which also normalizes backslash paths and forces UTF-8
output for Windows consoles.
The router runs on the host rather than the devcontainer, so the kernel now
says to use py or python on Windows when python3 is unavailable.
* fix(ui): give pull conflict panes room and tidy the dialog edges
Short conflicting files still rendered as cramped strips, so panes now keep
a 40vh minimum. A long body scrolled straight under the title, so the header
gets a separator like the footer. The conflict banner's text sat above its
button because notes align to the top for multi-line errors; it is centered
when the message is the fixed conflict text.
* fix(ui): bound the pull conflict line diff
diffLines keeps an n×m table, so two 16 KiB previews that differ on every
line could allocate hundreds of megabytes and freeze the dialog. Matching
leading and trailing lines are now skipped before diffing, and versions whose
differing middle would still need over a million cells are shown unmarked.
Removing a Skillshare marketplace from Claude passed --scope user (or
project). Claude refuses a scoped removal when the marketplace is only
recorded in known_marketplaces.json, which happens once synced settings
drop its declaration, so cleanup failed on every sync. Remove it without
a scope: the name is unique to the binding and its root is checked
first, so every scope's copy is Skillshare's. A name declared at
several paths is reported as a conflict and nothing is removed.
Claude also reads a skill folder that has a plugin manifest as
<name>@skills-dir and loads only one plugin per name, so installing a
Claude plugin named like such a skill made Claude report the skill as
not loaded with no warning beforehand. The install preview now says
which copy Claude will load.
Validation: make check, the UI vitest suite and tsc in the devcontainer;
the cleanup and clash tests fail without the change. Claude 2.1.287
rejected the scoped removal and accepted the unscoped one against a copy
of an affected config.
Release-As: 0.23.4
Managed Claude/Codex marketplaces were named skillshare-<hash>, which
says nothing in native marketplace lists, and they stayed registered
after the plugin was excluded or removed. Cleanup ran only after a
native uninstall, so a plugin already removed in the Agent, a failed
first install, or a failed cleanup left the marketplace behind for good.
Name new marketplaces skillshare-<plugin>-<hash>, and remove the one
Skillshare registered whenever its plugin is excluded or removed, also
when the plugin is already gone. Cleanup checks that the marketplace is
registered from Skillshare's own state directory, re-lists afterwards,
and stays pending for the next sync on failure or while the marketplace
list cannot be read. An update registers a missing managed marketplace
again.
An imported plugin reinstalls from its native marketplace. When that
marketplace is gone (for example when synced settings dropped it), sync
failed with a generic "command failed". Skip that target with the reason
instead, so other Agents still sync. Skillshare does not move an import
to its recorded source on its own: that would install a distribution
and version nobody reviewed for that Agent.
Failed outcomes now carry their translation key, and the dashboard
shows each distinct failure once instead of the joined English text.
Validation: make check and the full UI vitest suite in the devcontainer,
tsc and eslint; the new Go tests fail without the change. Claude and
Codex marketplace removal was checked against the real CLIs in
isolated config directories.
Release-As: 0.23.3
Pi 1.0 adds oauth.authServerMetadataUrl and trusts that document instead
of discovering the authorization server, so it requires https except on
loopback. Skillshare passed the field through unchecked, which left a
wrong URL to fail only at sign-in inside Pi. Check it on save in both
the CLI and the dashboard, like oauth.callbackUrl.
Pi 1.0 also keeps OAuth sign-ins per server name and URL; document that
renaming a server or changing its url needs a new sign-in in Pi.
Validation: make check in the devcontainer, mcpView vitest, tsc and
eslint; the new Go and UI tests fail without the check.
Git 2.54 added named config hooks, but keeping their registrations and
helper paths consistent across machines still required manual config
edits. Bring them into the same preview, sync, and recovery workflow as
Agent hooks.
- Global and project scope, with linked worktrees sharing the common dir
- Portable helper files, collision detection, and ownership tracking of
generated files and include.path entries
- Backups and restore preserve unrelated settings and conditional includes
- Management never executes hooks; Git below 2.54 is reported as inactive
while outputs are still generated
- CLI/API inventory, raw YAML editing in the dashboard, localized docs
The share command had no scope flag, so its target depended on where the
recipient pasted it: inside any directory with a .skillshare/config.yaml
it added the plugins to that project instead of the global configuration.
Every add in the copied command now passes -g.
Validation: vitest for plugins API and PluginsPage (20 tests),
tsc --noEmit, eslint, and ai-context check.
Passing plugins to a teammate meant looking up each source, plugin name
and ref and typing a `skillshare plugin add` per plugin.
The Plugins page now has Share, in the header and in each row's menu. It
lists the plugins added from an HTTPS source, and copies one line that
adds the ticked ones in order. Each add passes --no-tui by default, so
the whole list lands in Skillshare without a picker per plugin; the
recipient ticks Agents on the Plugins page afterwards. An option keeps
the per-plugin Agent picker instead. The adds are joined with && on one
line because, pasted on separate lines, the first picker would read the
rest as keystrokes. Plugins from a local directory are left out, since
the path only exists on the sharer's machine.
Validation: vitest for plugins API, PluginsPage and i18n (29 tests),
tsc --noEmit, eslint, and ai-context check.
Target folder backups were capped at a fixed 10 snapshots and 500 MB, and
the dashboard could only remove them one at a time. Users with larger
targets or little disk space had no way to tune either.
The global config now takes backup.max_count and backup.max_size_mb
(0 = no limit); sync, the dashboard's sync and backup --cleanup apply them,
while the 30-day limit stays fixed and project snapshots keep the defaults.
The Target folders tab shows the limits in its toolbar, opens a panel to
change them, and adds Delete all behind a confirmation. File, MCP and Hooks
backups are not touched.
Doctor only diagnosed skills and agents. MCP, hooks and plugins had no
check at all, and extras only confirmed that the source and target parent
directories existed. Their misconfigurations stayed hidden from both the
CLI and the dashboard's Doctor page.
Doctor now reuses each domain's own read-only logic in both modes:
- MCP: the static part of mcp check (env, command, client rules, sync),
without DNS lookups or starting servers
- Hooks: the hooks sync preview (failures, pending changes, conflicts)
- Plugins: the plugin sync preview without fetching sources, run only
when a package exists
- Extras: config validation, broken links in targets, and drift as diff
reports it (flatten/extension targets are not compared)
The dashboard labels for these checks, plus the shared_target_paths,
cross_target_discovery and tracked_repos checks that had none, are
translated in every locale.
Turning a server off in Pi took hand-written enabled: false in the Other Pi settings JSON. A checkbox above Tool exposure now writes and removes it, kept in step with the JSON. The Pi docs link points at Pi 0.99.2.
The editor kept its own list of pi-mcp-adapter fields and refused auth whatever its shape, so Pi's own auth object could not be saved from the dashboard after the backend accepted it. Refuse only the adapter's string, and check auth.provider and oauth.clientName like the backend.