troxy-cli 1.7.3 → 1.7.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "troxy-cli",
-  "version": "1.7.3",
+  "version": "1.7.4",
   "description": "AI payment control — protect your agent's payments with policies",
   "type": "module",
   "bin": {

package/src/api.js

@@ -58,7 +58,7 @@ export const api = {
   waitApprovalStatus: (token) => request('GET', `/approvals/${encodeURIComponent(token)}/wait`),
 
   // MCP heartbeat (agent API key)
-  mcpHeartbeat: (apiKey, agentName) => request('POST', '/mcp/heartbeat', { apiKey, body: agentName ? { agent_name: agentName } : undefined }),
+  mcpHeartbeat: (apiKey, agentName, force) => request('POST', '/mcp/heartbeat', { apiKey, body: agentName ? { agent_name: agentName, force_name: !!force } : undefined }),
 
   // MCP status (agent API key — no login needed)
   mcpStatus:  (apiKey) => request('GET', '/mcp/status', { apiKey }),

package/src/daemon.js

@@ -19,14 +19,17 @@ export async function runDaemon() {
 
   const { apiKey, agentName } = cfg;
 
-  const beat = () =>
-    api.mcpHeartbeat(apiKey, agentName)
+  // `force` pushes the config name as the authoritative display name. We only
+  // do this on the FIRST beat after (re)start, so a `troxy restart` overrides
+  // the dashboard, while regular beats never clobber a dashboard rename.
+  const beat = (force) =>
+    api.mcpHeartbeat(apiKey, agentName, force)
       .then(() => process.stderr.write(`[troxy-daemon] heartbeat ok\n`))
       .catch(err => process.stderr.write(`[troxy-daemon] heartbeat failed: ${err.message}\n`));
 
   process.stderr.write(`[troxy-daemon] starting (agent: ${agentName || 'unnamed'})\n`);
-  await beat();
-  setInterval(beat, INTERVAL_MS);
+  await beat(true);                       // startup beat: config name wins
+  setInterval(() => beat(false), INTERVAL_MS);  // regular beats: don't touch name
 
   // Keep process alive indefinitely
   process.stdin.resume();