Skip to content

fix: handle UUID identities in instance_not_found_error_for#30

Merged
aannoo merged 1 commit intoaannoo:mainfrom
toller892:fix/uuid-identity-error
Apr 28, 2026
Merged

fix: handle UUID identities in instance_not_found_error_for#30
aannoo merged 1 commit intoaannoo:mainfrom
toller892:fix/uuid-identity-error

Conversation

@toller892
Copy link
Copy Markdown
Contributor

Sub-agents using UUID-based agent IDs (36 chars with hyphens) were getting incorrect hcom start --as recovery advice instead of the 'session may have ended' message.

Problem

instance_not_found_error_for() checks looks_like_agent_id() (7-char hex) but not looks_like_uuid() (36-char UUID). When a sub-agent with a UUID identity loses its session, the error message incorrectly suggests hcom start --as <uuid> — which would rebind the parent's identity.

Fix

Add looks_like_uuid(name) check alongside the existing looks_like_agent_id(name) check.

Related

Fixes #29

Sub-agents using UUID-based agent IDs (36 chars with hyphens)
were getting incorrect 'hcom start --as' recovery advice instead
of the 'session may have ended' message.

Add looks_like_uuid() check alongside the existing
looks_like_agent_id() check (7-char hex).

Fixes aannoo#29
@aannoo
Copy link
Copy Markdown
Owner

aannoo commented Apr 28, 2026

thanks

@aannoo aannoo merged commit 45e472c into aannoo:main Apr 28, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

instance_not_found_error_for doesn't handle UUID identities (incorrect --as advice for sub-agents)

2 participants