Deterministic automations

When the steps never change, write them once.

A script is a short piece of JavaScript that calls the same tools your agents use, with no model in the loop. The same steps every time, no tokens spent, and the same approvals, run history and schedules as an agent.

The problem

Not every job needs a model to decide.

Some agent jobs are the same steps every time: read a sheet, post the row for today, send the reply that matches. A model adds cost and a chance of a different answer, and decides nothing. Writing it as code elsewhere loses the approvals, the run history and the schedule your agents have.

How it works

Code that calls your tools, run like an agent.

A script is JavaScript with your enabled tools. It runs in a sandbox, with limits on time, memory and calls, and no access to the network or the file system except through those tools.

No tokens.

No model is called, so a run costs nothing in tokens and returns the same result for the same input.

The same gates.

Any tool can require a person's approval; the script waits for the decision and continues where it stopped.

The same record.

Every run, tool call and log line is on the timeline, like an agent's.

Works with agents.

An agent can call a script as a tool, and a script can hand work to an agent.

Agent or script

Use a model where judgement is needed, and code where it is not.

An agent

  • A model decides each step.
  • Handles the unexpected: new wording, missing data.
  • Costs tokens on every run.

A script

  • Your code decides each step.
  • Does the same thing for the same input, every time.
  • No model, no tokens.

Free two-week pilot

Try it free for two weeks.

We set it up on one job your team repeats. You approve every email and post. If it does not work for you, you stop and pay nothing.