ltms - Gitea

ltms commented on issue fleet/fleetd#176

2026-09-03 07:02:15 +02:00

capacity counts panes, not subscription seats, so a subscription profile reports a free slot that cannot be filled

Hit the same shape again today, on a different profile and for a different underlying reason. Recording it because it shows the defect is wider than the subscription-seat case this ticket was…

ltms opened issue fleet/fleetd#249

2026-09-03 06:59:22 +02:00

fleet_list can report another session's agentSessionId, and fleet_spawn{resumeSessionId} will resume it

ltms closed issue fleet/fleetd#234

2026-09-03 06:58:26 +02:00

#175's model read-back fires a FALSE POSITIVE on any member spawned without a worktree — and the quarantine it announces never happens

ltms commented on issue fleet/fleetd#234

2026-09-03 06:58:23 +02:00

#175's model read-back fires a FALSE POSITIVE on any member spawned without a worktree — and the quarantine it announces never happens

Fixed and merged to main as 838a701.

ExhaustionSink's 3-argument method (carrying the profile) is now the single abstract method, so a caller must supply the profile. The false positive is…

ltms closed issue fleet/fleetd#227

2026-09-03 06:58:16 +02:00

A backend outage is invisible at fleet level: repeated backend errors are never correlated, never cool off a credential, and never reach the lead

ltms commented on issue fleet/fleetd#227

2026-09-03 06:58:14 +02:00

A backend outage is invisible at fleet level: repeated backend errors are never correlated, never cool off a credential, and never reach the lead

Done and merged, together with #201 — the two were refined into one five-unit series because a fleet-level correlation needs a per-target classification to correlate. See #201 for the unit-by-unit…

ltms closed issue fleet/fleetd#201

2026-09-03 06:58:04 +02:00

Backend-error classification needs a real mechanism, not hard-coded strings (#164 points 3 and 4)

ltms commented on issue fleet/fleetd#201

2026-09-03 06:57:58 +02:00

Backend-error classification needs a real mechanism, not hard-coded strings (#164 points 3 and 4)

Done and merged. All five units are on main.

ltms closed pull request fleet/fleetd#243

2026-09-03 06:57:47 +02:00

fleetd #241: suppress echoed fallback briefs

ltms commented on issue fleet/fleetd#241

2026-09-03 06:57:44 +02:00

Completion fallback can hand the lead back its own brief as the member's "report"

Correction to my comment above: the PR for this work is #243, not #245. #245 is the #134 tool-surface PR. The merge commit 5cf3ca9 carries the same wrong number in its message; it is pushed,…

ltms closed issue fleet/fleetd#241

2026-09-03 06:57:19 +02:00

Completion fallback can hand the lead back its own brief as the member's "report"

ltms commented on issue fleet/fleetd#241

2026-09-03 06:57:14 +02:00

Completion fallback can hand the lead back its own brief as the member's "report"

Fixed and merged to main as 5cf3ca9 (PR #245).

CompletionResolver.echoesInjectedBrief now refuses a scrape that is just the injected brief read back, so a silent member no longer looks like…

ltms closed pull request fleet/fleetd#246

2026-09-03 06:57:05 +02:00

fleetd #201/#227 unit 5: wire errorPattern, cool-off spawn gate, and fleet views

ltms opened issue fleet/fleetd#248

2026-09-03 06:55:33 +02:00

Fleetd's composition root is untested: a feature can be silently unwired and every test stays green

ltms pushed to main at fleet/fleetd

2026-09-03 06:54:19 +02:00

5cf3ca9a89 fleetd #241: never hand the lead back its own brief as the member's report

ac474981e4 fleetd #201/#227 Unit 5: wire the backend-error cool-off into config, placement and the MCP surface

ba04b2359b fleetd #201/#227 unit 5: wire errorPattern, cool-off spawn gate, and fleet views

3437d6313d fleetd #241: bound the echo match so a real report is never swallowed

321d8dcbb5 fleetd #241: suppress echoed fallback briefs

Compare 5 commits »

ltms commented on issue fleet/fleetd#148

2026-09-03 06:50:44 +02:00

CB-634: the parity overlay copies .env/.envrc into worker worktrees — the same shape as CB-633

Decision on points 1 and 2 (lead), with the evidence the ticket asked for first

Live exposure: none today. I checked this host on 2026-09-03:

ls -la .env .envrc in the primary…

ltms commented on issue fleet/fleetd#149

2026-09-03 06:48:16 +02:00

A claude-code member spawned into a fresh worktree blocks forever on the workspace trust dialog

Fixed and merged to main as 2e5b63f (PR #244).

ClaudeCodeLauncher now seeds projects.<cwd>.hasTrustDialogAccepted and hasCompletedProjectOnboarding in ~/.claude.json (or `configDir/.cl…

ltms opened issue fleet/fleetd#247

2026-09-03 06:47:57 +02:00

Seeding ~/.claude.json can still lose an external writer's change

ltms closed pull request fleet/fleetd#244

2026-09-03 06:47:40 +02:00

fleetd #149: seed the workspace-trust dialog before a claude-code spawn

ltms commented on pull request fleet/fleetd#244

2026-09-03 06:47:34 +02:00

fleetd #149: seed the workspace-trust dialog before a claude-code spawn

Merged into main as 2e5b63f (round 2 head 743377d). Closing this PR — the branch is in main, not dropped.

How I checked it (lead, in an isolated worktree):