Repository navigation
CLI: prospecting plan command - #42
Merged
Merged
Conversation
The API now leaves a plan's contact engine, company check engine or
search provider unselected when an organization has several providers
and none is the default, and approve returns 409 until one is picked.
The SDK already wraps PATCH /prospecting/runs/{id}/plan, but CLI users
had no way to reach it, so such a run could not be approved from the
CLI. `prospecting plan` forwards every ProspectingPlanSettings field and
sends only the flags passed, so it also covers resizing and spend
limits without restarting the run.
The plan tests' responses had no plan_version, so the model's default of 1 hid whether the new version reached stdout; users need that value for their next approve.
yudelevi
force-pushed
the
feat/cli-prospecting-plan
branch
from
October 7, 2026 23:22
4ef40ba to
cf9ae95
Compare
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.
discolike prospecting plan RUN_ID --plan-version Nwrappingupdate_plan, so CLI users can pick an engine the plan left unselected (selected: null) and approve; the API returns 409 on approve until one is picked.The PR appears safe to merge, with a non-blocking improvement to the returned-version test.
Fix with agent prompt
Summary
Adds
prospecting planto change engines, counts, deliverables, goals, and spending limits before approval.plan_versionand sends only supplied flags.Reviews (1) · Last reviewed commit: "Add prospecting plan command to the CLI" · Reviewed by Greptile