# Code mode

Use Code mode to organize a multi-step tool task through code, keeping discovery, intermediate data, and verified results in the sandbox.

## Before you start

Open **Customize → Plugins** and select this plugin. Choose **Add** if it is available and not installed; **Uninstall** means it is already installed. Availability depends on the deployment and administrator policy. Enable the plugin for the selected agent or task using [agent setup](/agents/create/).

This package does not require a separate external app account for its own Redbelt tools. Its work can still depend on configured services, sandbox availability, selected files, or a separate authorized connection. Adding the package does not grant access to additional data. Review the installed tool controls and handle any requested [action approval](/threads/approvals/).

![Use Code mode plugin in Redbelt](/screenshots/current/plugin-workspace.png)

The related **Sandbox** plugin page. Code mode availability depends on your deployment.

## Coordinate a read-first analysis

1. Confirm that Code mode and Sandbox are available in your deployment. If Code mode is absent from the plugin gallery, ask your administrator about package availability.
2. Define the source systems, exact resources, and desired final result.
3. Ask Redbelt to discover the available plugin contracts before composing the program.
4. Start with bounded reads and inspect intermediate results before any proposed write.
5. Review the final summary or file and identify which actions actually completed.

> Use Code mode to read the selected launch tracker and the corresponding Jira issues. Match records by explicit issue key, report missing matches, and prepare a discrepancy table. Do not change either system. Return the checked table with source references.

## Keep connected-tool boundaries intact

Code mode supplies a programming workflow, not a separate catalog of create/read/update app actions. The program discovers and invokes the connected tools that are available to the task. Those tools still enforce account access, validation, and requested approvals.

Use returned identifiers and typed inputs rather than guessing app endpoints or handling provider credentials directly. A partially successful batch can contain failed items; inspect each result and report its coverage instead of treating the whole batch as complete.

Code mode is useful for repeated reads, joins, and file transformations. It does not make unsupported plugin operations available. If a write is needed, review the exact destination and content first.

## Tool Reference

Thread and workflow availability are listed separately. A tool must also be enabled for your task and allowed by its account and administrator policy. [Configure workflow app actions](/workflows/apps/) using only actions offered by the current picker.

This package supplies an agent skill and sandbox helpers rather than a separate named app-action tool catalog. Its task workflow is described above.

## Troubleshoot

If a required tool is missing, inspect the task’s plugin selection and deployment catalog. If Code mode is not listed locally, keep its use pending until the administrator supplies a compatible package.
