Connect Codex desktop
SupportedThe bundled integration path is tested against RateLoop's own contracts; the pinned-client release smoke test is still outstanding.
Primary path only when RateLoop Workspace is already available in Codex's native inventory; no public plugin marketplace or repository install source is released. If the host installs that inventory entry, it loads in exactly one new Codex task with one still-unclaimed message paste. An already-loaded plugin continues in the same task after OAuth. If Codex offers no native plugin action, report the host blocker. Stale authorization recovery uses host-presented plugin OAuth followed by one fresh task with one new targeted reconnect message; standalone MCP authentication is not the plugin's OAuth state.
What to expect
- Use RateLoop Workspace only when Codex already offers it
- If Codex installs it, start one new task
- Approve any host trust or RateLoop OAuth prompt, then Continue in the same task
Connect your workspace
Copy your message from Connections and paste it into this app. It contains a private, single-use link. Keep the complete message private.
Example connection message
This example shows the instructions your agent receives. Its placeholder link cannot connect a workspace.
[@RateLoop Workspace](plugin://rateloop-workspace@rateloop) Use $rateloop-workspace-connection to connect to my RateLoop workspace with the private link below. If no RateLoop tools are available, stop and tell me to add RateLoop first. Don't open, repeat or share the link. It works once. Once connected, use $rateloop-human-review-loop when the workspace's review policy requires it.
/connect/aci_...#...Host-native setup
No verified install command is available for this app. Follow its setup steps above.
Check and recover
The connection is ready only after rateloop_connect_workspace or rateloop_verify_connection verifies it. If tools are missing, check the app's server setup and policy. After access expires or is revoked, complete the app's OAuth prompt, then create a targeted reconnect message in Connections (or a new message if the agent was deleted). Never reuse a claimed link. Recovery guide.
Delivery controls remain advisory; your workflow decides when to send an output.