Agents API

Pricing

The agent's model calls are billed at the selected model's rates, against your organization and tier, like any other LatentStack request. They appear in My Usage.

Try an example

• Run your first session: run a task in a sandbox, then have an agent change code in a repository.
• Review a pull request: check out a PR branch with read-only permissions and collect the review.
• Fix failing tests in CI: run an agent from a GitHub Actions job and upload its patch.
• Ask a human: stream an agent's work to a terminal and approve risky commands as they come up.

Core concepts

The Agents API is built around four concepts:

• Agent: the model, instructions and permissions the agent works with.
• Environment: where the agent works. Either an empty workspace, or up to six GitHub repositories on the branch, tag or commit you choose.
• Session: a durable instance of an agent. It works on tasks, responds to your input, and survives pauses.
• Events: everything the agent does, as a numbered stream you can follow live and resume from.

import { LatentStack } from "@latentcode/sandbox-agents"

const client = new LatentStack({ apiKey: process.env.LS_API_KEY! })
const sessions = client.agents.sessions

const session = await sessions.create({
  agent: {
    model: "bedrock/us.anthropic.claude-sonnet-5",
    instructions: "Answer briefly.",
    // An empty sandbox has nothing to protect, so let the agent run commands without asking.
    permissions: [{ action: "bash", effect: "allow" }],
  },
  input: "Write a Python script that prints the first 10 prime numbers, run it, and show me the output.",
})

for await (const event of sessions.events(session.id)) {
  if (event.type === "tool.called") console.log("tool:", event.data?.tool)
  if (event.type === "text.ended") console.log(event.data?.text)
  if (event.type === "run.completed" || event.type === "run.failed") break
}

const { last_seq } = await sessions.get(session.id)
await sessions.message(session.id, "Now make it print the first 20.")

for await (const event of sessions.events(session.id, { after: last_seq })) {
  if (event.type === "text.ended") console.log(event.data?.text)
  if (event.type === "run.completed" || event.type === "run.failed") break
}

await sessions.delete(session.id)

What the hosted agent provides

• Reading, searching and editing code in its own workspace.
• Running commands and tests in a sandbox.
• Working across several repositories at once, with one patch per repository.
• Asking before risky actions, under permission rules you set.
• Steering while it works, and queueing follow-up tasks.
• Summarizing earlier work to keep long sessions within the model's context window.
• Pausing when idle and resuming later with its conversation and files intact.

Agents use the models, tiers and guardrails your organization already has. Official clients are available for TypeScript and Python.

Data and access

• A session is visible only to the person who created it, in the organization it was created in.
• Repository access uses the GitHub token saved on your Agent Settings page. The token stays with LatentStack and is never placed in the sandbox, and agents can't push. You decide what to do with the patch.
• Authenticate with your personal ls- API key. Keep it on your server; never ship it to a browser.