@skylence-ai/skyline 1.0.34 → 1.0.36

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.
Files changed (2) hide show
  1. package/README.md +8 -7
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -39,22 +39,23 @@ dependency — no native installer or compile step. Alternatives:
39
39
  `cargo binstall skyline`, or a prebuilt archive from
40
40
  [GitHub Releases](https://github.com/skylence-be/binary-skyline/releases).
41
41
 
42
- ### 2. Bootstrap the daemon and agent wiring
42
+ ### 2. Bootstrap the daemon and plugins
43
43
 
44
44
  ```bash
45
45
  skyline setup
46
46
  ```
47
47
 
48
48
  `skyline setup` is the idempotent, cross-package-manager setup path. It installs
49
- the shared HTTP daemon as a supervised autostart service on port 7333, wires
50
- supported AI agents to `http://127.0.0.1:7333/mcp`, and best-effort installs the
51
- Skyline marketplace plugins for agent CLIs already on PATH. Re-run with
52
- `skyline setup --force` after changing agent installs or PATH.
49
+ the shared HTTP daemon as a supervised autostart service on port 7333 and
50
+ best-effort installs the Skyline marketplace plugins for agent CLIs already on
51
+ PATH. Re-run with `skyline setup --force` after changing agent installs or PATH.
53
52
 
54
53
  npm may run this for you as a best-effort postinstall hook, but modern package
55
54
  managers can block lifecycle scripts. If in doubt, run `skyline setup` once.
56
55
 
57
56
  Check it is up with `skyline daemon status` (the port should read `running`).
57
+ To remove the setup-installed daemon, optional plugins, package-manager install,
58
+ skyline-owned dispatchers, and any legacy Skyline agent wiring, run `skyline uninstall --full`.
58
59
  Other install methods are in [docs/install.md](https://github.com/skylence-be/binary-skyline/blob/main/docs/install.md).
59
60
 
60
61
  ### 3. Prompts for your agent
@@ -68,7 +69,7 @@ Prefer skyline's MCP tools over your built-in file read, edit, and search tools
68
69
  Or skip the manual setup entirely and hand your agent this:
69
70
 
70
71
  ```text
71
- Set up skyline for me: install it with `npm install -g @skylence-ai/skyline` (prebuilt binaries for every platform, incl Windows arm64), run `skyline setup` to install the shared HTTP MCP daemon as a supervised autostart service and wire supported agents to it, then verify: `skyline daemon status` must show port 7333 as `running`, and the agent's MCP list/status command must show skyline as connected. Do NOT probe the endpoint with raw curl: it is a stateful streamable-HTTP MCP server that requires an initialize handshake, an Accept header for both application/json and text/event-stream, and a session id, so ad-hoc curl calls fail by design; the agent's MCP status command is the correct connectivity check, and the tools (e.g. `skyline_version`) become callable in your next session. If the port is taken, run `skyline daemon install --port <free-port>` and configure agents to `http://127.0.0.1:<free-port>/mcp`.
72
+ Set up skyline for me: install it with `npm install -g @skylence-ai/skyline` (prebuilt binaries for every platform, incl Windows arm64), run `skyline setup` to install the shared HTTP MCP daemon as a supervised autostart service and install the Skyline marketplace plugins when Claude or Codex CLIs are available, then verify: `skyline daemon status` must show port 7333 as `running`, and the agent's plugin/MCP list or status command must show skyline as connected. Do NOT probe the endpoint with raw curl: it is a stateful streamable-HTTP MCP server that requires an initialize handshake, an Accept header for both application/json and text/event-stream, and a session id, so ad-hoc curl calls fail by design; the agent's MCP status command is the correct connectivity check, and the tools (e.g. `skyline_version`) become callable in your next session. If the port is taken, run `skyline daemon install --port <free-port>` and configure the plugin or explicit agent wiring to `http://127.0.0.1:<free-port>/mcp`.
72
73
  ```
73
74
 
74
75
  ## The numbers
@@ -146,7 +147,7 @@ skyline is one Rust binary with two faces: a command-line tool and an MCP server
146
147
  | Observability streams (audit, devlog, bench) | `skyline audit/devlog/bench` | `skyline_observability_*`, tail and prune tools |
147
148
  | Manage the background daemon | `skyline daemon …` | (CLI) |
148
149
  | Start the daemon on every boot | `skyline daemon install` | (CLI) |
149
- | Bootstrap daemon + agent wiring | `skyline setup` | (CLI) |
150
+ | Bootstrap daemon + plugins | `skyline setup` | (CLI) |
150
151
  | Health check | `skyline doctor` | (CLI) |
151
152
  ### Understanding code, not just matching text
152
153
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skylence-ai/skyline",
3
- "version": "1.0.34",
3
+ "version": "1.0.36",
4
4
  "description": "Content-hash line editor — CLI and MCP server",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -28,11 +28,11 @@
28
28
  "skyline": "bin.js"
29
29
  },
30
30
  "optionalDependencies": {
31
- "@skylence-ai/skyline-darwin-arm64": "1.0.34",
32
- "@skylence-ai/skyline-darwin-x64": "1.0.34",
33
- "@skylence-ai/skyline-linux-arm64": "1.0.34",
34
- "@skylence-ai/skyline-linux-x64": "1.0.34",
35
- "@skylence-ai/skyline-win32-x64": "1.0.34",
36
- "@skylence-ai/skyline-win32-arm64": "1.0.34"
31
+ "@skylence-ai/skyline-darwin-arm64": "1.0.36",
32
+ "@skylence-ai/skyline-darwin-x64": "1.0.36",
33
+ "@skylence-ai/skyline-linux-arm64": "1.0.36",
34
+ "@skylence-ai/skyline-linux-x64": "1.0.36",
35
+ "@skylence-ai/skyline-win32-x64": "1.0.36",
36
+ "@skylence-ai/skyline-win32-arm64": "1.0.36"
37
37
  }
38
38
  }