* feat: restore pipe IPC, LAN pipes, monitor tool, and PR-package features Core IPC system (UDS_INBOX): - PipeServer/PipeClient with UDS + TCP dual transport, NDJSON protocol - PipeRegistry: machineId-based role assignment, file locking - Master/slave attach, prompt relay, permission forwarding - Heartbeat lifecycle with parallel isPipeAlive probes - Commands: /pipes, /attach, /detach, /send, /claim-main, /pipe-status LAN Pipes (LAN_PIPES): - UDP multicast beacon (224.0.71.67:7101) for zero-config LAN discovery - PipeServer TCP listener, PipeClient TCP connect mode - Heartbeat auto-attaches LAN peers via TCP - Cross-machine attach allowed regardless of role - /pipes shows [LAN] peers with role + hostname/IP - SendMessageTool supports tcp: scheme with user consent Architecture — extracted hooks from REPL.tsx (~830 lines → ~20 lines): - usePipeIpc: lifecycle (bootstrap, handlers, heartbeat, cleanup) - usePipeRelay: slave→master message relay via module singleton - usePipePermissionForward: permission request/cancel forwarding - usePipeRouter: selected pipe input routing with role+IP labels - Shared ndjsonFramer.ts replaces 3 duplicate NDJSON parsers Key fixes applied during development: - Multicast binds to correct LAN interface (not WSL/Docker) - Beacon ref stored as module singleton (not Zustand state mutation) - Heartbeat preserves LAN peers in discoveredPipes and selectedPipes - Disconnect handler calls removeSlaveClient (fixes listener leak) - cleanupStaleEntries probes without lock, writes briefly under lock - getMachineId uses async execFile (not blocking execSync) - globalThis.__pipeSendToMaster replaced with setPipeRelay singleton - M key only toggles route mode when selector panel is expanded - User prompt displayed in message list on pipe broadcast - Broadcast notifications show [role] + hostname/IP for LAN peers Other restored features: - Monitor tool: /monitor command, MonitorTool, MonitorMcpTask lifecycle - Daemon supervisor and remoteControlServer command - Tools: SnipTool, SleepTool, ListPeersTool, SendUserFileTool, WebBrowserTool, WorkflowTool, and 10+ stub→implementation rewrites - Feature flags: UDS_INBOX, LAN_PIPES, MONITOR_TOOL, FORK_SUBAGENT, KAIROS, COORDINATOR_MODE, WORKFLOW_SCRIPTS, HISTORY_SNIP Tests: 2190 pass / 0 fail (15 new: lanBeacon 7, peerAddress 8) * fix: resolve merge conflicts and fix all tsc/test errors after main merge - Export ToolResultBlockParam from Tool.ts (14 tool files fixed) - Migrate ink imports from ../../ink.js to @anthropic/ink (7 files) - Fix toolUseID → toolUseId typo in monitor.ts and MonitorTool.tsx - Add fallback values for string|undefined type errors (8 locations) - Fix AppState type in assistant.ts, add NewInstallWizard stubs - Fix ParsedRepository.repo → .name in subscribe-pr.ts - Fix AgentId/string type mismatch in BackgroundTasksDialog.tsx - Fix PipeRelayFn return type in pipePermissionRelay.ts - Use PipeMessage type in usePipeRelay.ts - Fix lanBeacon.test.ts mock type assertions - Create missing MouseActionEvent class for ink package - Use ansi: color format instead of bare "green"/"red" - Resolve theme.permission access via getTheme() Result: 0 tsc errors, 2496 tests pass, 0 fail Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: 恢复 /poor 的说明 --------- Co-authored-by: unraid <local@unraid.local> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
34 lines
1.4 KiB
TypeScript
34 lines
1.4 KiB
TypeScript
/**
|
|
* Peer address parsing — kept separate from peerRegistry.ts so that
|
|
* SendMessageTool can import parseAddress without transitively loading
|
|
* the bridge (axios) and UDS (fs, net) modules at tool-enumeration time.
|
|
*/
|
|
|
|
/** Parse a URI-style address into scheme + target. */
|
|
export function parseAddress(to: string): {
|
|
scheme: 'uds' | 'bridge' | 'tcp' | 'other'
|
|
target: string
|
|
} {
|
|
if (to.startsWith('uds:')) return { scheme: 'uds', target: to.slice(4) }
|
|
if (to.startsWith('bridge:')) return { scheme: 'bridge', target: to.slice(7) }
|
|
if (to.startsWith('tcp:')) return { scheme: 'tcp', target: to.slice(4) }
|
|
// Legacy: old-code UDS senders emit bare socket paths in from=; route them
|
|
// through the UDS branch so replies aren't silently dropped into teammate
|
|
// routing. (No bare-session-ID fallback — bridge messaging is new enough
|
|
// that no old senders exist, and the prefix would hijack teammate names
|
|
// like session_manager.)
|
|
if (to.startsWith('/')) return { scheme: 'uds', target: to }
|
|
return { scheme: 'other', target: to }
|
|
}
|
|
|
|
/** Parse a tcp: target string into host and port. */
|
|
export function parseTcpTarget(
|
|
target: string,
|
|
): { host: string; port: number } | null {
|
|
const match = target.match(/^([^:]+):(\d+)$/)
|
|
if (!match) return null
|
|
const port = parseInt(match[2]!, 10)
|
|
if (port < 1 || port > 65535) return null
|
|
return { host: match[1]!, port }
|
|
}
|