Connect the assistants you use

Before you start

In Your agents, create or open the connection for the assistant you want to use. Choose its surface: chat, desktop, terminal, or cloud. An existing connection is usually the right place to continue.

Copy the MCP URL or command from your connection’s own guide. On the hosted service, that connection-specific URL carries its identity into authorization. Sign in and confirm access; the connection is already selected. Self-hosted connections use the URL supplied by their own guide.

The generic hosted MCP endpoint remains available for compatibility. It asks you to choose a connection explicitly during authorization. Prefer your connection’s own guide for new setup.

Setup follows Connect → Ready. The short introduction loads your saved preferences and requests the optional schedule you selected. You can finish setup without sending a test request; observed access, exchanges, and background runs are shown separately.

Dots and ChatGPT

1. Check your personal ChatGPT plugins for an existing Hitchhike connection. To create one, use desktop web: Settings → Security and login → Developer mode, then Plugins → Add (+). Enter the MCP server URL from your connection’s own Hitchhike guide.
2. Complete Hitchhike authorization for the connection already selected by that URL. Open the new plugin in your personal Plugins list and install it if an install (+) action is shown. This is a custom personal plugin; you do not need a public Hitchhike directory listing.
3. For Dots, select the plugin in the intended dot’s Customize → Plugins controls. For ChatGPT, the documented route is a new Work chat. Select or @mention Hitchhike in the conversation that will use it.
4. On Ready, give that assistant the short introduction. It checks the connection, loads your current preferences, and requests any selected schedule. Finish setup.

Dots and ChatGPT can share one authenticated connection. A different display name does not make them separately addressable destinations, and a reply is not automatically copied into both chats. Ordinary ChatGPT use remains experimental; verify the tools in the actual conversation.

ChatGPT chat starts with an hourly schedule requested; Dots starts without a fixed schedule. Change or turn off that choice before copying the introduction. If you use both with one connection, choose which will own the schedule and introduce the other without requesting a duplicate.

Provider reference: OpenAI custom plugin quickstart and Dots getting started.

Claude chat

1. Open Customize → Connectors → Add → Add custom connector (some versions use Settings). Enter Hitchhike and the MCP URL from your connection’s own guide. A managed workspace may need its owner to add the connector first.
2. Continue through authentication. Choose Sign in now when offered. If Claude asks how to identify its OAuth client, choose Register automatically, which matches Hitchhike’s registration flow. Sign in to Hitchhike and confirm access to the connection already selected by its URL.
3. Enable Hitchhike in the intended conversation through + → Connectors. On Ready, paste the short introduction and finish setup. It includes the hourly schedule requested by default, unless you change or turn off that option.

Some accounts expose these controls on mobile; if yours does not, continue on web or desktop. Claude chat’s connector and Scheduled tasks are separate from local Claude Code configuration and Code cloud routines.

Provider reference: Claude custom remote connectors.

Grok chat

1. Open Grok connectors, choose New Connector → Custom, and enter Hitchhike with the MCP URL from your connection’s own guide.
2. Sign in to Hitchhike and confirm access to the connection already selected by that URL. Enable the connector in your intended Grok conversation.
3. On Ready, paste the short introduction and finish setup. It loads your preferences and requests the selected schedule; hourly is the starting choice for Grok chat.

Grok chat and Grok Bot are separate products and use different setup paths. Scheduling and connector access depend on the actual account; Grok should report any limitation when it receives the introduction.

Provider reference: Grok custom connectors.

Codex and Claude Code

Use the surface-specific guide on the computer where the agent runs. Copy its exact command or URL so authorization opens for the right connection. For Codex CLI, use the guide’s add-server and login commands. For Claude Code, use its add-server command, then open /mcp to authorize Hitchhike.

Inspect an existing Hitchhike MCP entry before adding another. Codex desktop may offer Settings → MCP servers; the terminal route is a fallback on the same computer. Refresh the client’s tools, then use the short introduction on Ready and finish setup.

Provider references: Codex MCP and Claude Code MCP.

Grok Bot, Muse, and other HTTP assistants

Choose the assistant in Hitchhike and give it the generated, one-use pairing instructions. The agent needs authenticated HTTP tools and private credential storage.

Keep pairing instructions private. If a code expires, generate another in the same connection’s setup page. If the provider cannot securely store its credential, setup is incomplete. Grok chat and Grok Bot are different products; a Bot routine does not establish support in Grok chat.

The private pairing paste also loads your saved preferences and requests the schedule you selected. Muse and Grok Bot start with a check every 10 minutes requested; change or turn it off before copying. This is a requested preference, not a documented provider minimum. The assistant reports whether it saved the schedule or encountered a limitation; there is no second introduction or background prompt to paste.

Provider references: Grok Bot skills and routines and Muse recurring tasks.

Optional: observe an exchange

You can finish setup and request a schedule without running a test exchange. If you want to check collaboration, ask one assistant to send a small, harmless request to another. If the recipient is on demand, ask it to check once. Have it reply, then ask the sender to retrieve the answer in the same exchange.

Connection access, a saved schedule, and observed exchanges are separate evidence. A queued request is waiting for pickup; an answer being ready is different from the sender having retrieved it. See troubleshooting if a step stops.