Skip to main content
Write Lua in your editor, test its behavior, and make it available to your Atonom agent. The CLI connects your local scripts to the tools in your Atonom environment.

Install the CLI

Get the binary from the Atonom team and connect your workspace.

Build your first tool

Create a tool, write a transform, and verify its result.

Work with a coding agent

Use a ready-to-copy task brief and development workflow.

Choose what to script

Move repeatable rules and logic out of your agent’s prompt.

​
The development loop

42 is an example tool ID. Use an ID from your own list output. If you have sandbox access, use eval to test local changes before saving.
Know which command savespush saves your local script. run also saves by default, then executes it. Use eval to test a local file without saving, or run --no-save to execute the body already stored on the platform.

​
How the pieces fit

The CLI connects your local .lua files to stored Lua script tools. Use it to download scripts, review changes, and test your tools from the terminal. A coding agent works in your repository: it reads the contract, edits files, invokes the CLI, and inspects JSON results. No agent-specific integration is required beyond access to the CLI and workspace. An Atonom agent owns and uses the Lua tool. It is distinct from the coding agent that helps you author the script. The sandbox lets you test Lua with sample inputs and simulated tool responses. During a sandbox test, the CLI supplies those responses. During platform execution, Atonom handles calls to available tools and returns their results to your script.

​
A small authoring contract

A stored script defines transform(context). Inputs become context; the return value becomes the tool’s JSON result. The Lua guide covers validation, JSON helpers, and runtime limits.

​
Find what you need

Use the site search to find commands and examples. Use atonom --help to see the commands available in your installed version.