# code-cli mit Homebrew, Nix, pacman installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für code-cli in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:code-cli
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install code-cli
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#code
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/co/code/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S code
```

  Evidenz: Arch Linux sync databases: code from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

## Paketfakten

- **Paketschlüssel:** brew:code-cli
- **Paketmanager:** Homebrew
- **Version:** 1.131.0
- **Quellzusammenfassung:** Command-line interface built-in Visual Studio Code
- **Homepage:** <https://code.visualstudio.com>
- **Repository:** <https://github.com/microsoft/vscode>
- **Zuletzt aktualisiert:** 2026-07-29T15:20:26Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- code (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.131.0
## Projektgeschichte und Nutzung

The Visual Studio Code CLI is the command-line surface of VS Code, exposed as the `code` command. It lets users launch the editor, open files and folders, manage extensions, inspect status, and create remote tunnels from a terminal.

### Projektgeschichte

VS Code was announced in 2015 as Microsoft's cross-platform editor. Later that year the November 2015 Beta release made the Code OSS project open source and added extension support. The `code` command became part of the product's developer workflow: the official CLI docs describe it as built in and document editor launch, file navigation, extension management, chat, diagnostics, and tunneling.

### Adoptionsgeschichte

Microsoft's 1.0 announcement reported 2 million installs and more than 500,000 monthly active developers by April 2016. The CLI followed VS Code's adoption because `code .` became the normal bridge between shell workflows and the editor. The input also records package-manager distribution for the CLI through Homebrew, Nix, and pacman.

### Wie es verwendet wird

Common usage includes `code .` to open the current directory, file arguments to open or create files, `--install-extension` and `--list-extensions` for extension workflows, `--user-data-dir` for isolated instances, and `code tunnel` for remote tunnel setup.

### Warum Paket-Nerds sich dafür interessieren

For package-manager users, `code-cli` matters because it splits the terminal command from the desktop app story. A working `code` executable is what lets editors participate in Unix-style workflows: scripts can open files, shells can jump into projects, and remote machines can expose VS Code access without starting from a GUI installer.

### Zeitleiste

- 2015: Visual Studio Code announced at Build.
- 2015: November Beta made VS Code open source and added extensions.
- 2016: Visual Studio Code 1.0 released with reported 2 million installs and 500,000 monthly active developers.
- 2026: Official CLI docs cover built-in `code` command workflows, chat subcommands, and remote tunnels.

### Related projects

- Related projects and surfaces include the microsoft/vscode Code OSS repository, the VS Code desktop product, VS Code Insiders, Remote Tunnels, the extension marketplace, and downstream open-source builds such as Code OSS packages.

### Quellen

- <https://code.visualstudio.com/docs/configure/command-line>
- <https://code.visualstudio.com/docs/configure/settings>
- <https://code.visualstudio.com/blogs/2016/04/14/vscode-1.0>
- <https://code.visualstudio.com/updates/vNovember>
- <https://github.com/microsoft/vscode>


## Sicherheitshinweise

Für code-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Linux: ~/.config/Code/User/settings.json, .vscode/settings.json
- macOS: ~/Library/Application Support/Code/User/settings.json, .vscode/settings.json
- Windows: %APPDATA%\Code\User\settings.json, .vscode\settings.json
## Andere Paketmanager-Einträge

- Nix - code: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/co/code/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - code - 1.131.0-1: installed executable or alias match | Arch Linux sync databases: code from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | The Open Source build of Visual Studio Code (vscode) editor | https://github.com/microsoft/vscode


## Combined YAML source

View the package source record on GitHub. [combined/code-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/code-cli.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
