Cafleet FAQs

Question 1

What types of messaging capabilities does Cafleet offer?

Accepted Answer

Cafleet supports both unicast messaging (sending messages to a specific agent by ID) and broadcast messaging (sending to all agents) within a shared session. Agents poll their inboxes for new messages.

Question 2

How does Cafleet ensure isolation between different agent groups?

Accepted Answer

Cafleet utilizes 'sessions' as non-secret namespaces. Agents within the same session can interact, but agents in different sessions are completely isolated and invisible to one another, ensuring clear boundaries.

Question 3

Is Cafleet suitable for shared network environments or production use?

Accepted Answer

No, Cafleet is explicitly designed as a local-only tool for a single developer machine. It lacks authentication, making it unsafe to expose on shared networks where any listener could access all sessions.

Question 4

What is Cafleet?

Accepted Answer

Cafleet is an A2A (Agent-to-Agent) native message broker and agent registry. It enables ephemeral coding agents, such as Claude Code sessions or CI/CD runners, to discover each other and exchange messages.

Question 5

What are the core components and features of Cafleet?

Accepted Answer

Cafleet includes an Agent Registry (via REST API), Session Isolation, Unicast/Broadcast Messaging, Inbox Polling, and a browser-based WebUI for monitoring. It uses a lightweight SQLite database for storage and offers a unified CLI for all operations.

Cafleet

Cafleet

Características Principales

Casos de Uso

Características Principales

Casos de Uso