LagrangeCloud Docs
Open the console
Quickstart

Quickstart

If you built an agent in Codex or Claude Code, the lagrange plugin deploys it from the folder you are working in. It reads the folder, uploads it with the keys it needs, and gives you an endpoint you can call.

You need Node.js 22 or later.

1. Install the plugin

Codex CLI:

codex plugin marketplace add https://github.com/TensorBlock/lagrange-plugins
codex plugin add lagrange@tensorblock

Codex app (if you have no codex command; the app picks the plugin up from the same ~/.codex folder):

npx -y @openai/codex plugin marketplace add https://github.com/TensorBlock/lagrange-plugins
npx -y @openai/codex plugin add lagrange@tensorblock

Claude Code:

claude plugin marketplace add https://github.com/TensorBlock/lagrange-plugins
claude plugin install lagrange@tensorblock

2. Ask it to deploy

Open Codex or Claude Code in your agent's folder and ask:

Deploy this agent to LagrangeCloud

In Claude Code you can also run /lagrange:deploy.

Claude Code · ~/acme/support-bot

/lagrange:deploy

  1. Signed in to LagrangeCloud in the browser
  2. Wrote lgr.yaml from CLAUDE.md, 2 skills and scripts/
  3. Kept the MCP servers linear and stripe
  4. Stored LINEAR_TOKEN and STRIPE_KEY as secrets, without printing them
  5. Deployed support-bot v1 on Claude Code
  6. Sent a test message: "Where is order 1057?" was answered

Live https://d3iwapvcygehqg.cloudfront.net/v1/invoke/ag_5d02c7a3b81e

The first time, a browser page opens for you to sign in and approve the device. Then the plugin:

  1. writes lgr.yaml from the folder (see lgr.yaml) and shows you what will be uploaded,
  2. asks which of your own MCP servers the agent uses,
  3. stores the keys those servers and scripts need as project secrets, reading them on your machine without printing them,
  4. deploys the agent and sends it a test message,
  5. if the agent is a recurring job, such as a daily review, asks when it should run and sets up a schedule,
  6. gives you the link to the agent in the console.

The agent runs on the same harness you use locally: Codex agents on Codex, Claude Code agents on Claude Code. To run it on Lagrange instead, ask for it: "Deploy this agent to LagrangeCloud on Lagrange". Lagrange needs your own ANTHROPIC_API_KEY as a project secret for now.

3. Try it and call it

The agent's page in the console has:

  • Playground: talk to the agent through its endpoint, with each reply's time, cost and run.
  • API: the endpoint, caller keys and request examples, including a chat widget to paste into a website.
  • Schedules: schedules and webhooks that start runs.
  • Setup: instructions, skills, MCP servers and secrets.

Create a caller key under API, then follow Call your agent.

Deploying again

After you change the folder, ask again to deploy. Each deploy is a new version on the same endpoint and keys, so callers get the change on their next message. See Versions and changes to try a version before callers get it.

What doesn't carry over

  • MCP servers that run on localhost, and MCP servers you signed in to through the browser in Codex or Claude Code. Add them on the agent's page under Setup → MCP servers and secrets, as a hosted URL with a token or as a command the sandbox runs.
  • Files that aren't listed under files: in lgr.yaml. Only listed files are uploaded.