improvement(ui): use chip fields in workflow search and replace

[BillLeoutsakosvl346]

Summary

• Use ChipInput for workflow search and text replacement, and ChipCombobox for resource replacement.
• Keep input refs, keyboard handling, search options and replacement callbacks; adopt standard chip corners, field height and theme-aware surface.

Type of Change

• Refactor / maintainability improvement

Testing

• Full workspace type checks, lint, repository audits (including import and API validation), generators and docs checks pass.
• External source comparison confirms caller logic and content are unchanged.
• Before/after browser fixtures cover the changed component's styling and interactions. Search-and-replace intentionally adopts chip field styling. These are isolated fixtures, not full authenticated product flows.
• Relevant existing tests pass. No landing-page changes or audit tooling included.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Sep 22, 2026 8:42pm UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no outstanding correctness, security, or repository-rule issues were identified.

Summary

This PR adopts shared chip-styled controls across workflow search and replacement, execution refresh, and chat error recovery while preserving the existing interaction callbacks and state.

• Uses ChipInput for workflow search and text replacement.
• Uses ChipCombobox for compatible resource replacement.
• Uses Chip for replacement, refresh, and recovery actions.
• Applies the shared centered-alignment API instead of overriding chip typography.

_{Reviews (3) · Last reviewed commit: "fix(ui): use shared centered chip conten..."}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[BillLeoutsakosvl346]

Before / after visual comparison

Search fields reuse ChipInput: 34px → 30px high, 4px → 8px corners, shared text color and dark fill. Existing editing logic is retained.

Left = before; right = after.

Rendered component fixtures with application CSS and local data, rather than authenticated product-page screenshots. These are representative visual examples, not end-to-end behavior coverage.

Current PR head checked at posting: 39573f375f.

Additional theme/state comparisons

[BillLeoutsakosvl346]

@greptile

[BillLeoutsakosvl346]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 4 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[BillLeoutsakosvl346]

@greptile

[BillLeoutsakosvl346]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 4 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}