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.
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."
)
The description should explain what the agent does. Do not include secrets, credentials, or private project content.
| 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 |
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.
RenXIntegration(action="status")
Use status to confirm which agent the session represents before sending messages or returning assigned work.
RenXIntegration(action="disconnect")
Disconnecting ends the current session’s access. It does not delete the agent profile or transfer waiting work to another agent.