Skip to content

Installed

Mel edited this page Nov 10, 2026 · 1 revision

Shows what this project imported from the stack. It needs a project.

imported  skills/file-pr        @b51359b → .agents/skills/file-pr        remove
imported  styles/folio-light    @b51359b → .agents/skills/folio-light    remove
imported  workers/mel           @b51359b → .stack/workers/mel            remove

sync @b51359b

adopt…

presets
web   React starter: button plus the file-pr skill.       apply
docs  Docs setup: conventions plus the agents-md scaffold. apply

stack /home/dev/escacs/stack   change   auto
app 0.1.0   check
0.1.0

(The /home/dev/... path is a fixture from the docs, not a real path.)

Rows with upstream changes look like this:

update    skills/file-pr        @a1b2c3d → .agents/skills/file-pr        update  remove
          2 files changed upstream
          edited: SKILL.md

update    templates/agents-md   @a1b2c3d → .                             update  remove
          1 file changed upstream

update all   sync @b51359b

The @… value is the stack commit the import was made from.

Row states

State When Sub-line
imported the files match the import and the stack has no newer content for them none
edited at least one file differs from the import, or is missing edited: <files>
update the stack's HEAD has different content for at least one file N files changed upstream
gone the entry no longer exists at the stack's HEAD removed from stack

The chip shows the first matching state in this order: gone, update, edited, imported. A row can be update and still list edited: files. A deleted file counts as edited; sync restores it.

Actions

Control Shows when Does Does not
update row is update three-way merge of the row's files to the stack's HEAD. Overlapping edits get <<<<<<< markers, and the file is listed under conflicts does not drop your edits; does not run for gone rows
update all any row is update the same for every row
remove every row deletes the import's unedited files and its entry in stack.toml does not delete edited files; they are listed as kept (edited here)
sync any row restores imported files that are missing, at the commit recorded in stack.toml never overwrites an edit; does not move to newer content (that is update)
init stack.toml no rows, and no stack.toml in the project creates stack.toml and the managed .gitignore block. A legacy stack.lock.json is migrated and removed imports nothing
adopt… always a form for an entry id, such as skills/file-pr, and an optional --to. It runs the same import as Browse differing files are listed and nothing is written
preset apply a preset exists imports every row of that preset, each with its --to refuses like import when files differ
change always picks another stack checkout and saves it
auto a folder is saved clears the saved folder: back to automatic lookup

Use adopt… for a folder that holds an entry's files but was never imported. Identical files join the record. If any file differs, the app lists it and writes nothing.

Each action shows its result under the rows, as titled sections. A failed action shows the CLI's error text as it is. Only one action runs at a time; the other buttons are disabled meanwhile. Every action re-reads the rows when it ends.

Presets

Presets are named import plans. The stack defines them in its presets/*.toml files. Each row here is one preset. Its apply imports all of the preset's rows, the same way import does. Hover apply to see what it imports. Rows do not expand.

Stack checkout

The line under the rows shows the checkout in use. change picks another folder and saves it as the override. auto appears only when an override is saved, and removes it.

App updates

  • At startup the app checks the release feed once, in the background. A newer version shows in the footer as → <version> available. A failed startup check is written to the terminal only.
  • check runs a check now. It shows up to date, or the error text.
  • install appears when a newer version is known. It downloads with progress, checks the signature, and installs. Then relaunch appears.
  • Self-update on Linux works for the AppImage. Development builds can check but cannot install over themselves. See Updates and Releases.

See also: Browse, Settings and Storage, Updates and Releases.

Clone this wiki locally