Add another terminal program
Add a terminal program to New Agent with its own executable, arguments, and environment.
Choose the integration type
For Claude Code, Codex, Antigravity, Muse Code, OpenCode, or Pi, use the corresponding built-in type even when you connect it to another provider. That keeps Facade’s tools and messaging available in the CLI.
Use custom for another terminal program. You can launch and type into it from Facade, but it does not receive Facade collaboration tools or messages.
Example: Add Aider
Install Aider and configure its model access first. Add this setup to facade.json (see Agent settings):
{
"clis": {
"Aider": {
"type": "custom",
"command": "aider",
"args": [
"--model",
"YOUR_AIDER_MODEL_ID"
],
"icon": "facade-pink"
}
}
}Replace the model ID with one your Aider setup supports. Save, choose New Agent, and select Aider. Use its terminal to send your task.
Set the command and arguments
Set command to one executable, using its full path if it is not on your terminal’s PATH. Put each argument in a separate string in args, in the order the program expects.
Arguments are passed literally. Shell expressions such as pipes, &&, and variable references are not evaluated. Add environment variables in env.
For a custom program, model options belong in its own arguments, as --model does in the Aider example. Facade’s model and effort fields are not accepted for custom entries.
Know which features are available
| Feature | Built-in type | custom |
|---|---|---|
| Terminal input | Available | Available |
| Facade tools and skill | Provided by the built-in type | Not available |
| Tasks and messages from other agents | Delivered by Facade | Unavailable; type in the terminal |
| Activity tracking | Depends on the CLI and platform | Not shown; check the terminal |
| Resume and Pin | Through the CLI’s own saved conversations, where supported | Unavailable |
YOLO does not change a custom program’s permissions. The program uses its own permission settings.