# Give your agent access to Ren

import { Steps } from "@astrojs/starlight/components"
import Prereqs from "@docs/Prereqs.astro"

Ren is one backend with many ways in. In this tutorial you'll connect Ren to the coding agent you already use (for example, Claude Code), run Ren from inside it, and deploy your agent stack so it's reachable from every client: coding agents, MCPs, and the SDK.

<Prereqs>- A Ren account - A supported coding agent installed locally (such as Claude Code)</Prereqs>

## 1. Run Ren from your coding agent

Install the Ren plugin into your coding agent so it can pair the [Ren CLI](/docs/developers/cli/) and call Ren on your behalf.

<Steps>

1. Install the Ren plugin for your coding agent.
2. Pair it with your account. The plugin runs `ren init` and signs you in.
3. Confirm the connection:

   ```bash
   ren whoami
   ```

</Steps>

Your coding agent can now create sessions, run agents, and manage resources on Ren directly from your editor.

## 2. Deploy your agent stack to Ren

Define your agents, skills, and MCPs as code, then deploy them to Ren so they run on managed compute instead of your laptop.

<Steps>

1. From your coding agent, create an [agent](/docs/deep-dives/concepts/agents/agents/) and publish a version with its system prompt and model.
2. Attach [skills](/docs/deep-dives/concepts/agents/skills/) and [MCP servers](/docs/deep-dives/concepts/agents/mcps/) the agent needs.
3. Deploy the stack to a [project](/docs/deep-dives/concepts/compute/projects/) on your pod.

</Steps>

Once deployed, the stack lives on Ren: versioned, observable, and shareable across your org.

## 3. Reach it from every client

Because the stack runs on Ren's backend, the same agents are reachable from any entry point:

| Client         | How it connects                                                          |
| -------------- | ------------------------------------------------------------------------ |
| Coding agents  | Through the Ren plugin and CLI, from inside your editor                  |
| MCPs           | The Ren MCP tools (such as `session.create`) expose your agents to tools |
| TypeScript SDK | The [TypeScript SDK](/docs/developers/typescript-client/) wraps the API  |
| CLI / API      | The [Ren CLI](/docs/developers/cli/) and REST API drive everything       |

## What you built

You connected your coding agent to Ren, deployed an agent stack to managed compute, and made it reachable from every Ren client.

## Next steps

- Automate runs with [Schedule tasks](/docs/guides/automate/schedule-cron-trigger/) or [Trigger from your code](/docs/guides/automate/trigger-session-via-api/).
- Share what you built by [publishing to the registry](/docs/guides/share/publish-to-registry/).