Shell settings

The Shell card on the Plugins page holds the two limits that bind every command Oda runs: Command timeout (ms) and Output cap per stream (bytes). Use them to set how long one command may run and how much output it may produce.

Open the Shell card

Choose Plugins in the sidebar.
In the Official group, select Shell.

As you work with it:

When you are not editing it, the card shows one line: Limit how long each command may run and how much it may output.
The card appears only while this deployment runs the shell that executes commands and Developer tools is on; Developer settings covers that switch.
The card shares its page with the deployment's other built-in cards, such as Agent loop settings; Built-in plugins shows where each one lives.

Change the command limits

Type a number into Command timeout (ms). The field's hint reads How long one command may run before it is terminated.
Type a number into Output cap per stream (bytes). The field's hint reads Output beyond this spills to a temporary file rather than being lost.
Choose Save. While the write runs, the card shows Saving….

Worth knowing:

Staged until saved. The card keeps what you type as drafts and writes both fields together, only on Save. Leave the card and the drafts are dropped.
An empty field resets. Leave a field empty and choose Save to write a reset for it, so the default applies again.
Numbers only. Text that is not a number blocks the save; the field shows Enter a number, or leave blank to use the default. under it.
A refusal keeps your drafts. If the deployment does not accept the values, nothing is written and the card shows The deployment did not accept these values; they were left for you to correct.
Back to the default. After you save a value that differs from the default, the field carries the Overridden badge. Choose Reset to default beside it, then Save, to clear your value.

Messages you may see

Message	What it means	What to do
`This deployment stores settings read-only.`	The deployment keeps its settings read-only, so the fields are disabled and nothing can be saved here.	There is nothing to change on this card; if a limit must change, contact your administrator.
`This plugin is not loaded, so it cannot be configured right now.`	The deployment is not running the shell plugin at the moment.	There is nothing to configure until the plugin is loaded.
`Enter a number, or leave blank to use the default.`	A field holds something that is not a number, so the save is blocked.	Type a number, or clear the field and save to use the default.
`The deployment did not accept these values; they were left for you to correct.`	The save was refused; nothing was written and your drafts were kept.	Check the values, then choose Save again.

Questions, answered

Where do I set the command timeout and output cap?

On the Plugins page: choose Shell in the Official group and use Command timeout (ms) and Output cap per stream (bytes).

Which commands do these limits apply to?

They bound the shell Oda uses for commands: PowerShell on Windows, and bash on macOS and Linux. The command environment describes the shell and the limits each command runs under.

What does each limit do?

Command timeout (ms) ends a command that runs longer than the time you set; its hint reads How long one command may run before it is terminated. Output cap per stream (bytes) bounds how much of one output stream is kept; output beyond it goes to a temporary file rather than being lost. What happens when a command reaches its time limit is on Shell commands.

Do my edits save as I type?

No. The card stages what you type and writes only when you choose Save, and a save writes both fields together. Leaving the card drops the drafts.

What happens if I leave a field empty?

The save writes a reset for that field, so the default applies again.

What does the Overridden badge mean?

The field holds a value you saved that differs from the deployment's default. The badge stays until the field is reset.

How do I go back to the default value?

Choose Reset to default beside the overridden field, then choose Save. The field returns to the deployment's default.

Why does a field say to enter a number?

The field holds something that is not a number, so the save is blocked. Type a number, or leave the field blank and save to use the default.

The deployment did not accept my values. What now?

The save was refused and nothing was written; your drafts were kept so you can correct them. Check the values and choose Save again.

Why can't I type in the fields?

The deployment stores settings read-only, so the card disables the fields and shows This deployment stores settings read-only. Nothing can be saved here; if a limit must change, contact your administrator.

Why can't I find the Shell card?

The Plugins page shows only while the Plugins page switch is on under Settings > Developer > Advanced features (Advanced features); the Shell card also needs Developer tools on, and a deployment without a local shell shows no Shell card.