Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesstack72

Relationships

#2030 Expose configured per-method definition arguments in model get --json

Opened by dieter · 9/5/2026· Shipped 9/7/2026

Problem

A YAML model definition can configure per-method argument overrides at methods.<method>.arguments. The supported JSON surfaces do not expose them:

  • swamp model get <definition> --json returns the definition identity, global arguments, and the TypeScript type methods, but not the definition method configuration.
  • swamp model evaluate <definition> --json evaluates global arguments only.

This prevents CLI-only clients from accurately showing the effective definition configuration. Lazyswamp can distinguish a YAML definition from its TypeScript type interface, but cannot display per-method overrides without reading private YAML storage directly.

Proposal

Add a definition-level field to swamp model get <definition> --json that exposes configured per-method arguments, keyed by method name. Preserve the raw configured values/expressions rather than substituting the type-level argument schema.

For example:

{
  "configuredMethods": {
    "import": {
      "arguments": { "chunkSize": 1000 }
    }
  }
}

The exact field name and shape can follow existing CLI conventions.

Why this surface

model get --json already represents a selected YAML definition, so it is the natural place for definition-specific configuration. Extending type-level search/describe output would not solve this, because multiple definitions may share one type while carrying different overrides.

Acceptance criteria

  • A definition with methods.<name>.arguments returns those configured arguments from model get --json.
  • Definitions without overrides remain distinguishable from type-level method schemas.
  • Values are redacted consistently with other sensitive definition fields.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 15 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/7/2026, 10:12:14 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/7/2026, 9:17:34 PM
Editable. Press Enter to edit.

stack72 commented 9/7/2026, 10:15:42 PM

Thanks @dieter for reporting this! We shipped: Expose definition-configured per-method argument overrides through model get --json, keeping them separate from type-level method schemas and applying the existing schema-driven sensitive-value redaction.. The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.