@dsiloed/silo-link 1.0.0 → 1.0.1

package/README.md

@@ -26,21 +26,15 @@ Claude Code (tmux) ──MCP──►  :3579    ──REST API──►  ├─
 - **Agent Dashboard** — active sessions appear in Mission Control with real-time status
 - **Control Channel** — launch/stop/status commands via ActionCable from the UI
 - **Channel linking** — command Claude from Slack, Discord, Teams, or SMS
+- **Session continuity** — `remote_load_context` restores prior conversation history on session restart
 
 ## Installation
 
 ```bash
-git clone git@gitlab.com:model-api/silo_link.git
-cd silo_link
-pnpm install
-pnpm build
+npm install -g @dsiloed/silo-link
 ```
 
-To make the `silolink` command available globally:
-
-```bash
-pnpm link --global
-```
+This installs the `silolink` CLI globally.
 
 ## Configuration
 
@@ -172,6 +166,7 @@ tmux attach -t silolink-claude-1774363497579
 | Tool | Description | Blocking |
 |------|-------------|----------|
 | `remote_register` | Register session, create/attach conversation | No |
+| `remote_load_context` | Load prior conversation history for session continuity | No |
 | `remote_notify` | Fire-and-forget message | No |
 | `remote_ask` | Post question, wait for reply | Yes |
 | `remote_poll` | Non-blocking check for next message (**recommended**) | No |
@@ -189,6 +184,15 @@ Output: { session_id, conversation_id, conversation_url }
 
 When `conversation_id` is provided, attaches to that existing conversation (used by auto-launcher).
 
+### remote_load_context
+
+```
+Input:  { conversation_id?: 109, limit?: 50 }
+Output: { success: true, conversation_id, resume_id, message_count, history: [...] }
+```
+
+Fetches prior conversation history and the last `claude_resume_id` from agent session metadata. Call after `remote_register` when attaching to an existing conversation to restore session continuity.
+
 ### remote_poll (Recommended)
 
 ```
@@ -244,13 +248,15 @@ When the SiloLink MCP server is connected:
 
 1. Register with `remote_register({ session_name: "<name>" })`.
    If a conversation_id is provided, pass it too.
-2. ALL communication MUST go through SiloLink — never write to terminal.
-3. Send progress updates with `remote_notify()`.
-4. When idle, use the poll loop:
+2. **Session Continuity**: If you registered with an existing conversation_id,
+   call `remote_load_context()` to load prior conversation history.
+3. ALL communication MUST go through SiloLink — never write to terminal.
+4. Send progress updates with `remote_notify()`.
+5. When idle, use the poll loop:
    - Call `remote_poll()` — returns instantly
    - If `{ pending: true }`: sleep 3s, poll again
    - If message received: process it, notify result, resume
-5. Use `remote_ask()` for questions needing immediate reply.
+6. Use `remote_ask()` for questions needing immediate reply.
 ```
 
 ### Poll Loop Pattern
@@ -259,6 +265,10 @@ When the SiloLink MCP server is connected:
 // Register (use conversation_id if provided in launch prompt)
 remote_register({ session_name: "portablemind", conversation_id: 123 })
 
+// If attaching to existing conversation, load prior context
+context = remote_load_context()
+// Review context.history to understand what was discussed
+
 // Poll loop
 while (idle) {
   result = remote_poll()
@@ -340,11 +350,11 @@ src/
   mcp/
     server.ts                   # MCP server (Streamable HTTP on Express)
     tools/
-      register-tools.ts         # All 8 MCP tool definitions
+      register-tools.ts         # All 9 MCP tool definitions
   types/
     index.ts                    # Shared TypeScript interfaces
 ```
 
 ## License
 
-Private — model-api/silo_link
+MIT — see [LICENSE](LICENSE)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dsiloed/silo-link",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Claude Code Remote Bridge — connects Claude Code sessions to DSiloed via MCP + ActionCable",
   "type": "module",
   "license": "MIT",