The Backups tab only listed target snapshots and was hidden in project
mode, while file backups had no view at all and MCP backups sat in a
dialog on the MCP page. The tab now has three sections: target folders
(filter, copy path, delete one snapshot), files (each version with why
it was taken, a diff or full-text preview, and restore) and MCP (grouped
by agent config, opening the existing restore dialog). It is shown in
project mode too, scoped to the project.
Refs #299
Single-file extras in a project sat in the Folders tab and looked like
folder extras: a folder icon, folder modes and a flatten switch, with
no import mode and no sync on add. They now appear as shared-file cards
on the project AGENTS.md tab, reusing the global location rows and Add
location dialog with project-relative paths. The Folders tab lists only
folder extras in both modes, so the file-name field added there is gone.
The CJK location counts now say "locations", since the card header has
no heading next to it to give "2" its meaning.
Refs #299
An edited location only showed a hint, with no way to settle it. It now
gets the same collect and reapply note as a target row. The remove
dialog closes before removing, so the refetch no longer asks for the
preview of a location that is gone.
Refs #299
Show locations outside the tool list under the shared file, with an add
dialog for folder, file name and mode, a restore preview before removal,
and localized errors. The project Extras page takes a file name for
single-file extras.
Refs #299
Every rider row repeated the same line under its path on the AGENTS.md page, which is about instructions, not skills. The origin now shows when hovering the tool name.
Refs #299
"Run a sync" did not say where. The copy option now points at the Sync button that appears above the targets when the shared file changes elsewhere.
Refs #299
The copy option reused the Skills folder-copy text and glued a second sentence on with a space, which read oddly in Chinese. It now has one sentence about copying the shared file.
Refs #299
Mode changes, attach and the other AGENTS.md actions returned English
sentences, so a zh-TW dashboard showed "backed up ... before replacing
it" and "... is a directory" untranslated. Warnings are now
{code, params, message} and every instructions error carries a code,
so the dashboard shows them from i18n and falls back to the English
message for unknown codes. CLI output is unchanged.
Also from the Windows re-test:
- replacing a user's junction says so and where it pointed;
- status, doctor and sync agree on identical unowned copies (kept, not
linked), and an identical copy no longer suggests --force;
- the targets list shows a Developer Mode tooltip when file links are
unavailable;
- file names are taken from Windows paths too.
Refs #299
Updating many resources gave no sense of progress, and a failure was
easy to miss among the rest. The status card now shows a progress bar,
the row being updated gets a moving line and a pop when it finishes,
and blocked or failed updates move to their own section with a
one-line reason. Motion is off under prefers-reduced-motion.
A real directory at a target path showed the generic drift hint ("sync
will change it back") although sync refuses to replace a directory. The
assignment now carries reason "directory" and the row says to remove or
rename the folder.
The restore plan read "personal stay" in English because the kept-files
line had no singular form.
Refs #299
Connect-all still planned to switch a target that another shared file
holds in copy mode (the API marks only links as linked_shared), which
would silently take it from that file. Any link or copy assignment now
marks the target as held, so the switch step is gone.
The header tabs sat on the strip's divider; they are now centred with
room under the underline.
Refs #299
Exploratory testing of the dashboard found edits lost without warning,
Cmd+S saving the page editor through an open dialog, and a connect-all
plan that would write an import through another shared file's link.
- Unsaved edits now ask before leaving the target tab, closing the edit
dialog, or reloading.
- Cmd+S does nothing to the page editor while a dialog is open.
- Connect-all skips targets already held by another shared file
(linked_shared), and 409 instructions_target_held shows its reason.
- Mode and attach warnings (such as a backed-up edit) show in a toast.
- Restore wording matches what restore does; the per-file connect time
was dropped because the record is per target file.
- Convert defaults to a new shared file; a new file is selected at once;
an unknown ?file= falls back and fixes the URL.
- The collapsed shared-file card scrolls instead of clipping.
- Change location is disabled while a shared file holds the target.
Refs #299
Every AGENTS.md box showed its size and view switch differently, which
read as clutter. One header strip now carries the live line count and
the Preview/Source switch everywhere; the read-only card opens in
Preview since that is what people read first.
The target page editor now saves with Cmd/Ctrl+S. An open editor
claims the shortcut so it no longer jumps to Sync while editing.
Read-only raw text wraps instead of scrolling sideways.
Refs #299
The edit/preview switch existed only on the target page, so the shared
file's editor, the new-file dialog and the read-only card still showed
raw Markdown. They now share one tab component: Edit | Preview in the
editors and Source | Preview on the read-only card, with previews built
from the unsaved draft.
The read order also listed rule folders such as claude's rules/*.md with
"0 files" for everyone who does not use them; empty folders are now left
out and a folder appears once it holds files.
Refs #299
Saving a shared AGENTS.md in the dashboard only wrote the source, so every
target in copy mode (including the Windows copy fallback) kept the old
content until someone found the sync button. Saving now rewrites that
file's copy targets through the regular extras sync, so an edited copy is
still backed up first, and the toast names the copies it updated. Link and
import targets already read the source and are left alone.
Refs #299
The AGENTS.md tab picked each target's mode for the user (import where
supported, a link elsewhere), which left Windows users without Developer
Mode no way out of a broken link and gave no copy option. Restore replaced
a file without showing what would come back, and only custom tools could
change which file a target reads.
- Each connected target gets a mode picker (import, symlink, copy); symlink
is unavailable when the machine cannot create file links, and a target
whose file is a folder link says so.
- Restore opens a preview of the file after restore and its diff.
- Every supported target can change its file location and name in a
dialog, with reset to default.
- The target file tab is a single column with the read order on one line,
a tinted managed import block, soft wrap, and an edit/preview switch;
universal lists the files of the tools that read its skills.
- The convert dialog shows only the methods that apply and a ready preview.
Refs #299
With only universal configured, tools such as Codex, Gemini CLI and Pi
still read skills from ~/.agents/skills, but none of them reads
~/.agents/AGENTS.md, and their own instruction files had no page and
could not take a shared AGENTS.md. Universal's AGENTS.md tab now offers
the installed ones in a dropdown, and the shared AGENTS.md list includes
them. A tool is listed once per file and disappears when it becomes a
target of its own.
Cline and the Warp Agent CLI read ~/.agents/AGENTS.md itself, per their
docs, so they now share universal's file.
Git opens every HTTPS failure with "unable to access", a bad certificate
or a 403 included, and a missing git-lfs says "command not found". Those
were reported as a network problem or a missing source and sent the user
to the wrong fix; they now fall back to the general failure.
Discovery of a managed plugin is also cached per plugin, since two
plugins of one source can have snapshots at different commits.
Opening a plugin cloned its whole source again to learn which Agents
can take it, which took tens of seconds per row. A managed plugin
already has a reviewed snapshot; it answers when its digest still
matches, and the network is used only otherwise.
A failed clone said only that git failed. Git's output is sorted into
an unreachable source or a missing one without passing it on, since it
can hold credentials. The dashboard translates those, notes when a read
or an Agent's CLI is slow, and says when the browser is offline.
Project targets (`<project>@<tool>`) drew the same icon as the global
tool, so a skill synced to claude plus two projects showed three Claude
icons and the Targets column could not say which was which.
The icon stack now holds global tools only, followed by a count of the
projects the skill reaches; hovering lists global tools and each
project's tools, naming projects it misses. The Target filter groups
global tools and projects, with one entry per project. In the tree
view the Targets row shows where a single skill actually goes, tagging
a `targets:` that narrows it. Without projects the page is unchanged.
Refs #297
The shared AGENTS.md tab split its controls between a list and a
separate detail page, so connecting a target, editing the file and
fixing drift meant moving between pages and repeating the same
target list twice.
Everything now lives in one panel next to the file list: a short
preview, one switch per target, connect-all and restore-all, and
multi-select with a bulk toolbar. Editing opens a large dialog with
the readers and length warnings beside it. Every change goes through
a confirm dialog, and old detail-page links redirect to the panel.
The delete confirmation no longer says the file is deleted, because
the server only removes it from the list and keeps it on disk.
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.
Claude Code now reads AGENTS.md, but every tool still keeps its standing
instructions in its own file (CLAUDE.md, GEMINI.md, AGENTS.md), and Claude
has no user-level AGENTS.md at all. Keeping several tools on the same
instructions meant copying text between those files by hand.
Each target page gets a tab named after the file it reads, with its read
order, an editor, and a convert flow from CLAUDE.md to AGENTS.md. In global
mode the Extras page gets an AGENTS.md tab where several shared files can
coexist and each target picks one or keeps its own. Shared files are
single-file extras: tools that follow @imports get a managed import block
and keep their own lines, others get a link in place of their file.
Projects get small shims instead, since every tool there reads ./AGENTS.md.
Custom targets can declare which file they read.
Restore records the target's state when it is first attached (file,
symlink, or no file) and always returns to it. Edits made after attaching
are kept as drift backups instead of becoming the restore point, so sync,
reapply and mode switches can no longer lose the user's original file.
When git cannot finish a pull's checkout (for example, it may not unlink
a root-owned file), it stops without undoing the files it already wrote,
and with no MERGE_HEAD there is nothing for merge --abort to undo. The
remote's copies then showed up as local changes: the dashboard blocked
the next pull and suggested committing them, which would push the stale
remote content back as a new commit.
A failed pull now restores paths that were clean before it started and
now hold exactly the upstream version, leaving the user's own edits
alone. The dashboard reports permission failures with a
permission_denied code and shows the chown command that gives the
source folder back to the current user.
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.
Six labelled selects, each reading "All" most of the time, plus a
two-button expand/collapse group made the toolbar wrap and hard to scan.
- Filters are chips: an unset one shows only its name; a set one fills
in, shows its value and has a clear button.
- Group and sort, which change rarely, share one icon menu.
- Expand/collapse all is one button that flips with the tree's state.
The tree showed "Disabled" as hover text on each disabled skill, which
repeated what the dimmed row already said and crowded the hover slot.
A disabled item now swaps its icon for a power-off icon (with an
accessible name), and the hover text is kept only for folder counts.
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
When an Agent's plugin inventory failed (for example OpenCode with both
opencode.json and opencode.jsonc present), the inventory call overwrote
the host's installed list with nil, which the API encoded as null. The
Plugins page read its length unguarded, so one misconfigured Agent
crashed the whole page.
Host.fail now restores an empty list, covering every inventory path
that reports through it, and the dashboard reads a null list as empty
so a single Agent can no longer take the page down.
Refs #296
Two machines sharing a source repo kept stopping at the same two places.
The Git page had no way to know the remote moved until a push bounced, so
it now fetches once on open and labels Pull with the commit count (status
itself stays offline because the sidebar polls it). And both machines
rewrite .metadata.json on every install or update, so nearly every
diverged pull conflicted there; those conflicts are now merged per entry,
keeping the later installed_at, while any other conflict still stops the
pull and names the files.
Once both machines committed, the UI push was rejected and the follow-up
pull failed with "Need to specify how to reconcile divergent branches",
leaving no way out without a terminal. Pull now merges explicitly and
aborts a conflicted merge so a later commit-all cannot push conflict
markers; a rejected push returns push_rejected so the UI offers Pull.
A target's page covered its skills and agents only, so seeing which MCP
servers an Agent gets meant reading across the MCP page's matrix. A
target with an MCP config file now has an MCP tab, in global and -p
mode, with a row per server that saves as it is clicked, and the
Targets list counts those servers beside the skills.
MCP sync writes every target's files at once, so the tab names its
button for that. Its confirm dialog, like the MCP page's and the
project sync dialog, now lists one row per Agent file the way the
Skills sync dialog does, and still says why an MCP entry conflicts.
Each save previews first and sends that revision, so a second click
racing it was refused and rolled back the first; the toggles now wait.
A switch that names no targets no longer gets saved with Agents that
cannot turn a server off, which the backend refused.
Direct tools and other adapter settings were only visible on hover, so
checking which tools a server exposes to Pi meant pointing at every row.
They now sit on a line under the endpoint. Other adapter settings only
say that they are set, since they may hold anything.
Refs #289
Import from an Agent on a project's conflict read the Agent's global
file and wrote to the global source, so the project's own entry could
never be taken over from there. It now reads that project's file and
imports into the project.
The MCP page also crashed on a cold load: a hook ran after the loading
return, so the first render with data called one more hook than before.
Refs #290
Servers added to an Agent directly never showed up in the dashboard, so
they could only be found by opening Import for each Agent in turn. The
MCP page and each project's MCP tab now note which Agent files hold
servers skillshare does not manage, and Import opens on that file; a
project's import reads the file in that project's folder.
Refs #290
Removing a server always ended with its entries cleared from the Agent
config files on the next sync, so there was no way to hand a server back
to the Agent. Stop managing drops it from the source and forgets which
entries it wrote; the files stay as they are and sync leaves them alone.
Available as `mcp remove --keep-files`, in the remove wizard and as a
third choice in the dashboard's remove dialog.
Refs #290
The Skills and Agents lists count project targets in their icon stack,
but the detail page showed only global targets, so the two disagreed.
The detail page now lists each project the resource syncs to and links
to it, since project filters are set per project, not per target.
The Skills and Agents sync dialogs previewed with a dry-run, which reports
every existing link as linked again, so they showed changes on targets
that were already in sync and disagreed with the Sync page and the
project dialog. They now read the same diff as the pending dots.
Refs #289
A project's pending changes could only be written by a full sync, which
also touched global targets and every other project. Sync project on the
project page previews and writes just that project's skills, agents and
MCP; the API takes a project root to scope the resource sync and the MCP
apply.
Refs #289
Syncing meant leaving the page for Sync and reviewing every part at once.
Skills, Agents and MCP now each have a sync button that previews and
writes only that part in a dialog, and the Go to Sync spots after an
update, uninstall or collect open the same dialog. Pi adapter settings
are shown on hover so they can be checked without opening Edit.
Refs #289
Unticking every Agent dropped directTools and piOptions from the source,
so ticking Pi again came back with the adapter reset. The settings now
stay until the adapter itself is changed.
Refs #289
The available-target list comes from a Go map, so the Agents in the
add-target dialog's account mode changed order on every load. Sort them
by name like the known-target list, which puts claude first and pi last.
Refs #289
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 row listed the native field written per Agent in a narrow right-aligned
column, which was tiring to read and meant nothing to someone who has not seen
those files. It now shows the Agents' logos, keeps a sentence only for what
needs a reason, and an old entry with its own Agent list gets a one-click way
to follow the project instead of an instruction.
Refs #289
The dialog rebuilds a server from its fields, so without one for piOptions any
edit from the dashboard would drop what the config holds. It reuses the snippet
editor and refuses text that is not a JSON object, or that sets a field
Skillshare writes itself, before anything is sent.
Refs #289