Skip to content

spec(FIX-1185): a coding agent driven through the in-process SDK never invokes its plan tools; the CLI does - #3166

Merged
jhoffner merged 1 commit into
mainfrom
spec/FIX-1185
Oct 12, 2026
Merged

jhoffner merged 1 commit into
mainfrom
spec/FIX-1185

Conversation

@jhoffner

Copy link
Copy Markdown
Collaborator

Requested by Jake · project thread

spec(FIX-1185): a Claude Code run started from a flow keeps its own plan

Someone who… Today After
runs Claude Code from a flow with no prompt of its own The agent starts from an empty system prompt. It keeps no to-do list. It writes its plan as prose at the end The agent starts from Claude Code's own prompt, the same as the claude CLI. It keeps its to-do list as it works
reads a run's plan record (Kitchen Sink's plan panel) The record is empty on every real run, 0 of 8 The rows go from pending to completed while the run works
adds a line of instructions to the agent The line replaces the full prompt The line goes on top of Claude Code's prompt, or replaces it, as the host selects
wrote a full prompt on purpose Gets that prompt Gets that prompt. No change
wants the empty start of today n/a Gives an empty string

Goal: a Claude Code run started from a flow, with no prompt of its own and a job that does not mention planning, keeps its own to-do list, and you can read that list from the run's state.

flowchart LR
  J["a held-out multi-step job · names no tool"] --> R["a real Claude Code run · no prompt given · recordWork on"]
  R --> S["the run's plan record · read from state"]
  S -->|"rows on 3 of 3 runs · at least one completed"| P["PASS · goal met"]
  C["control · an empty prompt · today's behaviour"] -.-> R
  S -.->|"under the control"| F["must FAIL · no plan rows"]
Loading

The check reads rows from state, not the closing message of the agent. Under the control it must fail. Check: goals/claude-code-harness/it-keeps-its-own-plan/, real model on a signed-in local host, control GOAL_CONTROL=empty-prompt. Why this goal: SPEC.md.''``

Two rows, the same run. Today the block asks for nothing, the SDK sends an empty prompt and the plan record stays empty. After, the block asks for Claude Code's own prompt and the record fills. A full prompt string or an empty one still goes through unchanged

Only the second box changes: what the block asks the SDK for when the host gives nothing.

How: the CLI and the SDK run the same agent. The CLI starts from Claude Code's prompt, which tells the agent to use its to-do tools. The SDK sends an empty prompt when it gets none. A model-free POC shows this. The block now asks for Claude Code's prompt by default, and it forwards the SDK's append form.

Sign off

The goal, at that size. If wrong: the recorder fills only when a host remembers to prompt for it.

With no prompt given, a run starts from Claude Code's own prompt · D1

D1: what a run starts from with no prompt given. Chosen: Claude Code's own prompt, instead of an empty prompt plus a plan line when recording. Decides it: whose plan is recorded. Price: every host that omits the prompt changes

It comes down to whose plan it is: a line we add records our instruction, not the decision of the agent. If wrong: every host that omits the prompt gets a larger, different agent, and our runs change when Claude Code's prompt changes.

A caller's own string still replaces that prompt; to add to it is a separate form · D2

D2: what a caller's prompt string means. Chosen: it replaces, as in the SDK, instead of becoming an addition. Decides it: a host that wrote a full prompt on purpose. Price: one-line role text keeps an empty plan until it moves

It comes down to the host that wrote a full prompt on purpose: an addition makes it larger without a request. If wrong: hosts with one line of role text keep an empty plan until they move to the append form. In this repo, that is the Shift Manager harness and one devforce goal.

Open: none. D1 is the one to weigh. Reasons and what lost: DECISIONS.md.

Reviewers · look here

  • Decisions → D1. Is a changed default for all hosts better than a plan line that only runs with recording on?
  • Spec → the goal check. Does 3 of 3 runs, with the record read from state and a job that names no tool, prove that the agent plans on its own?
  • Decisions → Settled. The POC shows what the SDK sends. It does not show that Claude Code's prompt makes the agent plan. The goal check shows that.

Not here: the plan panel and the move of the record into core (FIX-1915). Changes to the Shift Manager harness (its owners decide).

Spec · Decisions · Rules · Plan · Docs · Linear FIX-1185 · epic FIX-1907 · merges after human approval and required checks (contract)

POC · what the SDK sends for each prompt shape (model-free, throwaway)

pnpm tsx specs/issues/FIX-1185/poc/what-the-sdk-sends/run.mts

The question: do the CLI and the SDK differ before the model sees anything? It drives the real SDK query() with a stub agent process and prints the first message the SDK sends. Result: no prompt and "" both send systemPrompt: [""]. The preset sends no custom prompt, so the agent keeps Claude Code's own. A planted fault makes it fail. Exit 0 means the premise holds.

How to review this — altitude, what's in scope, what's deliberately unsettled

This is a direction set, not an implementation. Reviewing it well means
answering one question: is this the right approach?

In scope to challenge:

  • The goal and the problem framing in SPEC.md — is the goal the real need at full size,
    for the people named, or a smaller goal that would let us call this done early? Would the
    named check fail if the goal were not met?
  • The approach — will it work, does it fit the architecture and docs/philosophy.md?
  • Any numbered decision in DECISIONS.md — that's the sign-off surface.
  • A case BUSINESS-RULES.md misses, or a rule that would invalidate the design.
  • Scope — a deliverable that shouldn't ship, or one that's missing.
  • The reader-facing promises in DOCS.md and their fit with the rules; a missing or
    misleading lineage claim in conditional EVOLUTION.md.

Out of scope — deliberately unsettled here, and owned by the implementing agent:

  • Names, signatures, file paths, and module layout beyond the few PLAN.md pins on purpose.
  • Local structure: which helper, how a function is decomposed, error-message wording.
  • Micro-optimizations and style preferences.
  • Test names and internal test structure (the behaviours are the rules; the tests are not).
  • Anything PLAN.md left open on purpose — it is directional by design, and a gap at that
    altitude is intended, not an omission.
  • The figures, at the pixel level. A figure is right when it reads right. A misplaced label
    or a colour you'd have chosen differently is not a finding; a figure that shows a shape the
    decisions don't say is.
  • The solution sketch, at the line level. PLAN.md may include a rough pseudocode sketch
    showing the shape of the proposed solution. It is knowingly incomplete, is not real code,
    and is not what will ship. Review it for directional viability only. Do not report
    that it lacks error handling, omits edge cases, names things that don't exist in the repo, or
    wouldn't build: all of that is true on purpose.
  • POC implementation polish. Experiments under the owning spec's poc/ are retained,
    not production code. Read them for directional evidence, not production completeness.
    Their isolation from production/default discovery and absence of secrets or generated
    dependencies are in scope; retention is not permission to weaken repository checks.

One request, if you are an automated reviewer: the two lists above are the whole difference
between a useful review of this document and a long one. Volume is not signal here — a single
finding above the line is worth more than twenty below it.

Feedback in the second list is welcome and gets recorded verbatim in PLAN.md → Notes from review for the implementer to weigh against real code. It will not be argued with, and it
will not be folded into the design prose. Please don't re-raise it: one mention is enough.

The one exception is the sketch and the POC. Line-level feedback on either is dropped, not
recorded — there is nothing for an implementer to weigh about code that isn't shipping. Feedback
about their direction is not line-level and is treated like any other above-the-bar finding.

Direction approval does not waive merge-time required checks, approvals or thread policy.
Optional comments do not require another design round merely to reach zero comments.

🤖 Generated with Claude Code

https://claude.ai/code/session_017pp7wCd87NW4BH7XVuF9Gv


Generated by Claude Code

The SDK path sends an empty system prompt when the block gives none, so
the agent never sees the guidance that makes the CLI use its to-do tools.
The spec moves the block's default to Claude Code's own prompt, forwards
the SDK's append form, and proves it with a real-model goal check that
reads the plan record from state. Includes a model-free POC showing what
the SDK sends for each prompt shape.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017pp7wCd87NW4BH7XVuF9Gv
@linear-code

linear-code Bot commented Oct 12, 2026

Copy link
Copy Markdown

FIX-1185

@jhoffner

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-12T18:27:03.580986Z 02fea6c Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Copy link
Copy Markdown
Collaborator Author

Second look (direction only)

The diagnosis and the lean shape are right. One option's default moves, the SDK's own prompt union is forwarded, and the recorder is left alone. I found no better approach. The items below are things to settle or watch, ranked.

1. The "3 of 3 runs, at least two rows" bar may be flaky by construction.
Whether Claude Code plans is up to the model. A job of three or more steps may legitimately get one to-do row, or none. The control bar ("fails on at least two plan rows") is a count threshold, so a PASS run that plans once will fail. The spec should say how a flake is told apart from a miss. For example, state that the held-out job is sized so that the CLI plans on it every time (measure the CLI first), and put that CLI baseline in the PR. Without it, a red PASS arm is ambiguous: wrong default, or a job too small to plan.

2. D1 widens beyond the plan. The spec prices "a larger, different agent" but doesn't measure it.
The preset also brings Claude Code's other behaviour: its tool-use conventions, its git and commit guidance, and the environment block. The hosts that change on upgrade (Kitchen Sink, the coding-skill lab, the conductor lab, the workspace capability) each have their own tests. Suggest the implementer run those suites' real-model goals (or at least their stubbed specs) once against the new default and report the diff in the PR. "Every host changes" is the stated price, but only the plan half of the change is proved.

3. Interaction with settingSources.
agent.ts already distinguishes absent from [] for settingSources. The spec doesn't say what the preset does when the host loads no settings. Check that the preset, with settingSources: [], doesn't pull in project CLAUDE.md or user settings the host meant to exclude. If it doesn't, add one line to the docs. If it does, that needs to be in BR-1.

4. A type-level breaking change is hidden under "minor".
Widening systemPrompt from string to the SDK union is additive for callers. It is breaking for anyone who reads the option back as a string, including wrappers that spread or concatenate it. A grep across the repo found nothing, but the changeset should say the type widened, and not only that the default changed.

5. The "Follow-ups" leave two in-repo callers silently degraded.
The spec says Shift Manager's harness and one devforce goal keep an empty record under D2 and are "their owners' call". Because the default is changing, I'd rather those hosts be moved in the same PR to append. It is a one-line diff each, and leaving them means this PR ships a known regression in the repo's own labs. If their owners must decide, the PR should name them and link a filed issue, not a note to the coordinator.

6. Smaller, and not blocking.

  • The "Settled" section says the POC shows what the SDK sends. The SDK's default-for-absent behaviour could change in a newer SDK, and PLAN already says S2 becomes a no-op in that case. Good. A V2 case that pins the SDK version's actual absent behaviour would catch a silent flip later.
  • harness-manager/src/ask.ts documents the harness's option list as fixed. That comment needs no change, but check it still reads true once systemPrompt is a union.

On the architecture lens: nothing here calls for a refactor. The default is decided in one place (the query options in agent.ts), which is the right place. I'd leave workspace.ts and capability.ts alone beyond type forwarding. This is a change that fits a single small PR.

Items 1, 2 and 5 are the ones I'd have the implementing agent resolve before building.


Generated by Claude Code

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Problem

In-process Claude Code runs start with an empty system prompt while the CLI uses Claude Code’s own, so plan/to-do tooling never fires unless hosts patch prompts themselves.

Verdict

Approve direction. D1 (omit → SDK claude_code preset) plus D2 (string still replaces; preset + append for additions) is the smallest honest fix: one branch at query-option build time, reuse the Agent SDK’s existing preset shape (same philosophy as sandbox), and leave the recorder alone so the plan stays the agent’s account. The rejected paths (recorder-injected plan line, per-host job text, planGuidance flag) would be simpler on paper but recreate “whose plan is this?” and ER-11 downstream patching.

The spec set is much heavier than the implementation (~784 lines for a one-line default). That is not wrong for epic closure, but it is where /simplify has the most leverage before implementation lands.

What went further than necessary (optional tightening)

  1. Control wording — “FAIL on at least two plan rows” reads like the control should have two rows. You mean “does not meet the PASS signal (fewer than two rows / none).” Same phrase in SPEC.md and PLAN.md VG; easy to mis-implement.
  2. Omitted vs main vs GOAL_CONTROL — POC shows omitted and "" both become [""] today, but they are different host inputs. One sentence on which arm main exercises (omitted default) vs the control env ("" escape hatch) would prevent someone from running only one path.
  3. Goal bar — 3/3 PASS, second held-out job, 2/2 control, FAIL-before-PASS on main, all on a real signed-in host is expensive for a wiring fix already backed by Aug 19 + model-free POC + V2 BR-1. Consider collapsing to BUSINESS-RULES as canonical numbers and dropping the second job unless FIX-1907 closure truly requires it.
  4. BR-2–BR-5 — five “forward verbatim” rows could be one rule plus BR-1 as the special case.
  5. Settled / POC — “planted fault turns the check red” is not in run.mts (only omitted/preset assertions). Either add a FIX1185_PLANT_FAULT hook or soften that sentence.
  6. Types (implement-time) — PLAN’s “forward SDK union” is right; prefer importing or aliasing the SDK type / unknown on the query bag (like sandbox) over enumerating every shape in V1 unless you want a maintenance copy.

Alternatives considered (not recommending over this spec)

Approach Tradeoff
Default-only PR, defer type widen Ship D1 first with systemPrompt?: string; add SDK union in a follow-up. Smaller spec surface; Shift Manager stays on string without typed append until then.
Doc + recordWork one-liner Smallest code; records instructions we asked for, not CLI parity. Correctly rejected in D1.
Treat every string as append Fixes one-line Shift Manager without migration; breaks hosts that intentionally replace with a full prompt. Correctly rejected in D2.

Evidence

Ran pnpm tsx specs/issues/FIX-1185/poc/what-the-sdk-sends/run.mts — omitted and "" → systemPrompt: [""], preset+append → appendSystemPrompt only (HOLDS).

For implementation

  • Resolve default in one place before queryOptions (guardrail already says this). Align with existing conditional spreads: POC’s omitted SDK key may differ from systemPrompt: undefined in the object — match what the stub test asserts.
  • Follow-ups (Shift Manager / devforce one-line strings) are appropriately out of scope; flagging to epic coordinator is enough.

No changes requested for merge of this spec PR; the inline notes are polish I’d fold before or during implementation.

Open in Web View Automation 

Sent by Cursor Automation: Review For Best Approach

| **Signal** | On each of 3 runs, the plan record holds at least two rows, and at least one reaches `completed` |
| **Input** | A held-out job of three or more steps whose prompt names no tool and says nothing about planning. A different job of that shape must pass too |
| **Anti-game** | Never put a tool name or "plan" in the job. Never count `tool_use` items or read the closing message. Never pass a prompt string in the PASS arm |
| **Control that must fail** | `GOAL_CONTROL=empty-prompt` (`systemPrompt: ""`), and today's `main`. Both must FAIL on *at least two plan rows*, on 2 of 2 runs, and the PR shows it before the PASS |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads as “the control must produce ≥2 plan rows.” I think you mean the control fails the same bar as PASS (i.e. does not reach two rows / none). Suggest: “must not meet the PASS signal (fewer than two rows, or none)” — same fix in PLAN.md VG row.

|---|---|
| **Goal check** | `goals/claude-code-harness/it-keeps-its-own-plan/` · Claude Code's default model on a signed-in local host · run by the implementer at completion · verdict in the implementation PR |
| **Signal** | On each of 3 runs, the plan record holds at least two rows, and at least one reaches `completed` |
| **Input** | A held-out job of three or more steps whose prompt names no tool and says nothing about planning. A different job of that shape must pass too |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A second held-out job that must pass is a lot of real-model cost on top of 3/3 + 2/2 control + pre-PASS on main. Unless epic closure requires it, consider demoting to “implementer may use a second job if flaky” or dropping — Aug 19 + POC + V2 BR-1 already anchor the premise.

model-free. Driving the real SDK `query()` with a stubbed agent process, the first message
it sends carries `systemPrompt: [""]` when none is given, the same as `""`. With the
`claude_code` preset it sends no custom prompt and only the appended text, so the agent
process keeps Claude Code's own. A planted fault (the omitted arm sent as the preset) turns

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Settled claims a planted fault turns the POC red; run.mts only sets refuted from omitted/preset arms. Either add an env-gated fault injection (nice for CI) or reword to “the assertions refute if omitted is not [""] or preset sends systemPrompt.”

| ID | Package · role | Change | Rules |
|---|---|---|---|
| S1 | `claude-code` · the agent options type and the SDK query-options type | `systemPrompt` takes the SDK's own union (string, string array, the `claude_code` preset with optional `append`), forwarded verbatim (D2) | BR-2 BR-4 BR-5 |
| S2 | `claude-code` · where the block builds the SDK query options | `undefined` becomes the preset with nothing appended (D1). Every other value, `""` included, passes through untouched | BR-1 BR-3 BR-7 BR-8 BR-9 |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

S1 widening to the full SDK union is the right long-term shape (D2 + sandbox precedent). For implementers: if V1 becomes a hand-copied union, it will drift — consider Parameters<typeof query>[0]['options']>['systemPrompt'] style alias, or document unknown on the internal query bag only with assignability smoke tests for the shapes you document publicly.

|---|---|---|
| V1 | S1 | Type test: each SDK prompt shape is accepted by the block and the capability; a non-prompt object is a type error |
| V2 | S2 | Agent spec: the options the stubbed SDK receives carry the preset when none is given (BR-1); the string, `""`, the preset and an array pass through byte-identical (BR-2 to BR-5). Red first: on today's `main` the BR-1 case fails |
| V3 | S2 | The second path (BP-035): the same assertions on a detached resumed run, an in-session run, `recordWork` off, and through the capability (BR-6 to BR-9) |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

V2 + V3 as separate checklist rows duplicate the same assertions across detached / in-session / recordWork off / capability. The fix is one builder — a single parameterized table in the agent spec (or one BP-035 row: “all entry paths”) would cut plan noise without weakening coverage.


Nothing here is fatal. A prompt shape the SDK rejects fails the run the way any bad SDK option
does today, as a `ClaudeAgentRunError`. A run that plans nothing is not an error: the empty record
is the honest answer.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BR-12 is “existing recorder tests” — not in PLAN’s V1–VG matrix and not owned by this issue. Consider moving to SPEC “What stays as it is” so acceptance criteria stay BR-10/11 only.

@jhoffner
jhoffner merged commit 9825241 into main Oct 12, 2026
16 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 02fea6c14e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

|---|---|
| Drive one goal run through the CLI to exercise the plan half once (the issue's second option) | Proves the recorder on a path Kitchen Sink and every host don't use. The epic needs the SDK path to fill |
| Put the plan line in each host's job prompt | Shown to work, but every host copies a line that only exists to undo our default |
| Add `TaskCreate` and `TaskUpdate` to `allowedTools`, or raise `maxTurns` | Measured: no change on 8 runs |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep task tools available on newer Claude models

On Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models, changing only the system prompt cannot satisfy BR-10: the locked Agent SDK 0.3.234 includes the 0.3.233 change that removes the task-tracking tools from the default surface unless they are named through tools, allowedTools, or the environment override. The eight-run result with a blank prompt does not rule out needing both the preset prompt and tool exposure, and the proposed documentation example also omits these tools from its allowlist. Revise the design to retain the task tools or explicitly limit the supported model set. Agent SDK 0.3.233 changelog.

Useful? React with 👍 / 👎.

Comment on lines +75 to +76
if (value === OMITTED && JSON.stringify(req.systemPrompt) !== JSON.stringify([""])) refuted = true;
if (typeof value === "object" && req.systemPrompt !== undefined) refuted = true;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Make every claimed POC arm affect the exit status

If explicit "" stops producing systemPrompt: [""], or the preset silently drops its appended text, this POC still prints HOLDS and exits 0 because it checks neither result. Those are the behaviors used as BR-3's control and BR-4's public contract, so assert the expected wire shape for all three arms before treating this as settled evidence.

Useful? React with 👍 / 👎.

|---|---|
| **Goal check** | `goals/claude-code-harness/it-keeps-its-own-plan/` · Claude Code's default model on a signed-in local host · run by the implementer at completion · verdict in the implementation PR |
| **Signal** | On each of 3 runs, the plan record holds at least two rows, and at least one reaches `completed` |
| **Input** | A held-out job of three or more steps whose prompt names no tool and says nothing about planning. A different job of that shape must pass too |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Exercise the second held-out job in the goal plan

The acceptance input requires a different job of the same shape to pass, but S4 defines only one held-out fixture and VG only repeats runs 3 of 3. An implementation can therefore satisfy every planned check by running the same fixture three times without proving this explicit generalization requirement; define the second fixture and its run allocation, or remove this requirement.

Useful? React with 👍 / 👎.

| The default is decided in one place, where the query options are built | The capability and every resolver path reach the SDK through it. A second place is how one path keeps the blank prompt (tenet 5) |
| Forward the SDK's shape; never translate or validate it | The package forwards `sandbox` the same way. A copy of the SDK's union drifts the day the SDK adds a field |
| The recorder is not touched | D1 rests on the plan being the agent's own. Any instruction the recorder adds would make the record ours |
| The goal check reads the plan record from state, through the resource route | The issue's verification asks for rows read back from state. A count of tool calls in the stream passes while the record stays empty |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Scope goal reads to the current request

When the goal reuses a session to cover repeated or resumed runs, reading the session-scoped observed-plan collection without the current request's prefix also returns rows from earlier attempts. That can let runs 2 and 3 satisfy the row threshold using run 1's plan, corrupting the 3-of-3 result. Require a fresh session per attempt or query observed-plan/<escaped requestId>/ and assert only that namespace.

Useful? React with 👍 / 👎.

@vercel

vercel Bot commented Oct 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Oct 12, 2026 7:03pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 12, 2026 7:03pm UTC
flow-state-dev-ui Ignored Ignored Oct 12, 2026 7:03pm UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants