feat: Per-host agent uniqueness and drag-and-drop tree management #49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When sending messages to agents on remote hosts, use the alias in the 'to' field instead of the UUID. Remote hosts can resolve aliases locally but don't know about UUIDs from other hosts. - For remote hosts: use alias (remote host resolves it locally) - For local hosts: continue using agent ID (more reliable) Fixes: "Unknown recipient: <uuid>" error when sending cross-host messages Co-Authored-By: Claude Opus 4.5 <[email protected]>
In a mesh network, "local" is meaningless. This refactor replaces the broken relative concept with absolute hostname-based identity. Changes: - Add isSelf(hostId) for self-detection instead of type checks - Add getSelfHostId() returning os.hostname() - Add getSelfHost() and getPeerHosts() replacing getLocalHost/getRemoteHosts - Auto-migrate legacy id:'local' configs to actual hostname - Replace all 'type === local' checks with isSelf() calls - Remove type:'remote' assignments (type field deprecated) - Client-side uses isLocalhostUrl() since browser can't use os.hostname() Key files: - lib/hosts-config.ts: Core identity functions and migration - lib/messageQueue.ts: Use isSelf() for routing decisions - lib/tmux-discovery.ts: Use isSelf() for session discovery - app/api/hosts/*: Updated peer registration and exchange Backward compat: Deprecated getLocalHost() and getRemoteHosts() kept as aliases. Legacy 'local' ID auto-migrates on config load. Co-Authored-By: Claude Opus 4.5 <[email protected]>
Agent Identity Improvements: - Agent names now unique per-host (like email: auth@host1 ≠ auth@host2) - getAgentByName() accepts optional hostId parameter - Added getAgentByNameAnyHost() for global searches - resolveAlias() supports name@host format for explicit targeting - createAgent/updateAgent uniqueness checks scoped to host Drag-and-Drop Tree Management: - Agents can be dragged between folders in the sidebar - Drop targets on Level 1 and Level 2 folder headers - Visual feedback with ring highlight during drag - API call updates agent tags on drop - Moving agents doesn't change their identity (ID, name) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
auth@host1≠auth@host2)name@hostformat support for explicit agent targetingTest plan
name@hostformat in messaging🤖 Generated with Claude Code