[FEATURE]: Config schema should tolerate unknown fields instead of failing all session loading #33196

Activity

1. mouse114514

   changed the title [-]Config schema should tolerate unknown fields instead of failing all session loading with ConfigInvalidError[/-] [+][FEATURE]: Config schema should tolerate unknown fields instead of failing all session loading[/+] on Jun 21, 2026
2. github-actions

   assigned

   nexxeln

   on Jun 21, 2026
3. Necmttn commented on Jun 21, 2026

   

   Necmttn

   on Jun 21, 2026

   More actions

   The config loader should produce partial config plus structured warnings. Unknown root keys can emit config.warning with JSON path, schema version, and ignored value type; invalid known sections can fall back to defaults for that section.

   Session loading should only fail for errors that make runtime unsafe, such as malformed JSON or invalid required provider credentials. A regression should prove one stray root key does not block session list, resume, or new-session creation.

   ---

   Generated with ax.
4. mouse114514 commented on Jun 22, 2026

   

   mouse114514

   on Jun 22, 2026

   Author

   More actions

   This isn't hypothetical — we have concrete evidence. In the current stable code (packages/opencode/src/config/parse.ts:40-47), topLevelExtraKeys() throws an InvalidError with code "unrecognized_keys" for any root-level key not in the Config schema:

   const extra = topLevelExtraKeys(schema, data)
   if (extra.length) {
     throw new InvalidError({
       issues: [{
         code: "unrecognized_keys",
         keys: extra,
         message: `Unrecognized key${...}: ${extra.join(", ")}`,
       }]
     })
   }

   We had a config file with "files": {} at root level, which is not a known Config key — this immediately blocked all session loading. The schema has no index signatures, so any stray key triggers the error.
5. github-actions commented on Aug 22, 2026

   

   github-actionsBot

   on Aug 22, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
6. github-actions

   closed this as not plannedon Aug 22, 2026