@lineman-io/mcp 2.3.0 → 2.4.2

package/hooks/core/lineman-config.mjs

@@ -1 +1 @@
-import{readFileSync as o}from"node:fs";import{homedir as e}from"node:os";import{join as n}from"node:path";const r=n(e(),".goodex","lineman.json");export function loadLinemanConfig(){let e={};try{e=JSON.parse(o(r,"utf-8"))}catch{}const n=process.env.LINEMAN_SERVER_URL??("string"==typeof e.serverUrl?e.serverUrl:null),t=process.env.LINEMAN_API_TOKEN??("string"==typeof e.apiToken?e.apiToken:null);return n&&t?{serverUrl:n,apiToken:t}:null}
+import{readFileSync as r}from"node:fs";import{homedir as e}from"node:os";import{join as o}from"node:path";const n=o(e(),".goodex","lineman.json");function t(r,e){return"string"==typeof r[e]?r[e]:null}export function loadLinemanConfig(){let e={};try{e=JSON.parse(r(n,"utf-8"))}catch{}const o=process.env.LINEMAN_API_TOKEN??t(e,"apiToken"),s=process.env.LINEMAN_DATA_API_URL??t(e,"dataApiUrl")??process.env.LINEMAN_SERVER_URL??t(e,"serverUrl"),p=process.env.LINEMAN_DATA_STREAM_API_URL??t(e,"dataStreamApiUrl")??s,A=process.env.LINEMAN_CONTROL_API_URL??t(e,"controlApiUrl")??process.env.LINEMAN_SERVER_URL??t(e,"serverUrl");return s&&o?{serverUrl:t(e,"serverUrl")??s,dataApiUrl:s,dataStreamApiUrl:p,controlApiUrl:A??s,apiToken:o}:null}

package/hooks/lineman-call.mjs

@@ -1 +1 @@
-import{loadLinemanConfig as t}from"./core/lineman-config.mjs";import{MCP_SERVER_NAME as n,MCP_TOOL_NAME as e,MCP_TOOL_PREFIX as o}from"./core/tool-naming.mjs";function r(){return t()}export function loadHookConfig(){return r()}export function isEnabled(){return"false"!==process.env.LINEMAN_ENABLED}export async function callLineman(t,n,e={},o={}){const a=r();if(!a)return null;const i=o.timeoutMs??3e4;let l,s;try{l=await fetch(`${a.serverUrl}/lineman/execute`,{method:"POST",headers:{"Content-Type":"application/json",Authorization:`Bearer ${a.apiToken}`},body:JSON.stringify({task_type:t,content:n,params:e}),signal:AbortSignal.timeout(i)})}catch{return null}if(!l.ok)return null;try{s=await l.json()}catch{return null}return"success"!==s?.metadata?.status?null:s.shaped_result??null}export function loadHooksConfig(){return{toolPrefix:o,toolName:e,serverName:n}}
+import{loadLinemanConfig as t}from"./core/lineman-config.mjs";import{MCP_SERVER_NAME as n,MCP_TOOL_NAME as e,MCP_TOOL_PREFIX as o}from"./core/tool-naming.mjs";function r(){return t()}export function loadHookConfig(){return r()}export function isEnabled(){return"false"!==process.env.LINEMAN_ENABLED}export async function callLineman(t,n,e={},o={}){const a=r();if(!a)return null;const i=o.timeoutMs??3e4;let l,u;try{l=await fetch(`${a.dataApiUrl}/lineman/execute`,{method:"POST",headers:{"Content-Type":"application/json",Authorization:`Bearer ${a.apiToken}`},body:JSON.stringify({task_type:t,content:n,params:e}),signal:AbortSignal.timeout(i)})}catch{return null}if(!l.ok)return null;try{u=await l.json()}catch{return null}return"success"!==u?.metadata?.status?null:u.shaped_result??null}export function loadHooksConfig(){return{toolPrefix:o,toolName:e,serverName:n}}

package/package.json

@@ -1,7 +1,26 @@
 {
   "name": "@lineman-io/mcp",
-  "version": "2.3.0",
+  "version": "2.4.2",
   "description": "Lineman MCP server — AI-powered code intelligence for Claude Code",
+  "license": "UNLICENSED",
+  "homepage": "https://lineman.io",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/lineman-io/lineman-mono",
+    "directory": "apps/lineman/mcp"
+  },
+  "bugs": "https://github.com/lineman-io/lineman-mono/issues",
+  "author": {
+    "name": "Lineman",
+    "url": "https://lineman.io"
+  },
+  "keywords": [
+    "mcp",
+    "claude-code",
+    "context-window",
+    "secondary-llm",
+    "token-saving"
+  ],
   "type": "module",
   "bin": {
     "lineman-mcp": "./dist/main.js"
@@ -20,7 +39,7 @@
     "zod": "^3.25.76"
   },
   "publishConfig": {
-    "access": "restricted",
+    "access": "public",
     "registry": "https://registry.npmjs.org/"
   },
   "engines": {

package/skills/telemetry/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: telemetry
+description: "View or change Lineman's telemetry consent — show what we send to Sentry and let the user opt out. Use when the user types '/lineman:telemetry', asks to 'turn telemetry on/off', 'disable analytics', 'opt out of telemetry', 'stop sending data to lineman', or asks 'what does lineman send to sentry'."
+user-invocable: true
+---
+
+# Lineman telemetry
+
+Show the user what Lineman sends to Sentry, and let them flip their consent. The actual mechanics are in the `telemetry` MCP tool — this skill is the model-facing wrapper that interprets the user's intent (`on` / `off` / "what do you send?") and dispatches accordingly.
+
+## How telemetry works
+
+Lineman MCP sends a small, anonymous stream of operational telemetry to Sentry so we can detect outages, fix bugs, and measure activation. We **never** send raw prompts, source code, file contents, or environment variable values.
+
+What we send (per LIN-523):
+
+- A stable per-machine UUID (`lineman_install_id`).
+- After authentication, the user's Lineman user id from the signed claim.
+- Tool-call telemetry: tool name, task type, latency, byte counts, savings estimates, error class.
+- Activation events: `mcp.first_run`, `mcp.auth_link_clicked`, `mcp.auth_completed`, `mcp.upgraded`.
+- OS, Node version, MCP version, runtime host (`claude-code` / `aider` / `continue` / `unknown`).
+
+What we strip before send:
+
+- All absolute file paths are rewritten — `/Users/<you>/...` and `/home/<you>/...` are replaced with `~`.
+- Stack-frame variables named `prompt`, `content`, `code`, `summary`, `messages`, `body`, `input`, or anything matching `KEY|TOKEN|SECRET|PASSWORD|API|AUTH|CREDENTIAL` are blanked.
+- HTTP request bodies are blanked wholesale.
+
+## Resolution order
+
+The MCP server resolves the on/off state in this order at boot (first match wins):
+
+1. `LINEMAN_TELEMETRY` env var — beats everything. `0`/`off`/`false`/`no` disable; `1`/`on`/`true`/`yes` enable.
+2. `~/.goodex/lineman.json::telemetryEnabled` — set by this skill (this file is what `/lineman:telemetry [on|off]` writes).
+3. Default: enabled.
+
+Setting the value via this skill won't override an active env var — surface that to the user so they're not confused if they think they flipped it but Sentry is still running.
+
+## Phase 1 — read
+
+If the user asks "what does lineman send to sentry?" or just types `/lineman:telemetry` without args, call `mcp__plugin_lineman_core__telemetry` with `{}` and show the response — it's a small JSON envelope with `enabled`, `source`, `envOverride`, and a `message` you can quote verbatim to the user.
+
+Then summarise the "What we send / What we strip" lists above so they can make an informed decision.
+
+## Phase 2 — flip
+
+When the user says "turn telemetry off" / "disable analytics" / similar, call `mcp__plugin_lineman_core__telemetry` with `{ enabled: false }`. When they say "turn it back on" / "enable telemetry", pass `{ enabled: true }`.
+
+After the call, read the response's `source` field:
+
+- `source: "config"` and matching `enabled` — the change took effect; tell the user to **restart their Claude Code session** for the next MCP launch to pick it up.
+- `source: "env"` — the env var is overriding the file setting; surface the `envOverride` value and tell the user they need to unset `LINEMAN_TELEMETRY` in their shell before the per-install setting will be honoured.
+
+## Edge cases
+
+- If the user pastes `/lineman:telemetry` without saying on or off and they previously had it off, ask "do you want to re-enable it?" rather than assuming.
+- If the call returns `isError: true`, the message will name the persistence failure (read-only HOME, etc.). Show the message and suggest the env var workaround as a fallback.
+- Don't argue with the user. If they want telemetry off, set it off. We have a documented opt-out for a reason.