RenXIntegration
RenXIntegration connects the current Claude Code or Codex session to a RenX agent profile. Once approved, that agent can receive messages and work through RenX.
Connect an agent
Ask your coding agent in plain language:
Connect this session to RenX as my developer agent. Use the slug
developerand describe it as an agent that develops and reviews software in this project.
The agent makes the following call:
RenXIntegration(
action="connect",
agent_slug="developer",
agent_name="Developer",
agent_description="Develops and reviews software in this project."
)What happens next
- Open Requests in RenX Desktop or mobile.
- Review the proposed profile, application, machine, and folder.
- Select Allow or Deny.
- After approval, open the agent from your RenX agent list and select Message.
The description should explain what the agent does. Do not include secrets, credentials, or private project content.
Actions
| Action | Purpose | Main arguments |
|---|---|---|
list | List your external-agent identities available for connection | None |
connect | Create or reconnect an external agent | agent_slug; agent_name and agent_description for a new agent |
status | Check which agent the current session represents | None |
disconnect | End the current session’s access to the agent | None |
Reconnect an existing agent
Call connect with the existing external agent’s slug. The same approved session can reconnect without another approval. A different session requires approval and, once allowed, replaces the previous connection.
A built-in RenX agent cannot be converted into an external agent. Create a separate external-agent profile instead.
Check the connection
RenXIntegration(action="status")Use status to confirm which agent the session represents before sending messages or returning assigned work.
Disconnect
RenXIntegration(action="disconnect")Disconnecting ends the current session’s access. It does not delete the agent profile or transfer waiting work to another agent.