The shared AGENTS.md workflow is dashboard-only, so users had no written
reference for how shared files attach, what restore puts back, or where
drift backups go. Adds a how-to page in every locale, documents
single-file extras and the target `instructions` key, and brings the
translated extras collect section up to date with English.
When the binary lived in a root-owned directory, upgrade re-ran the whole
command under sudo. The built-in skill download, UI asset cache, and oplog
then landed in the user's home as root-owned files, and a later git pull
of the skills source failed with "unable to unlink old
'skillshare/SKILL.md': Permission denied".
The sudo child now only receives an internal --replace-binary=<version>
flag that downloads and swaps the binary. The parent waits for it and
does everything else as the invoking user. The needs-password hint shown
by the CLI and dashboard drops its sudo prefix, since a fully root
upgrade reproduces the same breakage.
The 0.21.9 entry was written before the toolbar was compacted and before
disabled tree items got their own icon, and its folder bullet still
described Group as a separate dropdown.
Record the tree view rework, tracked-repo targets and folder grouping from #295, plus the dot-folder sync fix (#294), the Plugins page fix (#296) and the dashboard server crash fix.
Skills installed with --into land in folders, but the list and cards
views could only filter and group by source, so there was no way to
look at one folder at a time or see the folders side by side.
Add a Folder filter next to Targets and a Folder option to Group. A
skill's folder is its parent path, a tracked repo counts as one folder,
and skills at the source root group under "Root". The filter is hidden
when everything lives in one folder. Agents get the same controls.
Turning a whole folder or tracked repo off meant ticking every skill
in it, and the tree rows mixed table columns with indentation.
The tree view is now an explorer tree beside a detail pane. Click a
folder, repo or skill to select it; Cmd/Ctrl-click adds, Shift-click
selects a range. The pane turns the whole selection on or off with one
switch, sets its targets (tracked repos included), and lists each skill
with its own switch. Counts and disabled markers show on hover, and the
divider between the two sides can be dragged.
Enable/disable toasts now replace each other through a new toast `key`,
so quick on/off clicks no longer leave an outdated "Enabled" on screen.
Refs #295
Setting targets on a skill inside a tracked repo used to be refused,
because writing its SKILL.md leaves the clone dirty and `update` then
skips the repo (or `--force` throws the setting away).
Store those targets in the source's .metadata.json instead, keyed by
the skill's path, and apply them at discovery over the frontmatter.
The clone stays clean, `update` keeps working, and the setting survives
it. Uninstalling a repo or skill drops its entries.
Overrides are saved in the same lock section that writes them: every
API request reloads the store from disk, so saving after unlocking
could lose them, and saving outside the lock raced with other writers.
Refs #295
The pages still told users to inspect conflicts with git status and to
fix diverged tracked repos with git pull --rebase, but pull now merges
diverged history, resolves .metadata.json conflicts on its own, and
undoes the merge on any other conflict, so those steps no longer match
what happens. Also documents the Git Sync page fetch, the Pull count,
and the push_rejected API error in every translated locale.
The Targets row and the -p mode notes did not mention that a target
now lists and switches its MCP servers, nor that its Sync writes every
target's MCP files.
The Pi adapter settings moved from a hover icon to a line on the server
row, and Import from an Agent on a project's conflict now reads that
project's file, so the dashboard descriptions no longer matched.
Refs #289
Refs #290
A target declared with `agent` and `config_dir` is another config directory of a
built-in Agent, such as a second Claude account. Its skills and agents paths are
derived from the Agent's defaults at load time, so the config only records the
directory. The same target name works for MCP (written in the Agent's format into
the account's own file), for plugins (the Agent CLI runs with CLAUDE_CONFIG_DIR,
CODEX_HOME or PI_CODING_AGENT_DIR) and for `mcp import --from`. Removing such a
target warns when MCP config still names it instead of failing later at sync.
The dashboard gains an "another account" mode in the add-target dialog and lists
accounts next to the Agents on the MCP and plugin pages.
Refs #289
The MCP row on the ui page kept English button names in the translated pages,
next to labels that were already translated, and the English page itself said
Import where the button reads Import from a target. Three locales also lacked
the paragraph on upgrading without a terminal to ask for a password on.
The dashboard pages still described the project row without the Agent logos
and the Match the project action, the ui page did not mention where piOptions
is edited, and upgrade did not say the download now reports its progress.
Refs #289
OpenCode also loads opencode.json and opencode.jsonc from a project's
.opencode directory. Skillshare looked only at the project root, so a file
kept there was ignored and sync created a second one beside it. It is
resolved the way Kilo Code's .kilo already is: an existing file is reused
wherever it is, a new one goes to the root, and more than one is refused.
Refs #289
Also corrects a claim that every conflict offers an import action. One held
by another Skillshare config that still exists offers none, because only
that config can release the entry.
Refs #288
Adding a plugin forced at least one target, so keeping a plugin in
Skillshare for later meant installing it somewhere and then deselecting
every Agent by hand.
A package now records its source, so it stays managed with no Agent
bound. Agents are bound later from the same source, installing it as it
is then. Removing the last Agent keeps such a plugin; removing the
plugin itself drops it. In the terminal picker, confirming with nothing
selected records it, while Esc still cancels.
The plugin list also shows the installed version as a tag, and an
update check shows old -> new for plugins whose source has moved on.
The pages still said a disabled entry cannot target Claude Code, and that the
field is project mode only. Both are lifted: the entry is valid under an
mcp.projects root as well, and for Claude Code the switch goes to
~/.claude.json, where Claude Code keeps its per-project off list, leaving the
server definitions in that file alone. Only the global mcp.servers, where no
project is in scope, still refuses it.
The dashboard sentence was stale from an earlier change: the switch is its own
"Turn off a global server" button beside "Add server", shown in project mode
and on a project's MCP tab, not an option inside the add form.
All four locales follow, naming the buttons as the dashboard shows them there.
Refs #286
Claude Code keeps its per-project off list in ~/.claude.json, the same file
its user-scope servers live in. The plan keyed desired entries by file path
alone, so one file could carry only one native target, and mcp.projects had
to refuse a disabled entry for Claude Code rather than write that list.
Key the plan by file and target instead. Apply already rereads the file per
plan, and sectionDigest hashes only the target's own section, so two plans
on ~/.claude.json fold in order without further machinery.
A change now carries the mcp.projects root it belongs to. Its path no longer
says, because a project's off switch is written outside that project folder,
and the dashboard needs the root to keep the switch out of the global server
list and to show a pending badge on the project it came from.
Codex stays refused. It merges the project file field by field, so a switch
for a server its global config lacks leaves an entry with no transport and
stops Codex loading its config at all.
Alongside this, the dashboard gets a named "Turn off a global server" action,
so adding a switch and adding a server are two choices up front rather than
one form that asks afterwards. Two older glitches go with it: a project's
target toggles sprang back while the list was still empty, and the expanded
config editor stayed open when a tab arrived from the URL.
Refs #286
Teams need to know that skills.lock.json is meant to be committed, which
commands move a pin, and how it relates to the config.yaml manifest.
Covers project-skills, install, update, uninstall, declarative-manifest
and project-setup, in English and the four translated locales.
The analyze numbers were drifting from what tools really see. Symlink-mode
targets expose the whole source folder, so .skillignore'd skills still load
but were left out; merge/copy targets often hold skills the user dropped in
by hand that skillshare never counted; and chars/4 undercounted CJK text by
roughly four times.
Route the CLI, TUI, web handler and sync summary through one
sync.TargetSkills so the three copies of the filter logic cannot disagree
again. Disabled skills stay in the discovery with Disabled=true and are
priced for symlink targets; unmanaged folders in a target are reported as
Local. Token estimates now charge one token per wide rune.
The dashboard keeps the chosen target in the URL so target and project
pages can deep-link into the analysis, lists project targets after own
targets with their tool icon, and tags local/disabled rows. Select gives
single-select icons a key to silence a React warning.
Keeps the sync reference in every locale in step with the English page,
which now explains why project sync removes leftovers after a target's
default path moves.
Refs #135
Both tools now document ~/.agents/skills and <project>/.agents/skills as
their skills locations and keep the old directories only for backward
compatibility. Writing to the old path next to `universal` makes them read
every skill from two places.
Global configs pin absolute paths, so they are unaffected and keep their
overlap warning. Project configs store target names only, so an existing
project follows the new default on its next sync while the links it created
in .goose/skills or .openhands/skills would stay behind and show up as
duplicates. Project sync now removes those leftovers from also_scans
directories that no configured target writes to.
That directory belongs to another tool, so the cleanup runs the prune with
ManagedOnly: only symlinks into the source and manifest-tracked folders are
removed. The flat-name heuristic would otherwise delete hand-made folders
such as `_drafts`. Targets with an explicit path are skipped, and --dry-run
only previews.
Refs #135
The Antigravity CLI (agy) reads ~/.gemini/antigravity-cli/skills and
never the app's ~/.gemini/config/skills, so treating it as an alias of
antigravity synced skills to a directory it does not read. Give it its
own targets.yaml entry with the correct path.
A path-less `antigravity-cli:` config entry also failed validation,
because DefaultTargets() is not alias-aware; as a real target it now
resolves to the default path.
- Fallback fetch pulled only the default branch because a depth-1 clone
is single-branch; fetch all heads and tags so an abbreviated SHA off
the default branch resolves.
- Move the --track guard from CLI flag parsing into InstallTrackedRepo
so the Web UI is covered too, and reject tags as well as SHAs: both
leave HEAD detached with nothing for `git pull` to follow.
- An all-hex branch or tag name (e.g. 20240915) was treated as a SHA in
check and never queried; look the ref up first and fall back to the
literal SHA only when the remote has no such ref. Full 40-char SHAs
still skip the network.
- Rename the git package's 7-char shortHash to abbrevHash to avoid
clashing with install's 12-char helper.
Refs #281
Codex documents ~/.agents/skills as its user-level skills path and marks
~/.codex/skills as deprecated, while still reading both. It does not merge
skills that share a name, so the default init result (codex + universal)
showed every skill twice in Codex.
The codex target now defaults to the shared directory, keeps the old path
in also_scans, and is detected through ~/.codex. A fresh init therefore sets
up only `universal` for Codex and writes each skill once. Existing configs
keep their pinned path and still get the doctor overlap warning that
suggests removing the codex target.
Refs #135
Global skills already reach every project, so the docs lead with when
`projects` is not needed and compare it with plain global targets and
project mode. The recipe, config reference, MCP and UI command pages
are updated in English and the four translated locales.
Refs #286
The cross_target_discovery suggestion pointed users at removing the
writer target (e.g. universal). That target owns a shared directory, so
removing it also hides skills from every other tool that reads the same
path. Removing the scanning target (e.g. codex) only affects that one
runtime, which still receives the content through the shared directory.
Reword the suggestion and the matching docs resolution in all locales.
Refs #135
The mcp reference gains sections for managing several projects from the
global config, the dashboard's Projects tab and Defaults, and Pi direct
tools. It states that a project lists only what differs: a global server
already loads in every project because the Agent merges its global and
project files, a point readers arriving at that section kept missing.
A new recipe, many projects from one config, shows skills and MCP servers
together, since custom path targets already solve the skills half.
The built-in skill's MCP reference is rewritten around the same material so
an Agent editing config.yaml for a user knows these rules.
All of it is mirrored in zh-Hant, zh-Hans, ja and ko.
Refs #286
Completes zh-Hant, zh-Hans, ja, and ko translation of the final 50
pages (how-to/, learn/, reference/targets/, reference/appendix/,
reference/filtering.md, reference/index.md, troubleshooting/),
bringing all four locales to full parity with the English docs tree.
Anchor ids added in the previous commit are propagated to every
translated heading they land on, and one zh-Hans same-file link that
pointed at the pre-translation auto-slug is repointed at the pinned
id.
- how-to/advanced/security.md: pin {#periodic-scanning} on 'Periodic
Scanning', linked from this same page by anchor fragment.
- how-to/advanced/docker-sandbox.md: pin {#dev-profile} on 'Dev
Profile', same reason.
- how-to/daily-tasks/organizing-skills.md: pin
{#install-directly-into-folders} on that heading, same reason.
Without an explicit id, translating the heading text changes its
auto-generated slug and breaks the in-page link once translated.
- how-to/daily-tasks/creating-skills.md: the nested code-fence example
under 'Include examples' used the same 3-backtick fence for both the
outer block and the inner ```python block, so the inner fence's
info string didn't count as a closer but the following bare fence
did, silently truncating the outer block and leaving a dangling
opener for the rest of the file. Widened the outer fence to 4
backticks.
These headings mix prose with technical terms (e.g. '.skillignore
(Optional)', 'Git Authentication', 'Target include/exclude filters')
and are referenced by anchor fragment from other pages. Translating
the prose changes the auto-generated slug and breaks the link, so
pin the current slug explicitly before the next translation batch.
The unanchored patterns matched any nested file with that basename
(case-insensitively), so every translated understand/agents.md under
website/i18n/ and website/CLAUDE.md were silently excluded from every
commit since they were created. This broke the ja/ko/zh-Hans/zh-Hant
Pages build in CI: relative links to ./agents.md resolved to a file
that didn't exist in the checked-out tree, even though it existed
locally. Anchoring the patterns with a leading slash keeps them
scoped to the repo-root personal instruction files they were meant
for, and recovers the four missing translations plus website/CLAUDE.md.