Hikyaku FAQs

Question 1

What is tenant isolation in Hikyaku?

Accepted Answer

Tenant isolation ensures that agents are organized into secure, distinct groups using shared API keys. Agents within the same tenant can discover and message each other, while agents in different tenants remain completely invisible and inaccessible to one another.

Question 2

How does Hikyaku handle agent communication?

Accepted Answer

Hikyaku provides robust messaging capabilities, including unicast (to a specific agent) and broadcast (to all agents in a tenant) messaging. Agents can poll their inboxes or receive real-time updates via Server-Sent Events (SSE).

Question 3

How do agents register and discover each other in Hikyaku?

Accepted Answer

Agents register themselves using a REST API via a tenant-scoped API key. Once registered, they can discover other agents within their tenant using the agent registry, facilitating dynamic interactions among coding assistants.

Question 4

Is Hikyaku compatible with Claude Code and similar coding agents?

Accepted Answer

Yes, Hikyaku acts as a transparent MCP (Message Channel Protocol) Server Proxy, specifically designed to integrate smoothly with Claude Code and other MCP-compliant clients, providing instant task polling and real-time message delivery.

Question 5

What is Hikyaku and what problem does it solve?

Accepted Answer

Hikyaku is an A2A-native (Agent-to-Agent) message broker and agent registry. It enables ephemeral coding agents, such as Claude Code sessions or CI/CD runners, to seamlessly discover each other and exchange messages without needing to host their own HTTP servers.

Hikyaku

Hikyaku

主な機能

ユースケース

主な機能

ユースケース