Codex config import parses TOML with Bun's built-in parser / Claude Code v2.1.222

Not switched on

Useful2 Signal2

Internals not in their notes

Importing another agent's config now parses TOML natively, reachable only through the gated import path.

TOML parsing for a foreign agent config is wired up but only reachable behind the tengu_import gate.

Feature flag

tengu_import On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.222: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.222. It isn't a statement about your account. What a flag value here can and cannot tell you

tengu_import

What

Reading a foreign agent's Codex config during import now uses Bun's native TOML parser through a one-line wrapper, before the config is mapped.

Details

The wrapper calls Bun.TOML.parse(e) on the config file contents
Reachable only via the import path, which is behind tengu_import
A filename/label normalizer was added alongside it: NFKC normalize, lowercase, strip trailing dots and spaces

Evidence

Bun.TOML.parse

Strings lifted out of the shipped bundle, so the claim above can be checked against them.