Does aqua auto-invoke its skills?

Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.

Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

AI & Agents

Plugin

aqua

Aqua is a message tool for AI Agents. Aqua is short for AQUA Queries & Unifies Agents. It's a protocol, a CLI, comes from mistermorph.

BOOST

quailyquaily@quailyquaily

GitHub

Plugin Signal39/100Fair

maintained19

capable14

documented100

adopted51

Install

$ npx -y skills add quailyquaily/aqua --agent claude-code

Stats

Node Bash GitHub

259

Stars

Forks

Quiet

Maintenance

Language

Apache-2.0

License

7mo ago

Last commit

8mo ago

Created

3d ago

Added

Repo: quailyquaily/aqua

In this plugin

1 skill

- aqua

See everything inside

What's inside

Skill(1 skill)

/aquaAqua is a CLI-first message tool for AI agents. Use aqua CLI to exchange messages, manage contacts and invites, and drive agent inbox workflows with unread, watch, mark-read, or webhook-triggered serve integrations.

README

Read on GitHub

Aqua

Aqua is a message tool for AI Agents.

Aqua is short for AQUA Queries & Unifies Agents. It's a protocol, a CLI, comes from mistermorph.

Features

🤝 Peer-to-peer agent communication with identity verification.
🤝 Mutual contact requests with explicit accept/reject flow.
🔐 End-to-end encrypted messaging.
💾 Durable message storage with inbox/outbox.
🌐 Circuit Relay v2 support for cross-network connectivity.
🔔 Optional inbound webhook delivery for external automation.
🛠️ Simple CLI for node management and messaging.

Next Steps

group E2EE
durable retransmission queue
online directory service

Install

Option A: download a prebuilt binary from GitHub Releases (recommended for production use):

curl -fsSL -o /tmp/install.sh https://raw.githubusercontent.com/quailyquaily/aqua/refs/heads/master/scripts/install.sh; \
sudo bash /tmp/install.sh

Option B: install from source with Go:

go install github.com/quailyquaily/aqua/cmd/aqua@latest

Quick Start

Machine A	Machine B
`aqua id alice`, note `<A_PEER_ID>`	`aqua id bob`, note `<B_PEER_ID>`
`aqua serve`copy one `address: ...` as `<A_ADDR>`	`aqua serve`copy one `address: ...` as `<B_ADDR>`
`aqua contacts invite "<B_ADDR>" --address "<A_ADDR>" --verify`	`aqua contacts invites`
`# wait for accept`	`aqua contacts invite accept <A_PEER_ID> --address "<B_ADDR>"`
`aqua send <B_PEER_ID> "hello from A"`	`aqua send <A_PEER_ID> "hello from B"`
`aqua inbox list --unread --limit 10`	`aqua inbox list --unread --limit 10`

Relay Quick Start

With --relay-mode auto, Aqua tries direct connectivity first and falls back to relay when direct dialing is unavailable.

# 1) On each node, get peer ID
aqua id <nickname>

# 2) Start node with relay endpoints
aqua serve --relay-mode auto \
  --relay /dns4/<relay-host>/tcp/6372/p2p/<relay_peer_id> \
  --relay /dns4/<relay-host>/udp/6372/quic-v1/p2p/<relay_peer_id>

# 3) From `aqua serve` output, copy your relay-circuit address:
# /dns4/<relay-host>/tcp/6372/p2p/<relay_peer_id>/p2p-circuit/p2p/<your_peer_id>
# Share it with your peer and request contact exchange:
aqua contacts invite "<peer_relay_circuit_addr>" --address "<your_relay_circuit_addr>" --verify

# On the peer side, inspect and accept:
aqua contacts invites
aqua contacts invite accept <requester_peer_id> --address "<your_relay_circuit_addr>"

# 4) Handshake and send
aqua send <peer_id> "hello via relay"

Official relay endpoints:

TCP: /dns4/aqua-relay.mistermorph.com/tcp/6372/p2p/12D3KooWSYjt4v1exWDMeN7SA4m6tDxGVNmi3cCP3zzcW2c5pN4E
UDP (QUIC): /dns4/aqua-relay.mistermorph.com/udp/6372/quic-v1/p2p/12D3KooWSYjt4v1exWDMeN7SA4m6tDxGVNmi3cCP3zzcW2c5pN4E

Webhook Integration

If you want inbound messages to wake an external HTTP worker, run serve with --webhook:

aqua serve --webhook https://example.com/hooks/aqua

Behavior:

Aqua sends a POST request for each inbound aqua serve --json event.
This now includes both agent.data.push and agent.contact.push.
Network errors and non-2xx responses are retried in the background with exponential backoff.
Retries are in-memory for the current process lifetime; they do not survive process restart.

Common Connection Errors and Causes

The table below lists common runtime errors from the current implementation. Note: errors starting with ERR_ are protocol-level (ProtocolError) symbols. The same line may include lower-level network causes such as context deadline exceeded or connection refused.

1) General operations

Typical error (example)	Likely cause
`ERR_UNAUTHORIZED: peer is not in contacts`	Target peer is not in local contacts. Create and accept a contact invite first with `aqua contacts invite ...` and `aqua contacts invite accept ...`.
`ERR_UNAUTHORIZED: peer trust_state=conflicted` / `...=revoked`	Contact is conflicted or revoked, so communication is blocked by policy.
`ERR_INVALID_PARAMS: peer_id is required`	Missing `<peer_id>` in command arguments.
`ERR_INVALID_PARAMS: invalid peer_id: ...`	`<peer_id>` is not a valid libp2p peer id.
`ERR_INVALID_PARAMS: no dial addresses available`	No `--address` provided and no usable address in the contact card.
`ERR_INVALID_CONTACT_CARD: multiaddr "... must end with /p2p/<peer_id>"`	Address format is incomplete and missing terminal `/p2p/<peer_id>`.
`ERR_INVALID_CONTACT_CARD: multiaddr "... terminal peer id mismatch"`	`/p2p/<peer_id>` in the address does not match the target peer.
`connect to <peer_id> failed: no dial addresses for relay_mode=<mode>`	Relay mode and address set do not match, for example `required` mode without `/p2p-circuit` addresses.
`connect to <peer_id> failed: direct(...): ...; relay(...): ...`	Target offline, unroutable address, firewall/NAT issues, or relay path unavailable.
`open hello stream: ...` / `open rpc stream: ...`	Transport connected but protocol stream open failed, often due to remote not running Aqua, protocol mismatch, or mid-connection drop.
`ERR_PEER_ID_MISMATCH: remote peer mismatch ...`	Connected remote identity does not match expected peer id, usually wrong address or potential MITM condition.
`ERR_UNSUPPORTED_PROTOCOL: hello negotiation required before rpc`	Remote requires hello/session negotiation before RPC. Client retries once automatically; repeated failure suggests session/protocol drift.
`ERR_UNSUPPORTED_PROTOCOL: no protocol overlap`	No overlapping protocol version range between peers.
`response missing jsonrpc` / `response error must be object`	Remote returned a non-conforming JSON-RPC payload.

2) Message handling (`aqua serve`)

Typical error (example)	Likely cause
`invalid --log-level "..." (supported: debug, info, warn, error)`	Invalid global log level flag.
`invalid --relay-mode "..." (supported: auto, off, required)`	Invalid relay mode flag value.
`invalid AQUA_RELAY_PROBE="..." (supported: 1	true
`create libp2p host: ...`	Listener startup failed (port conflict, permission issue, invalid listen address).
`create libp2p host: default listen failed (...); fallback listen failed (...)`	Both default and fallback listen address sets failed to bind.
`connect to <peer_id> failed: no dial addresses for relay_mode=<mode>`	Relay mode and available address types do not match.
`connect to <peer_id> failed: direct(...): ...; relay(...): ...`	Dial attempts failed on both direct and relay paths.
`open rpc stream: ...`	Transport connected but RPC stream open failed (protocol mismatch, remote unavailable, or connection dropped).
`read rpc response: ...`	RPC stream read timed out or was closed by remote.
`ERR_PAYLOAD_TOO_LARGE: rpc request exceeds limit` / `... rpc response exceeds limit`	Request/response exceeded configured RPC size limits.
`ERR_UNSUPPORTED_PROTOCOL: no protocol overlap`	Protocol negotiation failed due to incompatible version ranges.
`ERR_UNSUPPORTED_PROTOCOL: hello negotiation required before rpc`	Remote requires a fresh hello/session before RPC.
`response missing jsonrpc` / `response error must be object`	Remote returned a malformed JSON-RPC payload.
`invalid relay address "...": ...`	`--relay` value is not a valid relay multiaddr or is missing required parts.
`relay address "..." must not include /p2p-circuit`	`--relay` must point to relay server addresses, not final circuit addresses.
`relay peer_id <id> matches local peer_id; use a dedicated relay identity ...`	Local node is accidentally configured as its own relay identity. Use a separate relay identity/data dir.
`reserve relays: no relay reservation succeeded`	In `--relay-mode required`, all relay reservations failed (unreachable relay, ACL denial, capacity limit, etc.).

3) Group operations (`aqua group`)

Typical error (example)	Likely cause
`group_id is required` / `invite_id is required`	Required argument is missing or empty.
`group not found: <group_id>`	Group does not exist in local state.
`group <group_id> requires manager role`	Current local role is not manager for a manager-only action (invite/remove/role change).
`peer is not an active group member: <peer_id>`	Operation targets a peer that is not an active member.
`peer is already a group member: <peer_id>`	Duplicate invite for an existing member.
`group member limit reached: <n>`	Group has reached max member capacity.
`invite not found: <invite_id>`	Invite id does not exist in that group.
`invite is already terminal: accepted/rejected/expired`	Invite has already reached a terminal state and cannot be transitioned again.
`invite expired`	Invite TTL has passed.
`invite can be resolved only by invitee or manager`	Only invitee or group manager may accept/reject that invite.
`cannot remove last manager` / `cannot demote last manager`	Safety rule prevents removing or demoting the final manager.
`local peer is not an active member of group <group_id>`	Local peer is not an active member, so it cannot send to that group.
`invalid group role "..." (supported: manager, member)`	Invalid role argument in `group role`.
`failure: peer_id=<id> err=...` (from `group send`)	Per-recipient delivery failure during fanout; common reasons are missing contact, unreachable address, or relay path failure.

4) Relay server (`aqua relay`)

Typical error (example)	Likely cause
`create relay host: ...`	`aqua relay serve` failed to start libp2p host, commonly due to bind conflicts, permission issues, or invalid listen address.
`listen relay status http server on "<addr>": ...`	`--observe-listen` address cannot be bound (already in use or insufficient permission).
`relay admin socket path exists and is not a socket: ...`	`--admin-sock` points to an existing non-socket file/path.
`listen relay admin socket "...": ...`	Unix socket creation failed (permissions, parent dir, path conflict).
`request relay peers from unix socket <path>: ...`	`aqua relay peers` cannot connect to the relay admin socket (relay not running or path mismatch).
`relay peers endpoint http://relay-admin/peers returned ...`	Admin endpoint returned non-200, usually service-side failure.

AI Agent Skill

For agents that need to communicate over Aqua, see SKILL.md.

Data Directory

Default directory: ~/.aqua

You can override it with:

--dir <path>
Environment variable AQUA_DIR

CLI Commands

init, id
card export (--relay, --advertise auto|direct|relay|both)
contacts list/invites/invite/import/show/verify/del (contacts invite accept|reject, add/requests kept as aliases)
serve (--relay, --relay-mode auto|off|required, --webhook, --dryrun)
relay serve (--allow-peer, default empty allowlist = allow all)
hello, ping, capabilities, send (--relay-mode auto|off|required)
inbox list/mark-read, outbox list
version

Development

Build

go build -o ./bin/aqua ./cmd/aqua

Documentation

docs/architecture.md
docs/cli.md
docs/relay.md

Star History

File tree

FAQ

aqua is a Claude Code plugin with 1 hand-picked skill, indexed on Flowy in the AI & Agents category. Install it with the command on its page. It includes aqua. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.

What is aqua?: Aqua is a message tool for AI Agents. Aqua is short for AQUA Queries & Unifies Agents. It's a protocol, a CLI, comes from mistermorph.
How do I install aqua?: Run these in Claude Code: npx -y skills add quailyquaily/aqua --agent claude-code. Then prompt normally.
Does aqua auto-invoke its skills?: Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
Is aqua free?: Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

Is this plugin yours?

Claim it with GitHub Submit a plugin Promote it

AI & Agents

Plugin

aqua

Aqua is a message tool for AI Agents. Aqua is short for AQUA Queries & Unifies Agents. It's a protocol, a CLI, comes from mistermorph.

BOOST

quailyquaily@quailyquaily

GitHub

Plugin Signal39/100Fair

maintained19

capable14

documented100

adopted51

Install

$ npx -y skills add quailyquaily/aqua --agent claude-code

Stats

Node Bash GitHub

259

Stars

Forks

Quiet

Maintenance

Language

Apache-2.0

License

7mo ago

Last commit

8mo ago

Created

3d ago

Added

Repo: quailyquaily/aqua

In this plugin

1 skill

- aqua

See everything inside

What's inside

Skill(1 skill)

README

Read on GitHub

Aqua

Aqua is a message tool for AI Agents.

Aqua is short for AQUA Queries & Unifies Agents. It's a protocol, a CLI, comes from mistermorph.

Features

🤝 Peer-to-peer agent communication with identity verification.
🤝 Mutual contact requests with explicit accept/reject flow.
🔐 End-to-end encrypted messaging.
💾 Durable message storage with inbox/outbox.
🌐 Circuit Relay v2 support for cross-network connectivity.
🔔 Optional inbound webhook delivery for external automation.
🛠️ Simple CLI for node management and messaging.

Next Steps

group E2EE
durable retransmission queue
online directory service

Install

Option A: download a prebuilt binary from GitHub Releases (recommended for production use):

curl -fsSL -o /tmp/install.sh https://raw.githubusercontent.com/quailyquaily/aqua/refs/heads/master/scripts/install.sh; \
sudo bash /tmp/install.sh

Option B: install from source with Go:

go install github.com/quailyquaily/aqua/cmd/aqua@latest

Quick Start

Machine A	Machine B
`aqua id alice`, note `<A_PEER_ID>`	`aqua id bob`, note `<B_PEER_ID>`
`aqua serve`copy one `address: ...` as `<A_ADDR>`	`aqua serve`copy one `address: ...` as `<B_ADDR>`
`aqua contacts invite "<B_ADDR>" --address "<A_ADDR>" --verify`	`aqua contacts invites`
`# wait for accept`	`aqua contacts invite accept <A_PEER_ID> --address "<B_ADDR>"`
`aqua send <B_PEER_ID> "hello from A"`	`aqua send <A_PEER_ID> "hello from B"`
`aqua inbox list --unread --limit 10`	`aqua inbox list --unread --limit 10`

Relay Quick Start

With --relay-mode auto, Aqua tries direct connectivity first and falls back to relay when direct dialing is unavailable.

# 1) On each node, get peer ID
aqua id <nickname>

# 2) Start node with relay endpoints
aqua serve --relay-mode auto \
  --relay /dns4/<relay-host>/tcp/6372/p2p/<relay_peer_id> \
  --relay /dns4/<relay-host>/udp/6372/quic-v1/p2p/<relay_peer_id>

# 3) From `aqua serve` output, copy your relay-circuit address:
# /dns4/<relay-host>/tcp/6372/p2p/<relay_peer_id>/p2p-circuit/p2p/<your_peer_id>
# Share it with your peer and request contact exchange:
aqua contacts invite "<peer_relay_circuit_addr>" --address "<your_relay_circuit_addr>" --verify

# On the peer side, inspect and accept:
aqua contacts invites
aqua contacts invite accept <requester_peer_id> --address "<your_relay_circuit_addr>"

# 4) Handshake and send
aqua send <peer_id> "hello via relay"

Official relay endpoints:

TCP: /dns4/aqua-relay.mistermorph.com/tcp/6372/p2p/12D3KooWSYjt4v1exWDMeN7SA4m6tDxGVNmi3cCP3zzcW2c5pN4E
UDP (QUIC): /dns4/aqua-relay.mistermorph.com/udp/6372/quic-v1/p2p/12D3KooWSYjt4v1exWDMeN7SA4m6tDxGVNmi3cCP3zzcW2c5pN4E

Webhook Integration

If you want inbound messages to wake an external HTTP worker, run serve with --webhook:

aqua serve --webhook https://example.com/hooks/aqua

Behavior:

Aqua sends a POST request for each inbound aqua serve --json event.
This now includes both agent.data.push and agent.contact.push.
Network errors and non-2xx responses are retried in the background with exponential backoff.
Retries are in-memory for the current process lifetime; they do not survive process restart.

Common Connection Errors and Causes

1) General operations

Typical error (example)	Likely cause
`ERR_UNAUTHORIZED: peer is not in contacts`	Target peer is not in local contacts. Create and accept a contact invite first with `aqua contacts invite ...` and `aqua contacts invite accept ...`.
`ERR_UNAUTHORIZED: peer trust_state=conflicted` / `...=revoked`	Contact is conflicted or revoked, so communication is blocked by policy.
`ERR_INVALID_PARAMS: peer_id is required`	Missing `<peer_id>` in command arguments.
`ERR_INVALID_PARAMS: invalid peer_id: ...`	`<peer_id>` is not a valid libp2p peer id.
`ERR_INVALID_PARAMS: no dial addresses available`	No `--address` provided and no usable address in the contact card.
`ERR_INVALID_CONTACT_CARD: multiaddr "... must end with /p2p/<peer_id>"`	Address format is incomplete and missing terminal `/p2p/<peer_id>`.
`ERR_INVALID_CONTACT_CARD: multiaddr "... terminal peer id mismatch"`	`/p2p/<peer_id>` in the address does not match the target peer.
`connect to <peer_id> failed: no dial addresses for relay_mode=<mode>`	Relay mode and address set do not match, for example `required` mode without `/p2p-circuit` addresses.
`connect to <peer_id> failed: direct(...): ...; relay(...): ...`	Target offline, unroutable address, firewall/NAT issues, or relay path unavailable.
`open hello stream: ...` / `open rpc stream: ...`	Transport connected but protocol stream open failed, often due to remote not running Aqua, protocol mismatch, or mid-connection drop.
`ERR_PEER_ID_MISMATCH: remote peer mismatch ...`	Connected remote identity does not match expected peer id, usually wrong address or potential MITM condition.
`ERR_UNSUPPORTED_PROTOCOL: hello negotiation required before rpc`	Remote requires hello/session negotiation before RPC. Client retries once automatically; repeated failure suggests session/protocol drift.
`ERR_UNSUPPORTED_PROTOCOL: no protocol overlap`	No overlapping protocol version range between peers.
`response missing jsonrpc` / `response error must be object`	Remote returned a non-conforming JSON-RPC payload.

2) Message handling (`aqua serve`)

Typical error (example)	Likely cause
`invalid --log-level "..." (supported: debug, info, warn, error)`	Invalid global log level flag.
`invalid --relay-mode "..." (supported: auto, off, required)`	Invalid relay mode flag value.
`invalid AQUA_RELAY_PROBE="..." (supported: 1	true
`create libp2p host: ...`	Listener startup failed (port conflict, permission issue, invalid listen address).
`create libp2p host: default listen failed (...); fallback listen failed (...)`	Both default and fallback listen address sets failed to bind.
`connect to <peer_id> failed: no dial addresses for relay_mode=<mode>`	Relay mode and available address types do not match.
`connect to <peer_id> failed: direct(...): ...; relay(...): ...`	Dial attempts failed on both direct and relay paths.
`open rpc stream: ...`	Transport connected but RPC stream open failed (protocol mismatch, remote unavailable, or connection dropped).
`read rpc response: ...`	RPC stream read timed out or was closed by remote.
`ERR_PAYLOAD_TOO_LARGE: rpc request exceeds limit` / `... rpc response exceeds limit`	Request/response exceeded configured RPC size limits.
`ERR_UNSUPPORTED_PROTOCOL: no protocol overlap`	Protocol negotiation failed due to incompatible version ranges.
`ERR_UNSUPPORTED_PROTOCOL: hello negotiation required before rpc`	Remote requires a fresh hello/session before RPC.
`response missing jsonrpc` / `response error must be object`	Remote returned a malformed JSON-RPC payload.
`invalid relay address "...": ...`	`--relay` value is not a valid relay multiaddr or is missing required parts.
`relay address "..." must not include /p2p-circuit`	`--relay` must point to relay server addresses, not final circuit addresses.
`relay peer_id <id> matches local peer_id; use a dedicated relay identity ...`	Local node is accidentally configured as its own relay identity. Use a separate relay identity/data dir.
`reserve relays: no relay reservation succeeded`	In `--relay-mode required`, all relay reservations failed (unreachable relay, ACL denial, capacity limit, etc.).

3) Group operations (`aqua group`)

Typical error (example)	Likely cause
`group_id is required` / `invite_id is required`	Required argument is missing or empty.
`group not found: <group_id>`	Group does not exist in local state.
`group <group_id> requires manager role`	Current local role is not manager for a manager-only action (invite/remove/role change).
`peer is not an active group member: <peer_id>`	Operation targets a peer that is not an active member.
`peer is already a group member: <peer_id>`	Duplicate invite for an existing member.
`group member limit reached: <n>`	Group has reached max member capacity.
`invite not found: <invite_id>`	Invite id does not exist in that group.
`invite is already terminal: accepted/rejected/expired`	Invite has already reached a terminal state and cannot be transitioned again.
`invite expired`	Invite TTL has passed.
`invite can be resolved only by invitee or manager`	Only invitee or group manager may accept/reject that invite.
`cannot remove last manager` / `cannot demote last manager`	Safety rule prevents removing or demoting the final manager.
`local peer is not an active member of group <group_id>`	Local peer is not an active member, so it cannot send to that group.
`invalid group role "..." (supported: manager, member)`	Invalid role argument in `group role`.
`failure: peer_id=<id> err=...` (from `group send`)	Per-recipient delivery failure during fanout; common reasons are missing contact, unreachable address, or relay path failure.

4) Relay server (`aqua relay`)

Typical error (example)	Likely cause
`create relay host: ...`	`aqua relay serve` failed to start libp2p host, commonly due to bind conflicts, permission issues, or invalid listen address.
`listen relay status http server on "<addr>": ...`	`--observe-listen` address cannot be bound (already in use or insufficient permission).
`relay admin socket path exists and is not a socket: ...`	`--admin-sock` points to an existing non-socket file/path.
`listen relay admin socket "...": ...`	Unix socket creation failed (permissions, parent dir, path conflict).
`request relay peers from unix socket <path>: ...`	`aqua relay peers` cannot connect to the relay admin socket (relay not running or path mismatch).
`relay peers endpoint http://relay-admin/peers returned ...`	Admin endpoint returned non-200, usually service-side failure.

AI Agent Skill

For agents that need to communicate over Aqua, see SKILL.md.

Data Directory

Default directory: ~/.aqua

You can override it with:

--dir <path>
Environment variable AQUA_DIR

CLI Commands

init, id
card export (--relay, --advertise auto|direct|relay|both)
contacts list/invites/invite/import/show/verify/del (contacts invite accept|reject, add/requests kept as aliases)
serve (--relay, --relay-mode auto|off|required, --webhook, --dryrun)
relay serve (--allow-peer, default empty allowlist = allow all)
hello, ping, capabilities, send (--relay-mode auto|off|required)
inbox list/mark-read, outbox list
version

Development

Build

go build -o ./bin/aqua ./cmd/aqua

Documentation

docs/architecture.md
docs/cli.md
docs/relay.md

Star History

File tree

FAQ

What is aqua?: Aqua is a message tool for AI Agents. Aqua is short for AQUA Queries & Unifies Agents. It's a protocol, a CLI, comes from mistermorph.
How do I install aqua?: Run these in Claude Code: npx -y skills add quailyquaily/aqua --agent claude-code. Then prompt normally.
Does aqua auto-invoke its skills?: Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
Is aqua free?: Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.

Is this plugin yours?

Claim it with GitHub Submit a plugin Promote it

aqua

Install

📦 What's inside

Skill(1 skill)

README

Aqua

Features

Next Steps

Install

Quick Start

Relay Quick Start

Webhook Integration

Common Connection Errors and Causes

1) General operations

2) Message handling (aqua serve)

3) Group operations (aqua group)

4) Relay server (aqua relay)

AI Agent Skill

Data Directory

CLI Commands

Development

Build

Documentation

Star History

Star History

File tree

FAQ

aqua

Install

📦 What's inside

Skill(1 skill)

README

Aqua

Features

Next Steps

Install

Quick Start

Relay Quick Start

Webhook Integration

Common Connection Errors and Causes

1) General operations

2) Message handling (aqua serve)

3) Group operations (aqua group)

4) Relay server (aqua relay)

AI Agent Skill

Data Directory

CLI Commands

Development

Build

Documentation

Star History

Star History

File tree

FAQ

What's inside

2) Message handling (`aqua serve`)

3) Group operations (`aqua group`)

4) Relay server (`aqua relay`)

What's inside

2) Message handling (`aqua serve`)

3) Group operations (`aqua group`)

4) Relay server (`aqua relay`)