# Installer hookdeck avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de hookdeck pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:hookdeck
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install hookdeck
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:hookdeck
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.3.1
- **Résumé source:** Forward webhook events from Hookdeck to a local server
- **Page d'accueil:** <https://hookdeck.com>
- **Dépôt:** <https://github.com/hookdeck/hookdeck-cli>
- **Dernière mise à jour:** 2026-07-30T12:46:44Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- hookdeck (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 2.3.1
## Historique du projet et usages

Hookdeck CLI is the command-line companion to Hookdeck's webhook/event-gateway platform. It began from the practical local-development problem of receiving third-party webhook traffic on a developer machine, then expanded into a broader CLI for event inspection, replay, project selection, connection management, and Event Gateway resource operations.

### Historique du projet

The official README describes the original center of gravity: forward webhooks and other events to a local web server using free, permanent event URLs, while preserving event history for inspection, replay, and testing. The docs explicitly position the CLI as an alternative to ngrok-style tunnels for webhook development.

The generated command reference shows the project evolving beyond `listen`. It includes authentication, project management, local development, sources, destinations, connections, transformations, events, requests, attempts, metrics, and a Gateway MCP command group. That puts the CLI in both local-development and infrastructure-management roles.

The configuration model also matured into profile-based TOML files. Global flags include `--hookdeck-config`, defaulting to `$HOME/.config/hookdeck/config.toml`, and login/project commands can save local state in `.hookdeck/config.toml` for repository-scoped workflows.

### Historique d'adoption

Hookdeck CLI is distributed through npm, Homebrew, Scoop, direct Linux archives/packages, and Docker. That packaging spread is important for a webhook tool because teams use it across macOS laptops, Windows development machines, Linux CI workers, and containerized test jobs.

The docs and README frame the CLI as part of a team workflow rather than a one-off tunnel: event history persists between sessions, teammates can inspect or replay events, and the CLI can manage Event Gateway resources for CI/CD and testing.

### Modes d'utilisation

For local development, `hookdeck listen` forwards incoming events for one or more Hookdeck sources to a local port or URL. Interactive mode provides a terminal UI with event history and request/response inspection, while compact and quiet output modes support scripts and CI logs.

For platform management, command groups operate on projects, sources, destinations, connections, transformations, events, requests, attempts, and metrics. `hookdeck login` persists credentials; `hookdeck project use --local` pins project selection into a repository-local config file.

The CLI also supports agent-oriented workflows through `hookdeck gateway mcp`, exposing Event Gateway capabilities to MCP-compatible clients.

### Pourquoi les passionnés de paquets s'y intéressent

Hookdeck CLI sits in a recognizable package-manager category: developer tunnel tools that become operational CLIs. Package maintainers care about it because it ships across several distribution channels and because a single executable touches credentials, local config, browser login, terminal UI behavior, and CI automation.

It is also a useful example of a vendor CLI that moved from a narrow local webhook listener into a control plane for platform resources. That expansion changes how package users think about upgrades: new releases can affect both localhost development and infrastructure automation.

### Chronologie

- 2021: Hookdeck-authored local-development material describes the CLI as a webhook proxy and ngrok alternative.
- 2024: Official connection-management guide documents CLI-driven Infrastructure as Code, CI/CD, and production automation workflows for CLI v1.2.0 and later.
- 2026: Generated CLI reference covers local development, Event Gateway resource management, metrics, and MCP integration.

### Related projects

- ngrok and other HTTP tunnel tools are related because Hookdeck positions the CLI as an alternative for webhook development.
- Hookdeck Console and Hookdeck Event Gateway are the platform surfaces the CLI manages.
- MCP-compatible clients are related through the `hookdeck gateway mcp` command group.

### Sources

- Generated REFERENCE.md: command groups, global flags, login/project local config, and MCP support.
- Hookdeck CLI README: package distribution, event history, Event Gateway management, Docker usage, and config paths.
- Official CLI docs: local development, webhook forwarding, replay, inspection, and ngrok-alternative positioning.


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour hookdeck. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## 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

- Unix: ~/.config/hookdeck/config.toml, .hookdeck/config.toml

## Credential files

- Unix: ~/.config/hookdeck/config.toml, .hookdeck/config.toml

## Combined YAML source

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


## Sources

- pkg.so package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph
