Back to Signal Feed
CodeTracked since May 19, 2026

Normalize RunCommand `kilocode_change` markers to cut merge noise

In `packages/opencode/src/cli/cmd/run.ts`, the PR reverts a noisy yargs reformat and rewrites the `kilocode_change` sections so the upstream diff reflects only real Kilo-specific logic (for example `--auto` and `KILO_SERVER_PASSWORD`) rather than a large formatting-only block.

run.tskilocode_changeRunCommandyargs

What Happened

  • In `packages/opencode/src/cli/cmd/run.ts`, the PR reverts a noisy yargs reformat and rewrites the `kilocode_change` sections so the upstream diff reflects only real Kilo-specific logic (for example `--auto` and `KILO_SERVER_PASSWORD`) rather than a large formatting-only block.
  • In `packages/opencode/src/cli/cmd/run.ts`, the PR reverts a noisy yargs reformat and rewrites the `kilocode_change` sections so the upstream diff reflects only real Kilo-specific logic (for example `--auto` and `KILO_SERVER_PASSWORD`) rather than a large formatting-only block.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

The concrete change is a mergeability-focused refactor: it removes a formatting-only parenthesize/indent churn from `RunCommand` and adds explanatory annotations to each `kilocode_change` marker, so future upstream syncs can be reviewed against true behavioral deltas only.

Why Track This

Why It Matters

Developers maintaining the Kilo fork should find upstream CLI merges in `run.ts` easier and safer, since the file now highlights only real Kilo-specific behavior changes and avoids a large false-positive diff that previously obscured what actually changed. This lowers merge-review effort and reduces the chance of missing or reintroducing changes around `--auto`, `--cloud-fork`, env handling, task tracking, retries, and stdin flow; teams should watch for future edits that drift from the documented markers and reintroduce formatting churn in `run.ts`.

Impact

Developers maintaining the Kilo fork should find upstream CLI merges in `run.ts` easier and safer, since the file now highlights only real Kilo-specific behavior changes and avoids a large false-positive diff that previously obscured what actually changed. This lowers merge-review effort and reduces the chance of missing or reintroducing changes around `--auto`, `--cloud-fork`, env handling, task tracking, retries, and stdin flow; teams should watch for future edits that drift from the documented markers and reintroduce formatting churn in `run.ts`.

What To Watch Next

  • Watch whether run.ts becomes a repeated pattern.
  • Track follow-up changes around Code Repository Intelligence.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: marker_annotation_drift, future_upstream_format_reversion.
Open Topic TimelineOpen Technical EventOpen Original Sourcemarker_annotation_drift / future_upstream_format_reversion / merge_review_false_confidence

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

Kilo-Org/kilocode PR #10379: refactor(cli): normalize kilocode_change markers in run.ts

Undo a parenthesize+extra-indent reformat of the yargs builder in RunCommand so the diff vs upstream shrinks from a ~90-line `kilocode_change` block to the actual Kilo-specific lines, and annotate every `kilocode_change` marker with what changed and why.