Repository navigation
feat(paseo-daemon): register token repositories as projects; preselect agent models - #181
Merged
Merged
Conversation
…t agent models A paired Paseo app showed no projects or file trees until the developer cloned and added each repository by hand, and every Buzz agent provider asked for a model although the bridge offers none. At startup, paseo-workspaces now clones each GITHUB_READ_TOKEN_REPOSITORIES entry once with paseo-code and registers it with paseo project create, in the background and bounded; and each Buzz provider declares one preselected model. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tee8z <tee8z@protonmail.com>
|
Warning Review limit reached
This review includes 7 billable files and costs up to $1.75.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 17 minutes for your next included review. View limit details
|
This was referenced Nov 12, 2026
thebrandonlucas
approved these changes
Nov 13, 2026
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
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.
Summary
Two fixes from the first live Paseo daemon test, where starting work felt awkward:
paseo-workspacesclones eachGITHUB_READ_TOKEN_REPOSITORIESentry once and registers it withpaseo project create. The repositories appear as projects with file trees.isDefault: true, so the picker is preselected.How it works
workspaces.mjs(installed as/usr/local/bin/paseo-workspaces) runs in the background from the entrypoint, after the keypair is removed from the environment, and never blocks startup.paseo project ls --jsonat most 60 times until the daemon answers.~/code/<owner>/<repo>is absent, it runspaseo-code clone, which uses the existing read-only helper, credential scoping and deadline. If the directory isn't registered yet, it runspaseo project create <dir>.ProviderOverride.models. The generic ACP provider callsunstable_setSessionModelonly when the agent advertises models; the bridge advertises none, so the declaration only preselects the picker.Testing
node voltage/images/paseo-daemon/test-workspaces.mjscovers:Falsified: removing the registered-project skip fails it.
Ran the full image contract locally:
docker buildplusbash voltage/images/paseo-daemon/test-image.sh paseo-daemon:local, ending inPASS: Paseo daemon image contract. It now asserts that the Brokkr provider ships one preselected model labelledBrokkr.Dockerfile.dockerignoreallows the new helper.Not yet exercised against a live daemon with real repositories. That happens after this image is promoted to
paseo_daemon_image, and needs the developer's Paseo GitHub read token.🤖 Generated with Claude Code