guides(paseo): the comparison table has no hosted-runtime row - #103
Merged
WhiteWorld merged 1 commit intoAug 20, 2026
Merged
Conversation
The 'How to Choose' table only has tools where code runs on a machine you own, but the 'Not a fit' section right below it calls out people who cannot accept 'the machine must be online'. Nothing in the table answers that case. Adds VibeKit as the hosted-runtime contrast in both mirrors, plus one 'How to pick' bullet that names the trade-off honestly: you stop keeping a machine awake, and you give up the local environment Paseo exists to protect. Disclosure: I work on VibeKit. It is already in your mobile-ai-coding-tools-2026 guide under both 'remote-control' and 'runtime from the phone'.
|
@609NFT is attempting to deploy a commit to the ww's projects Team on Vercel. A member of the Team first needs to authorize it. |
WhiteWorld
added a commit
that referenced
this pull request
Aug 20, 2026
* data: update Windsurf (Devin consolidation, pricing moved to devin.ai) and Codex plan structure (Plus/Pro 5x/Pro 20x, Codex App positioning) * data: fix Windsurf typo in windsurf.yaml Chinese note * data: add vibekit.yaml entry (persistent hosted agent runtime) - governance fix for PR #103 * data: vibekit - remove missing logo ref, add governance fields (review/due/confidence) --------- Co-authored-by: editor <editor@codepick.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The How to Choose Among Similar Tools table currently has one property in common across every row: the code runs on a machine you own or self-host. Directly below it, Not a fit says:
Nothing in the table answers that reader. This adds the hosted-runtime row so the comparison covers the case the guide itself raises.
What changed (both mirrors, one row + one bullet each):
vibekit-agent link, so "where code runs" is provider container by default and your machine in paired mode.I deliberately did not touch the Paseo-favouring bullets. Paseo wins the open-source, keep-my-env case and the table should keep saying so.
On category fit: your own mobile-ai-coding-tools-2026 guide already places VibeKit in both "remote-control local or VPS-based coding agents" and "open a real development runtime from the phone", so it is in the same lane the table is drawing.
Disclosure: I work on VibeKit. Facts are from vibekit.bot and docs.vibekit.bot; happy to cut the bullet and keep only the row, or reword anything that reads as too promotional.
Checks run locally on this branch:
npm run build,npm run check:seo,npm run content:check -- --strict(0 errors, 0 warnings),npm run content:check:baseline— all green.