Banata

Core Concepts

Capabilities

Choose the capabilities a sandbox should be prepared to use, and learn when each capability is worth enabling.

Capabilities tell Banata what the sandbox should be prepared to do.

They are how you shape the workflow environment around the job you are about to run.

Agent capability

Enable the AI agent when the job needs multi-step work.

ts
capabilities: {
  agent: { enabled: true, defaultAgent: "build" },
}

Use it for:

  • research
  • report generation
  • browser-driven tasks
  • document workflows
  • longer async jobs

Browser capability

Enable the browser when the workflow needs a real web session.

ts
capabilities: {
  browser: {
    viewport: { width: 1440, height: 900 },
  },
}

This makes these patterns possible:

  • live preview
  • agent-driven browsing
  • human handoff
  • uploads and downloads through the browser

Recording

Recording captures the browser session and saves it as an artifact.

ts
capabilities: {
  browser: {
    recording: true,
  },
}

Use it when you need:

  • QA review
  • compliance or audit trails
  • evidence of what the workflow actually did

Outbound proxy configuration

If your plan supports it, you can configure outbound routing for the sandbox browser and runtime.

ts
capabilities: {
  browser: {
    byoProxyUrl: "http://user:pass@proxy.example.com:8080",
  },
}

Document tools

Enable document tools when the job reads, transforms, or exports documents.

ts
capabilities: {
  documents: { libreofficeHeadless: true },
}

Use it when the workflow should:

  • export PDFs
  • convert formats
  • generate office-style deliverables

Storage options

Storage-related options are for workflows where artifact organization matters.

ts
capabilities: {
  storage: {
    artifactPrefix: "customer-a/job-42",
  },
}

How to choose capabilities well

A good rule is:

enable the capabilities the workflow truly needs, and no more