Field noteNov 16, 20265 min read1 source

Facade Code 0.1.3 moves settings to facade.json and adds custom CLIs

In one minute

Facade Code Extension 0.1.3 centralizes settings in facade.json and lets users register alternate built-in CLI configurations or custom programs. For teams orchestrating coding agents, the release makes configuration easier to inspect and validate while adding a more flexible way to connect command-line tools.

What changed: Facade Code 0.1.3 adds a facade.json settings file and support for custom CLIs.

What happened

Facade Code’s 0.1.3 release, published on November 11, moves the extension’s settings into one file: ~/.facade/facade.json by default. The file contains settings including yolo, names and clis. The release says the file lists every field for each built-in CLI and includes commented examples. In the extension, Open Settings opens Facade Code’s settings, while Edit in facade.json opens the configuration file and creates it if needed. The editor adds completion, hover help and checks for the configuration. Changes take effect for agents started after the save.

The configuration change also provides a way to define CLI entries. Users can register a built-in CLI under another name, such as Claude Code using another Anthropic-compatible API through environment variables, or Codex with a profile passed through arguments. A renamed built-in retains that CLI’s tools, folder trust, status, Resume and Pin features. The release gives Codex on another API key as an example of a configuration that will no longer show a red status dot. Users can also add other programs using type: "custom".

The release describes two levels of configuration error handling. If the file itself has an error, Facade stops every start and identifies the line and column, with a way to open the file. If one entry is invalid, that entry alone becomes unavailable. This distinction gives users a specific place to look when the overall configuration cannot be read while avoiding the loss of every other CLI because of a single bad entry.

Users upgrading from 0.1.2 have their settings moved on the first read into a new facade.json. The migration does not overwrite an existing file, and Facade reports once what it moved; the old settings are then marked deprecated. The release also says Facade: Home chooses the Facade home directory ahead of FACADE_HOME and ~/.facade. API keys stay out of command lines, logs and list_agents.

Other changes include six CLI logos and 16 Facade robot icons across agent selection, resume and navigation views, cards and terminal tabs. The release says the robots respond to pointer position in the panel but remain still when the operating system requests reduced motion. Installing the Window Component now installs Facade Code as well, and installing Facade Code brings in the Window Component. The release says the published Visual Studio Marketplace and Open VSX files were built and tested on native runners for every platform; it points to SHA-256 values in SHA256SUMS.

What the archive adds

New Runtime covered Facade Code’s 0.1.0 extension on November 7: it brought native agent CLIs into one IDE panel and let agents message and operate one another across windows and machines (earlier coverage). Version 0.1.3 is a new fact on that story, adding configurable CLI entries and centralized settings rather than restating the initial release.

Trend signal

This release supports agent-ready software exposes capabilities: Facade exposes configurable CLI entries as capabilities that users can name, validate and compose into an agent workflow. The release documents configuration mechanics, not a broader interoperability standard, so the signal is about making integrations manageable at the product boundary.

Why it matters

When a team uses several coding CLIs, each connection can otherwise become a special case embedded in a command, editor setting or local setup. A single configuration file gives maintainers a visible place to review which CLIs are registered and how they are invoked. Support for alternate names can help separate environments or API endpoints while retaining the built-in CLI behavior, rather than treating each endpoint as an unrelated tool.

The error model is also consequential for operations: a malformed file stops all starts, while an invalid individual entry affects only that entry. Teams can use that distinction to diagnose configuration-wide failures versus a broken integration. Migration avoids replacing an existing configuration, but teams should still inspect the resulting file and test their agent starts after upgrading. These are useful controls for an extension, though they do not establish how reliably the integrations behave across projects or platforms.

Limits and uncertainty

The release notes describe configuration fields and safeguards but do not report adoption, reliability measurements, or the number of users configuring custom programs. They do not specify a schema versioning or rollback mechanism for facade.json, nor detail which commands, environment variables or permissions a custom CLI can access. Facade says API keys stay out of command lines, logs and list_agents; the release does not describe an independent security review of that guarantee. Cross-platform native builds are reported, but the notes do not provide comparative test results.

Skill to build now

If your team uses Facade with more than one CLI, try moving a noncritical configuration into facade.json before changing production workflows. Register one alternate built-in with a distinct name, verify its API environment and folder trust, then start a new agent to confirm the saved configuration applies. Introduce a deliberately invalid entry in a test setup to check that it is isolated, and keep a copy of the working file so you can restore it if the migration or configuration behaves differently than expected.

Reader takeaway

Facade Code 0.1.3 turns CLI setup into a more explicit, validated configuration surface. Its practical value is clearest for teams already using the extension to coordinate multiple coding agents: alternate built-ins and custom programs can now be managed from one file, with safeguards for migration and configuration errors.

Evidence / sources

  1. 1github.com/y5ez3g/facadecode/releases/tag/extension/0.1.3
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicCodexExplore the codex topic hub.
  2. 02topicClaudeExplore the claude topic hub.
  3. 03topicClaude CodeExplore the claude-code topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract