fleet/fleetd
3
0
Fork 0
Code Issues 73 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

autoCompactWindow: per-profile bounded auto-compaction, both backends #165

Closed
agent wants to merge 0 commits from worker/autocompact-window-82bc2f-5 into main
pull from: worker/autocompact-window-82bc2f-5
merge into: fleet:main
Conversation 1 Commits - Files Changed -
agent commented 2026-08-24 16:55:00 +02:00
Member
Copy Link
Copy Source

Adds an opt-in per-profile config key autoCompactWindow (Integer, tokens) to FleetConfig.Profile and wires it into both peer launchers.

  • Claude Code: appends --autocompact <window> to argv (mirrors --model), surviving the ccs <profile> wrapper.
  • opencode: has no absolute compact-at-N knob, so the window is applied as the resolved model's own limit.context (plus a required limit.output: 16384 default) in the generated opencode.json, merged via get-or-create nodes so it never clobbers a custom-provider block written for a pinned endpoint. Only applies when model: resolves to provider/model; otherwise logs a WARN naming the profile rather than a silent no-op.
  • Validated at config load to [100000, 1000000] — the band Claude Code's own --autocompact flag accepts.
  • Default (unset/null) leaves today's behaviour exactly.

Docs added to fleetd.example.yaml explaining the cross-backend semantics difference.

Tests: new tests in ClaudeCodeLauncherTest, OpenCodeLauncherTest, and FleetConfigTest. Full mvn clean install: BUILD SUCCESS, 926 tests run, 0 failures, 0 errors.

Adds an opt-in per-profile config key `autoCompactWindow` (Integer, tokens) to `FleetConfig.Profile` and wires it into both peer launchers. - **Claude Code**: appends `--autocompact <window>` to argv (mirrors `--model`), surviving the `ccs <profile>` wrapper. - **opencode**: has no absolute compact-at-N knob, so the window is applied as the resolved model's own `limit.context` (plus a required `limit.output: 16384` default) in the generated `opencode.json`, merged via get-or-create nodes so it never clobbers a custom-provider block written for a pinned endpoint. Only applies when `model:` resolves to `provider/model`; otherwise logs a WARN naming the profile rather than a silent no-op. - Validated at config load to `[100000, 1000000]` — the band Claude Code's own `--autocompact` flag accepts. - Default (unset/null) leaves today's behaviour exactly. Docs added to `fleetd.example.yaml` explaining the cross-backend semantics difference. **Tests**: new tests in `ClaudeCodeLauncherTest`, `OpenCodeLauncherTest`, and `FleetConfigTest`. Full `mvn clean install`: BUILD SUCCESS, 926 tests run, 0 failures, 0 errors.
agent added 6 commits 2026-08-24 16:55:01 +02:00
CB-634 (draft): mount the IDE Index MCP into a member, opt-in per profile d811b30df3 
Adds `ideMcpUrl` to FleetConfig.Profile (default off). When set, the
Claude Code launcher mounts the IDE Index MCP as a second inline
--mcp-config server named `intellij`, and appends an IDE charter that
pins every ide_* call to the member's own worktree (spec.cwd()). The
charter order is role -> ide -> reply, one --append-system-prompt-file,
reply last (CB-618). The mount gate now fires on ideMcpUrl alone, not
only mcpUrl. ConfigRef treats an ideMcpUrl change as deferred, like the
other launch flags.

Never touches .mcp.json or CLAUDE.md — the mount and the rule arrive as
launch flags, so a project's own config is untouched.

Not yet done (see fleetd #162): the bridged-owned IDE lifecycle
(open on provision, close before worktree removal), and the opencode
adapter (separate ticket). fleetd.example.yaml documents ideMcpUrl and
fixes the stale parityOverlay default.

911 tests green.
CB-634: deliver IDE guidance as an on-disk overlay, not the system-prompt charter a3fc7e4df8 
Move the IDE guidance text to PeerLauncher.ideOverlayText (shared by both
launchers). ClaudeCodeLauncher drops it from the reply-charter file and writes
CLAUDE.local.md into a provisioned worktree instead, gated on a .git FILE
(safety: never writes into the primary's real .git-DIRECTORY checkout) and
registers it in info/exclude. OpenCodeLauncher mounts the intellij server and
adds the rules file to the instructions array.
Merge CB-634 overlay redesign: deliver IDE guidance as on-disk CLAUDE.local.md / opencode instructions overlay 5a8cf4cb4d
CB-634: write the overlay exclude to the common git dir, not the per-worktree gitdir a5efb7c676 
git reads info/exclude from the common dir for a linked worktree (only
info/sparse-checkout is per-worktree), so the entry written into
<common>/worktrees/<name>/info/exclude was never honoured and CLAUDE.local.md
showed as untracked -- at risk of being swept into a worker's PR. Derive the
common dir (<common>/worktrees/<name> -> <common>) and write there. Found by
dogfooding a real spawn on fleet01; the test now uses the real worktree layout
and asserts the entry lands in the common dir, not the per-worktree gitdir.
CB-634: pin the IDE overlay to the module dir + best-effort auto-open 7655f1b51a 
The overlay pinned project_path to the worktree root. For a repo whose Maven
module is a subdir (this repo's pom is in `bridged/`, not at the root), opening
the root imports no module and every ide_* call resolves nothing. Pin and open
the module dir instead.

Two new opt-in per-Profile keys, both read only when ideMcpUrl is set:
- ideProjectDir: repo-relative module dir the IDE opens and the overlay pins;
  blank keeps the old worktree-root behaviour.
- ideOpenCommand: host command that opens that dir in the IDE at spawn, with
  {dir} substituted and run through /bin/sh -c so env (e.g. DISPLAY) can be set
  inline. Best-effort and non-fatal — a failure never fails the spawn. Blank
  keeps the manual-open behaviour. No close half yet (deferred).

Shared helpers PeerLauncher.ideProjectPath / openInIde back both launchers.
The two Profile fields ride a back-compat constructor, so every existing call
site and YAML compiles and behaves unchanged.

Tests: overlay content pins the module dir when ideProjectDir is set;
ideProjectPath resolution; openInIde no-op on a blank command. 918 tests green.
autoCompactWindow: per-profile bounded auto-compaction, both backends
CI / contract (pull_request) Successful in 41s
Details
CI / build (pull_request) Failing after 1m37s
Details
2757bc7185 
Add opt-in Integer autoCompactWindow to FleetConfig.Profile (last field,
null/unset = today's behaviour). Validated at config load to [100000,
1000000] — the band Claude Code's own --autocompact flag accepts.

Claude Code: appends --autocompact <window> to argv (mirrors --model),
so it survives the ccs <profile> wrapper.

opencode: has no absolute compact-at-N knob (only compaction.auto/prune/
reserved/tail_turns/preserve_recent_tokens), so the window is applied as
the resolved model's own limit.context (+ a required limit.output:16384
default) in the generated opencode.json, merged via get-or-create nodes
so it does not clobber a custom-provider block. Only applies when model:
resolves to "provider/model"; otherwise logs a WARN naming the profile
rather than silently doing nothing.

Docs added to fleetd.example.yaml explaining the cross-backend semantics
difference (compacts AT the window vs. WITHIN it).
ltms commented 2026-08-24 19:12:46 +02:00
Owner
Copy Link
Copy Source

Landed on main via the cb-634-ide-mcp integration merge (450a5ed), not this PR. This branch forked from cb-634-ide-mcp, so it also carried the CB-634 work and could not merge to main on its own. The autoCompactWindow change is now in main and live on the Mac daemon (verified: claude member gets --autocompact 250000, opencode member gets limit.context). Closing as redundant.

Landed on `main` via the `cb-634-ide-mcp` integration merge (`450a5ed`), not this PR. This branch forked from `cb-634-ide-mcp`, so it also carried the CB-634 work and could not merge to `main` on its own. The autoCompactWindow change is now in `main` and live on the Mac daemon (verified: claude member gets `--autocompact 250000`, opencode member gets `limit.context`). Closing as redundant.
ltms closed this pull request 2026-08-24 19:12:57 +02:00
Some checks are pending
CI / contract (pull_request) Successful in 41s
Details
CI / build (pull_request) Failing after 1m37s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
blocked
Cannot start until something else lands. The body says what.
 needs-live-proof
Merged and green, but never shown working on the running daemon. Not the same as done.
 ready-to-delegate
Scope, files and acceptance criteria are written. A worker can be briefed from the body alone.
 silent-default
A feature that compiles, passes tests, and ships turned off. Nine recurrences and counting.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent kevin ltms
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fleet/fleetd#165
Delete Branch "worker/autocompact-window-82bc2f-5"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?