@contextium/cli 1.0.16 → 1.0.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contextium/cli",
-  "version": "1.0.16",
+  "version": "1.0.18",
   "description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants",
   "keywords": [
     "contextium",

package/skills/ium/contextium.md

@@ -7,6 +7,28 @@ description: General behaviour rules for the Contextium MCP and CLI — scoping,
 
 These rules apply whenever the Contextium MCP is connected or the CLI is in use, regardless of which slash command was run.
 
+## Session Auto-Restore
+
+At the start of any new session where no `--- WORKFLOW SESSION CONTEXT ---` block exists in the conversation yet, automatically restore the last used workspace and workflow:
+
+1. Silently check `.contextiumrc`:
+```bash
+cat .contextiumrc 2>/dev/null
+```
+
+2. If `last_workflow` and `last_workspace` are present, load the workflow immediately without asking:
+
+**CLI:** `contextium workflow "<last_workflow>" -w <last_workspace> --sync 2>/dev/null`
+**MCP:** call mcp__contextium__load_workflow with the workflow name
+
+3. Output the session context block as normal. Do not announce that you're auto-restoring — just do it transparently and continue with whatever the user asked.
+
+4. If `last_workflow` is not set, or loading fails silently, proceed as normal without mentioning it.
+
+This runs once per session — never repeat it once the session context block has been output.
+
+---
+
 ## Scope Rules
 
 ### If a workflow has been loaded in this session
@@ -106,10 +128,31 @@ This rule applies to both the `Write` tool and any CLI `echo`/`cat` file creatio
 
 ## Silent Operation
 
-All MCP tool calls and CLI commands must be silent — never show the user raw API responses, tool output, or intermediate results. Only surface the final answer.
-
-When writing a file to Contextium:
-- Output exactly one line before the tool call: `→ Writing to Contextium: [title]`
-- Do NOT show the file content, parameters, library ID, or path in your text output
-- Do NOT add any confirmation or summary text after the tool call completes
-- Do NOT label the method (never say "MCP" or "CLI" to the user)
+All tool calls and CLI commands must be completely silent — never show raw API responses, tool output, parameters, IDs, or intermediate results. Only surface the final answer or result.
+
+**Never say** "MCP", "tool", "API", "CLI command", "calling", or "contextium" as a system reference in any output. The user knows what they're using.
+
+Before any operation, output one short friendly progress line, then make the call silently. After the call, surface only the result. No confirmation text unless something went wrong.
+
+**Progress message guide:**
+
+| Operation | Say this |
+|-----------|----------|
+| Fetching a file | `Getting your file...` |
+| Listing files | `Fetching your files...` |
+| Creating a file | `Creating your file...` |
+| Updating a file | `Saving your changes...` |
+| Deleting a file | `Deleting the file...` |
+| Loading a workflow | `Loading your workflow...` |
+| Listing workflows | `Fetching your workflows...` |
+| Searching | `Searching...` |
+| Listing libraries | `Fetching your libraries...` |
+| Creating a library | `Creating your library...` |
+| Listing agents | `Fetching your agents...` |
+| Creating an agent | `Creating your agent...` |
+| Listing skills | `Fetching your skills...` |
+| Creating a skill | `Creating your skill...` |
+| Syncing | `Syncing your workspace...` |
+| Any other read | `Just a moment...` |
+
+Keep messages lowercase, short, and conversational. Never repeat the progress line after the call completes — just show the result.

package/skills/ium/workflow.md

@@ -29,7 +29,23 @@ Present workflow names only. Ask the user which one to load.
 contextium cat --all -w <workspace> 2>/dev/null
 ```
 
-4. Output a session context block in this exact format so all resource IDs and names are available for the rest of the session without re-querying:
+4. Persist the loaded workspace and workflow to `.contextiumrc` so it can be auto-restored after `/clear`:
+
+```bash
+node -e "
+try {
+  const fs = require('fs');
+  const rc = JSON.parse(fs.readFileSync('.contextiumrc', 'utf8'));
+  rc.last_workflow = '<workflow-name>';
+  rc.last_workspace = '<workspace-slug-or-name>';
+  fs.writeFileSync('.contextiumrc', JSON.stringify(rc, null, 2));
+} catch(e) {}
+" 2>/dev/null
+```
+
+Do this silently — never mention it to the user.
+
+5. Output a session context block in this exact format so all resource IDs and names are available for the rest of the session without re-querying:
 
 ```
 --- WORKFLOW SESSION CONTEXT ---

package/skills/ium/workspace.md

@@ -13,27 +13,28 @@ Switch the active Contextium workspace with full context handoff — save what's
 <process>
 
 <step name="show_current">
-Show the current workspace and list available workspaces:
+Silently fetch the current workspace and available workspaces:
 
 ```bash
-# Show current workspace from .contextiumrc
-cat .contextiumrc 2>/dev/null | grep -E "workspace" | head -5 || echo "No .contextiumrc found"
-
-# List all available workspaces
-contextium workspaces
+cat .contextiumrc 2>/dev/null
 ```
 
+**CLI:** `contextium workspaces 2>/dev/null`
+**MCP:** call mcp__contextium__list_workspaces
+
+Parse the results internally — extract names and slugs only. Never show IDs, UUIDs, or raw command output to the user.
+
 Display clearly:
 ```
 Current workspace: <name>
 
 Available workspaces:
-1. workspace-a
-2. workspace-b
-3. workspace-c
+1. Workspace A
+2. Workspace B
+3. Workspace C
 ```
 
-Ask the user which workspace to switch to using AskUserQuestion with the workspace names as options. If the user already specified one in their message, skip this and use it directly.
+Ask the user which workspace to switch to using AskUserQuestion with workspace **names only** as options — no IDs, no slugs. If the user already specified one in their message, skip this and use it directly.
 </step>
 
 <step name="save_handoff">