Skip to content

deploy(vera): pin the cloud model while smart is pulled #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mabry1985 merged 1 commit into from
Jul 23, 2026
Merged

deploy(vera): pin the cloud model while smart is pulled #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions deploy/vera.langgraph-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,20 @@ a2a:
- "review https://github.com/protoLabsAI/protoAgent/pull/64"
- "what's your verdict on PR #42 in protoLabsAI/qaEngineer?"

# Model — pinned to the CLOUD lane 2026-07-23 while the local `smart` backend
# (:8041) is pulled. Model settings are normally HOST-scoped (ADR 0047) and this
# agent layer deliberately outranks the box default, because the default
# `protolabs/reasoning` is a gateway ALIAS to `protolabs/smart` — leaving it unset
# would take the review panel down with the backend it points at.
#
# protolabs/cloud -> deepseek-v4-pro: 1M context, so the panel's ~37k-token finder
# prompts fit with room to spare (the previous local lane capped at 32k total,
# which is what exhausted the panel on large diffs).
#
# Revert to the host default (delete this block) once smart is back.
model:
name: protolabs/cloud

plugins:
enabled: [workflows, github, pr-reviewer]

Expand Down
Loading