base on A CLI/TUI that simplifies launching VSCode projects, with a focus on dev containers # vscli [](https://choosealicense.com/licenses/mit/) [](https://github.com/michidk/vscli/actions) A CLI/TUI which makes it easy to launch [Visual Studio Code](https://code.visualstudio.com/) (vscode) projects, with a focus on [dev containers](https://containers.dev/).  Read [here](https://blog.lohr.dev/launching-dev-containers) about the journey of reverse engineering Microsoft's dev container CLI in order to make this. ## Features - A shorthand for launching vscode projects (to be used like the `code` command but with dev container support) - Detects whether a project is a [dev container](https://containers.dev/) project, and launches the dev container instead - Supports [multiple dev containers](https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_75.md#folders-with-multiple-devcontainerjson-files) in the same project - Supports the [insiders](https://code.visualstudio.com/insiders/) version of vscode - Tracks your projects and allows you to open them using a CLI-based UI ## Installation [](https://repology.org/project/vscli/versions) [](https://github.com/michidk/homebrew-tools/blob/main/Formula/vscli.rb) ### [Cargo](https://doc.rust-lang.org/cargo/) Install [vscli using cargo](https://crates.io/crates/vscli) on Windows or Linux: ```sh cargo install vscli ``` ### [Homebrew](https://brew.sh/) Install [vscli using homebrew](https://github.com/michidk/homebrew-tools/blob/main/Formula/vscli.rb) on Linux or Mac: ```sh brew install michidk/tools/vscli ``` ### [Chocolatey](https://chocolatey.org/) Install [vscli using Chocolatey](https://community.chocolatey.org/packages/vscli) on Windows: ```sh choco install vscli ``` ### [Winget](https://learn.microsoft.com/en-us/windows/package-manager/winget/) Install [vscli using winget](https://github.com/microsoft/winget-pkgs/tree/master/manifests/m/michidk/vscli) on Windows: ```sh winget install vscli ``` ### Additional steps You can set a shorthand alias for `vscli` in your shell's configuration file: ```sh alias vs="vscli open" alias vsr="vscli recent" ``` ## Usage ### Commands After installation, the `vscli` command will be available: ``` Usage: vscli [OPTIONS] <COMMAND> Commands: open Opens a dev container recent Opens an interactive list of recently used workspaces help Print this message or the help of the given subcommand(s) Options: -s, --history-path <HISTORY_PATH> Overwrite the default path to the history file [env: HISTORY_PATH=] -d, --dry-run Whether to launch in dry-run mode (not actually open vscode) [env: DRY_RUN=] -v, --verbose... More output per occurrence -q, --quiet... Less output per occurrence -h, --help Print help -V, --version Print version ``` #### Open Dev Containers Opens a dev container. ``` Usage: vscli open [OPTIONS] [PATH] [ARGS]... Arguments: [PATH] The path of the vscode project to open [default: .] [ARGS]... Additional arguments to pass to vscode [env: ARGS=] Options: -b, --behavior <BEHAVIOR> Launch behavior [default: detect] [possible values: detect, force-container, force-classic] -s, --history-path <HISTORY_PATH> Overwrite the default path to the history file [env: HISTORY_PATH=] -c, --config <CONFIG> Overwrites the path to the dev container config file [env: CONFIG=] -d, --dry-run Whether to launch in dry-run mode (not actually open vscode) [env: DRY_RUN=] -n, --insiders Whether to launch the insider's version of vscode [env: INSIDERS=] -v, --verbose... More output per occurrence -q, --quiet... Less output per occurrence -h, --help Print help (see more with '--help') ``` #### Recent UI Opens an interactive list of recently used workspaces. ``` Usage: vscli recent [OPTIONS] Options: -s, --history-path <HISTORY_PATH> Overwrite the default path to the history file [env: HISTORY_PATH=] -d, --dry-run Whether to launch in dry-run mode (not actually open vscode) [env: DRY_RUN=] -v, --verbose... More output per occurrence -q, --quiet... Less output per occurrence -h, --help Print help ``` The following keybindings are available: ##### Keybindings | Key/Key Combination | Action | Description | | ------------------------------- | --------------------- | -------------------------------------- | | `Esc`, `Ctrl+Q` or `Ctrl+C` | Quit | Exits the application. | `Down` or `Ctrl+J` | Select Next | Moves to the next selectable item. | | `Up` or `Ctrl+K` | Select Previous | Moves to the previous selectable item. | | `KeypadBegin` or `Ctrl+1` | Select First | Selects the first item. | | `End` or `Ctrl+0` | Select Last | Selects the last item. | | `Enter` or `Ctrl+O` | Open Selected | Opens the currently selected item. | | `Delete`, `Ctrl+R`, or `Ctrl+X` | Delete Selected Entry | Deletes the currently selected item. | Note: If an input does not match any of the defined keybindings, it is treated as part of a search input. ##### Launch Behavior There are three launch behaviors: - `force-classic`: Launch vscode without a dev container - `force-container`: Launch vscode with a dev container, error if no dev container is found - `detect`: Detect whether the project is a dev container project, and launch the dev container if it is ##### Detection Algorithm The detection algorithm determines which dev container config to launch. - First, check whether a dev container config was specified via the `--config` flag -> launch it - Then loads the first dev container it finds - If more than one exists -> show a interactive list of dev containers and let the user select one - If one exists -> launch it - If none exists -> launch vscode normally without a dev container ### Examples #### Launching a project You can launch a project using the default behavior: ```sh vscli open # open vscode in the current directory vscli open . # open vscode in the current directory vscli open /path/to/project # open vscode in the specified directory ``` The default behavior tries to detect whether the project is a [dev container](https://containers.dev/) project. If it is, it will launch the dev container instead - if not it will launch vscode normally. You can change the launch behavior using the `--behavior` flag: ```sh vscli open --behavior force-container . # force open vscode dev container (even if vscli did not detect a dev container) vscli open --behavior force-classic . # force open vscode without a dev container (even if vscli did detect a dev container) ``` When you open a project containing more than one dev container config, you will be prompted to select one:  You can launch the insiders version of vscode using the `--insiders` flag: ```sh vscli open --insiders . # open vscode insiders in the current directory ``` Additional arguments can be passed to the `code` executable, by specifying them after `--`: ```sh vscli open . -- --disable-gpu # open vscode in the current directory without GPU hardware acceleration ``` Read more about the `code` flags, by executing `code --help`. #### CLI UI You can open a CLI-based user interface to display a list of recently opened projects using the `recent` command: ```sh vscli recent # open the CLI-based UI to select a recently opened project to open ``` ", Assign "at most 3 tags" to the expected json: {"id":"3034","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"