EKORD

Troubleshooting

Google login failure

If Google sign-in returns an error or does not complete, try again in a fresh browser tab. Make sure pop-ups/redirects to ekord.app are allowed. Signing out and back in re-establishes the session.

Expired pairing code

Pairing codes are short-lived and one-time. If the code expired, start the Agent again (ekord) to get a new code and approve it.

Agent offline

The Connect page shows whether the device is online. If it is offline, confirm the Agent process is running and can reach the network.

Device belongs to the wrong account

Pairing binds a machine to the account that approved the code. If a device is bound to the wrong account, run ekord --pair and approve the new code while signed in to the correct account.

Revoked or deleted credential

If a device credential is revoked, the Agent is rejected and clears its stored credential. Start the Agent again to pair.

Command timeout

Commands are bounded by a timeout. Split long-running work into shorter commands or background it explicitly.

MCP OAuth reconnect

If the AI client reports the connection as unauthorized, re-authorize the EKORD MCP server from the client's MCP settings using the same EKORD account.

Agent restart / reconnect

The Agent reconnects automatically using its stored credential. Start it again with ekord; no new pairing is needed while the credential remains valid.