epiq 1.3.3 → 1.3.5

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "epiq",
-	"version": "1.3.3",
+	"version": "1.3.5",
 	"license": "MIT",
 	"type": "module",
 	"description": "EPIQ - ergonomic, distributed CLI-first issue tracker TUI ready for the agentic era",
@@ -64,7 +64,10 @@
 		"meow": "^14.1.0",
 		"react": "^19.2.4",
 		"react-dom": "^19.2.6",
+		"react-markdown": "^10.1.0",
 		"react-router-dom": "^7.17.0",
+		"remark-breaks": "^4.0.0",
+		"remark-gfm": "^4.0.1",
 		"string-width": "^8.2.0",
 		"ulid": "^3.0.2",
 		"ws": "^8.21.0",

package/readme.md

@@ -183,6 +183,10 @@ claude mcp add epiq -- npx -y -p epiq epiq-mcp
 
 Use `--scope user` to make Epiq available in every directory; omit it to register Epiq only for the current project. Verify the connection with `claude mcp list` (it should report `epiq … ✔ Connected`). MCP servers are loaded at startup, so **restart Claude Code** after adding the server before its tools become available.
 
+### Skills
+
+Find skill at `.claude/skills/epiq/SKILL.md` that documents a recommended workflow for working the Epiq.
+
 ### Other MCP clients
 
 For clients that are configured by hand, add the following to the client's MCP config file — note this is **not** the same as Claude Code's `~/.claude.json`; Claude Desktop uses `claude_desktop_config.json`:
@@ -198,9 +202,31 @@ For clients that are configured by hand, add the following to the client's MCP c
 }
 ```
 
-
 Once registered, agents can interact with your local Epiq instance through the MCP.
 
+### Sandboxed or network-restricted environments
+
+`npx -y -p epiq epiq-mcp` resolves the package against the npm registry **every time it starts**, even if it's already cached locally. In agent sandboxes with restricted network access, this can make the MCP server appear to hang — `npx` retries DNS resolution instead of failing fast, and there's no MCP-level error to explain why.
+
+If you're running Epiq's MCP server in such an environment, install it globally once and point your MCP config at the resolved executable directly, bypassing `npx` (and the registry lookup) entirely on every subsequent start:
+
+```bash
+npm install --global epiq
+which epiq-mcp   # use this absolute path in your MCP config
+```
+
+```json
+{
+	"mcpServers": {
+		"epiq": {
+			"command": "/absolute/path/to/epiq-mcp"
+		}
+	}
+}
+```
+
+`npx` remains the simpler option for normal, network-connected setups.
+
 ---
 
 ## How Epiq is synchronized
@@ -249,6 +275,7 @@ Epiq follows a **local-first** model:
 > Frequent synchronization reduces divergence and keeps the system predictable
 
 ---
+
 [![GitHub Sponsors](https://img.shields.io/badge/Sponsor-Epiq-pink?logo=github)](https://github.com/sponsors/ljtn)
 
 🫡 Never leave your editor!