Skip to content

[RELEASE] free-plan runtime UX: locked runtimes never active + per-screen chip (#2351)#2352

Merged
vivekchand merged 1 commit into
mainfrom
release/runtime-chip-flow
May 30, 2026
Merged

[RELEASE] free-plan runtime UX: locked runtimes never active + per-screen chip (#2351)#2352
vivekchand merged 1 commit into
mainfrom
release/runtime-chip-flow

Conversation

@vivekchand
Copy link
Copy Markdown
Owner

@vivekchand vivekchand commented May 30, 2026

Publishes #2351 (already merged) to PyPI.

  • Flow tab no longer renders a locked runtime (Claude Code on free) as an active coding-agent topology — falls back to the default OpenClaw diagram.
  • New per-screen runtime chip (bottom-right, every tab) naming the current runtime, as a second switch point mirroring the header dropdown (locked → upgrade).

After merge: release-on-merge bumps + publishes; then I bump the cloud pin so the served app.js carries it.

🤖 Generated with Claude Code

@vivekchand @claude
[RELEASE] free-plan runtime UX: locked runtimes never active + per-sc…
b33c228 
…reen chip (carries #2351)

Publishes #2351 to PyPI: Flow no longer renders a locked runtime (Claude Code
on free) as active; new per-screen runtime chip as a 2nd switch point.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vivekchand vivekchand merged commit ec60466 into main May 30, 2026
17 checks passed
@github-actions github-actions Bot mentioned this pull request May 30, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@vivekchand