feat: interactive CLI, slug-based orgs, evals support#7
Open
feat: interactive CLI, slug-based orgs, evals support#7
Conversation
- Enhanced `.env.example` with clearer API base URL instructions for US and EU regions. - Updated `.gitignore` to simplify environment file exclusions and added a catch-all for `.env.*`. - Removed obsolete `.vapi-state.dev.json` and `.vapi-state.prod.json` files. - Added new scripts to `package.json` for setup, apply, push, pull, call, and cleanup operations. - Introduced `searchableCheckbox.ts` for improved user input handling in CLI prompts. - Cleaned up empty directories and `.gitkeep` files across various resource paths.
- Replaced existing push and pull scripts with new interactive versions (`push-cmd.ts` and `pull-cmd.ts`) that allow users to select organizations and resources interactively. - Added a new `interactive.ts` file to handle organization detection and resource selection. - Updated `package.json` scripts to point to the new command files. - Enhanced `searchableCheckbox.ts` to support a back option in the interactive prompts. - Refactored `setup.ts` to integrate the new interactive features.
- Introduced `apply-cmd.ts`, `call-cmd.ts`, and `cleanup-cmd.ts` as entry points for their respective commands, allowing for organization slug detection and interactive modes. - Updated `apply.ts`, `call.ts`, and `cleanup.ts` to support new command structures and improved error handling for invalid org names. - Enhanced `interactive.ts` to facilitate user interaction for selecting organizations and confirming actions. - Added support for eval resources across various scripts, including updates to state management and resource handling in `push.ts`, `pull.ts`, and `delete.ts`. - Refactored argument parsing and validation to ensure consistency across commands.
…ive setup - Replaced existing command scripts with new command files (`apply-cmd.ts`, `call-cmd.ts`, `cleanup-cmd.ts`) for improved organization and functionality. - Removed outdated scripts from `package.json` to streamline command usage. - Enhanced the README to introduce an interactive setup process, detailing the steps for first-time users and clarifying command functionalities. - Updated command descriptions to reflect the new interactive capabilities and improved user experience.
roshan-vapi
approved these changes
Apr 10, 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
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.
Summary
pull,push,apply,call,cleanupnow prompt for org selection and offer a searchable multi-select resource picker when run without arguments. Direct mode (npm run push -- <org>) still works for scripting/CI.my-org,production) instead of hardcoded environments. Each org gets its own.env.<org>,.vapi-state.<org>.json, andresources/<org>/directory. An interactivenpm run setupwizard handles first-time configuration.evalsthroughout the pipeline: types, state, pull, push, delete, resource loading, and the eval runner (npm run eval).Details
npm run setup— interactive wizard: API key validation with region auto-detection, org naming, searchable resource picker with dependency detectionsearchableCheckbox— custom@inquirer/coreprompt with type-to-search, space-to-toggle, Ctrl+A, grouped display, ESC-to-go-back-cmd.tswrappers detect whether a slug arg is present — if yes, forward to core script; if no, enter interactive modeshouldApplyResourceTypein push.ts now skips resource types not relevant to the selected file paths (less noise)push:dev,pull:stg:force, etc.) — replaced by 7 universal commandsTest plan
npm run setup— configure a new org end-to-endnpm run pull— interactive org selection, resource picker with ✔ local markers, ESC to go backnpm run push— interactive with git status indicators, selective push of individual filesnpm run push -- <org>— direct mode still worksnpm run push -- <org> resources/<org>/assistants/foo.md— single-file push only loads relevant resource typenpm run apply— interactive apply (pull → push)npm run call— interactive assistant/squad picker from state filenpm run cleanup— interactive dry-run then confirmnpm run eval -- <org> -s <squad>— eval runner works with slug-based envnpm run build— clean compile (no new type errors)Made with Cursor