cc-peer 1.1.7 → 1.1.9

package/README.md

@@ -61,5 +61,6 @@ The REST facade (`npx cc-peer`) serves `GET /sessions`, `POST /messages`, `POST
 
 - **Same-process constraint**: receipts and idle notices only reach the process that owns the peer's listening socket (the protocol verifies return addresses via kernel peer-pids). Do not split `CcPeer` listening and sending across processes or differently-owned workers.
 - **Single machine**: the local protocol is Unix-socket only. Writing to cloud sessions directly is blocked by design (device-attestation-signed events); bridged sessions reachable locally still work via their local mirror.
+- **No native Windows support**: Claude Code's own peer protocol addresses sockets by filesystem path end to end, but Node's `net` module has no real AF_UNIX support on Windows — its local domain there is implemented with named pipes, which must live under `\\.\pipe\`, not an arbitrary path (see [nodejs/node#55979](https://github.com/nodejs/node/issues/55979)). `CcPeer.start()` cannot bind a listening socket on Windows as a result. The SEA release matrix builds darwin and linux only for this reason; running from source or `npx` on Windows hits the same limitation.
 - **File transfers to Claude sessions** wait on an upstream feature flag (`tengu_send_file`) before Claude-side materialisation activates; peer-to-peer transfers work today.
 - Verified against Claude Code 2.1.269; treat every Claude Code upgrade as a potential protocol change.

package/dist/cc-peer.d.cts

@@ -70,12 +70,12 @@ declare const RegistryEntrySchema: z.ZodObject<{
   nameSince: z.ZodOptional<z.ZodNumber>;
   updatedAt: z.ZodNumber;
   status: z.ZodOptional<z.ZodEnum<{
-    idle: "idle";
     busy: "busy";
     shell: "shell";
+    idle: "idle";
     waiting: "waiting";
   }> & {
-    is(value: unknown): value is "idle" | "busy" | "shell" | "waiting";
+    is(value: unknown): value is "busy" | "shell" | "idle" | "waiting";
   }>;
   statusUpdatedAt: z.ZodOptional<z.ZodNumber>;
   bridgeSessionId: z.ZodOptional<z.ZodString>;
@@ -97,7 +97,7 @@ declare const RegistryEntrySchema: z.ZodObject<{
     name?: string | undefined;
     nameSource?: "user" | "peer" | "derived" | "collision" | "auto" | "hook" | undefined;
     nameSince?: number | undefined;
-    status?: "idle" | "busy" | "shell" | "waiting" | undefined;
+    status?: "busy" | "shell" | "idle" | "waiting" | undefined;
     statusUpdatedAt?: number | undefined;
     bridgeSessionId?: string | undefined;
   };

package/dist/cc-peer.d.mts

@@ -70,12 +70,12 @@ declare const RegistryEntrySchema: z.ZodObject<{
   nameSince: z.ZodOptional<z.ZodNumber>;
   updatedAt: z.ZodNumber;
   status: z.ZodOptional<z.ZodEnum<{
-    idle: "idle";
     busy: "busy";
     shell: "shell";
+    idle: "idle";
     waiting: "waiting";
   }> & {
-    is(value: unknown): value is "idle" | "busy" | "shell" | "waiting";
+    is(value: unknown): value is "busy" | "shell" | "idle" | "waiting";
   }>;
   statusUpdatedAt: z.ZodOptional<z.ZodNumber>;
   bridgeSessionId: z.ZodOptional<z.ZodString>;
@@ -97,7 +97,7 @@ declare const RegistryEntrySchema: z.ZodObject<{
     name?: string | undefined;
     nameSource?: "user" | "peer" | "derived" | "collision" | "auto" | "hook" | undefined;
     nameSince?: number | undefined;
-    status?: "idle" | "busy" | "shell" | "waiting" | undefined;
+    status?: "busy" | "shell" | "idle" | "waiting" | undefined;
     statusUpdatedAt?: number | undefined;
     bridgeSessionId?: string | undefined;
   };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-peer",
-  "version": "1.1.7",
+  "version": "1.1.9",
   "description": "Communicate with local Claude Code instances over their native cross-session peer messaging: send and receive messages, register as a named discoverable peer, receipts, idle subscriptions, and a REST facade via `npx cc-peer`.",
   "type": "module",
   "license": "MIT",