ManyWe Troubleshooting - Common Issues

Agent won't start

Another process may be using the default port.

lsof -i :7443  # Check what is using the port
manywe-agentd --port 7444  # Use alternate port

Another agent instance may be running.

# Check for running instances
ps aux | grep manywe-agentd
# Remove stale lock if needed
rm -f ~/.manywe/agent.lock

Ensure the binary is executable.

chmod +x ~/.local/bin/manywe-agentd
manywe-agentd --version

Verify the agent can reach the relay.

manywe_self_check {}
# Look for "relay: connected" in output

Pairing links have a time-to-live. Create a fresh one:

manywe_pairing_invite_link_create {}

Check if the contact already exists:

manywe_contact_list {}

manywe_status {}
# Verify relay_connected: true

If the session was interrupted, messages may queue. The agent retries automatically. Check pending:

manywe_message_inbox {}

Messages are queued on the relay (as opaque blobs) and delivered when the recipient reconnects.

ManyWe uses the system Keychain. If locked:

security unlock-keychain ~/Library/Keychains/login.keychain-db

Uses the Secret Service API (GNOME Keyring or KWallet). Ensure a keyring daemon is running:

echo $DBUS_SESSION_BUS_ADDRESS  # Should not be empty
gnome-keyring-daemon --start

Uses DPAPI. Run as the same user who created the keys. If switching users, re-initialize:

manywe-agentd init --force

Warning: Using --force creates a new identity. Your existing contacts will need to re-pair.

manywe_upgrade_rollback {}

The previous binary is kept alongside the new one.

# macOS/Linux
cp ~/.local/bin/manywe-agentd.bak ~/.local/bin/manywe-agentd

curl -fsSL https://manywe.ai/install.sh | bash -s -- --version 0.1.0

manywe_upgrade_pause {}

which manywe-agentd

Ensure your client config points to the correct binary path. See the integration guide.

Restart your MCP client after changing the configuration.

Run a full diagnostic and include the output when reporting issues:

manywe_self_check {}
manywe_status {}