pi-spaces 0.16.0 → 0.16.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ commands and options and a patch version fixes.
6
6
 
7
7
  ## Unreleased
8
8
 
9
+ ## 0.16.2
10
+
11
+ ### Changed
12
+
13
+ - The skill tells how to pin a space to a repository with `pi-space pin` (pi-spaces-cli 0.18.0).
14
+
15
+ ## 0.16.1
16
+
17
+ ### Changed
18
+
19
+ - The `pi-spaces` skill and the README say that `pi-space setup` runs in base too,
20
+ for a profile that has a setup command (pi-spaces-cli 0.17.0); the built-in `pi`
21
+ has none.
22
+
9
23
  ## 0.16.0
10
24
 
11
25
  ### Changed
package/README.md CHANGED
@@ -40,7 +40,7 @@ pi-spaces ships as two independent npm packages. They read the same spaces and t
40
40
 
41
41
  **The command without the extension:**
42
42
 
43
- - With the built-in `pi` profile (or any `commands.space` without `{home}`), starting a space runs `pi --space <name>`, and the package commands run `pi --space <name> update`. Only the extension understands `--space`, so these need it in the base home. Commands that only touch folders (`new`, `setup`, `rename`, `remove`, `migrate`, `list` without a space, `init`) never need it.
43
+ - With the built-in `pi` profile (or any `commands.space` without `{home}`), starting a space runs `pi --space <name>`, and the package commands run `pi --space <name> update`. Only the extension understands `--space`, so these need it in the base home. A package command in `<profile>/base` runs plain `pi update` (no `--space`), so `pi-space install pi/base npm:pi-spaces` works before the extension is there. Commands that only touch folders (`new`, `setup`, `rename`, `remove`, `migrate`, `list` without a space, `init`) never need it.
44
44
  - Inside Pi there is no `/space`, no status line, and the model gets no `<pi_space>` section. The variables `PI_SPACE` and `PI_SPACE_HOME` are still set for Pi's tools.
45
45
  - `pi-space new` asks whether the new space's `agent/settings.json` declares the extension (Enter is yes), and Pi installs what that file declares the first time it runs there. Answer no, or pass `--no-extension`, to keep the space without it; `--extension` declares it without asking, and without a terminal it is declared. `/space new` always declares it, since it runs inside the extension.
46
46
 
@@ -167,7 +167,7 @@ The `pi-spaces-cli` package adds a `pi-space` command to your shell; it works wi
167
167
  | `pi-space` | Opens a picker of the spaces of every profile and starts Pi in the one you choose. |
168
168
  | `pi-space <profile>/<name> [pi args...]` | Starts Pi in a named space; `<profile>/base` runs the profile's `commands.base` as it is. |
169
169
  | `pi-space new <profile>/<name> [--extension\|--no-extension]` | Creates a space, asking whether it declares the extension, then runs the profile's setup command. |
170
- | `pi-space setup <profile>/<name\|--every>` | Runs the setup command again. |
170
+ | `pi-space setup <profile>/<name\|base\|--every>` | Runs the setup command again; in `base` too for a profile that has one. |
171
171
  | `pi-space rename <profile>/<old> <new>` | Renames a space. |
172
172
  | `pi-space remove <profile>/<name>` | Deletes a space, after asking. |
173
173
  | `pi-space migrate <profile>/<name\|--every>` | Gives an old space the [`agent/` layout](#moving-an-old-space). |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-spaces",
3
- "version": "0.16.0",
3
+ "version": "0.16.2",
4
4
  "description": "Named spaces for Pi: keep several agent homes (sign-ins, packages, settings) and pick one by name.",
5
5
  "license": "MIT",
6
6
  "author": "jals1212",
@@ -33,9 +33,10 @@ Use when a task depends on which Pi agent home this session uses (settings, sign
33
33
  | Spaces folder | `PI_SPACES_DIR`, else the `dir` of the profile whose `home` is the base home, else `spaces` next to the base home (`PI_SPACES_BASE_HOME`, else this home) |
34
34
  | Profiles, or why a variable differs per space | The config file (`PI_SPACES_CONFIG`, else `config.toml` or `config.json` in `~/.config/pi-spaces`, then in `~/.pi-spaces`): a profile's `spaceEnv` variables are set only inside spaces (`{home}` the agent home, `{space}` the space's root folder and `{name}` filled in) and removed in base; without `spaceEnv` whatever a program keeps outside its agent home is shared with base |
35
35
  | Pick a space from a shell | bare `pi-space` on a terminal opens a picker of every profile's spaces (`<profile>/<name>`, `base` included) and starts Pi in the one chosen |
36
+ | Pin a space to a repository (like `.nvmrc`) | `pi-space pin <profile>/<name>` writes `.pi/pi-space/space` (one line `<profile>/<name>`) and a self-ignoring `.pi/pi-space/.gitignore` in the git root; a bare `pi-space` there or below then starts that space at once (a space named on the command line wins; `pi-space pick` opens the picker); `pi-space pin` shows it, `pi-space unpin` removes it. Only `pi-space` reads it, not Pi or `/space` |
36
37
  | Rename a space | User request only: `pi-space rename <profile>/<old> <new>`; the new name alone or with the same profile (`<profile>/<new>`), a space never changes profile; refused for base and for the space you are in |
37
38
  | Create a space | `pi-space new <profile>/<name>`, or ask the user for `/space new <name>` (this Pi's profile); `pi-space new` also runs the profile's setup command when there is one (or `--setup <cmd>` for one call), and asks whether the space declares the extension: pass `--extension` or `--no-extension` when running it for the user, since there is no terminal to answer |
38
- | Prepare a space for the program that runs Pi | `pi-space setup <profile>/<name>` (or `<profile>/--every`, or `--every` for every profile with a setup; the profile's `commands.setup`): runs the setup command (`{home}` becomes the space's agent home, `{space}` its root folder and `{name}` its name) with the agent home as `PI_CODING_AGENT_DIR`; never in base |
39
+ | Prepare a space for the program that runs Pi | `pi-space setup <profile>/<name>` (or `<profile>/base`, `<profile>/--every` for base then its spaces, or `--every` for the base and spaces of every profile with a setup, which pi has not by default; the profile's `commands.setup`): runs the setup command (`{home}` becomes the space's agent home, `{space}` its root folder and `{name}` its name) with the agent home as `PI_CODING_AGENT_DIR`; in base `{home}` is the profile's home and `{name}` is `base` |
39
40
  | Work in another space | User runs `/space switch <name>` (with a v2 profile it runs `commands.space`, or `<commands.base> --space <name>`; `/space switch base` runs `commands.base`; otherwise Pi starts again), or `$PI_SPACES_COMMAND --space <name> "<prompt>"` (only when the command has no `{home}` or `{name}`), or `pi-space <profile>/<name>` from a shell |
40
41
  | Give an old space the `agent/` layout | User request only: `pi-space migrate <profile>/<name>` (or `<profile>/--every`, `--every`): copies the space to `.backups`, then moves its content into `<space>/agent/`; refuses base, the space you are in and a space that already has `agent/` |
41
42
  | Remove a space | User request only: `pi-space remove <profile>/<name> --yes` keeps a backup in `.backups` |