# Installer droid avec Homebrew Cask

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

## installation

```sh
sudo av install cask:droid
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew Cask (100%):

```sh
brew install --cask droid
```

  Preuve: local Homebrew cask metadata

## Faits du paquet

- **Clé du paquet:** cask:droid
- **Gestionnaire de paquets:** Homebrew Cask
- **Version:** 0.186.0
- **Résumé source:** AI-powered software engineering agent by Factory
- **Page d'accueil:** <https://docs.factory.ai/cli/getting-started/overview>
- **Dernière mise à jour:** 2026-08-01T01:13:48Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- droid (binaire)
- droid (alias)

## Dépendances

- ripgrep

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

Droid CLI is Factory's terminal software-engineering agent, distributed through installer scripts, npm, and the Homebrew cask named droid.

### Historique du projet

Factory's public repository was created in September 2025 and presents Factory as an agent-native development platform spanning CLI, web, Slack/Teams, Linear/Jira, and mobile. Official docs describe droid as Factory's development agent in the terminal.

### Historique d'adoption

The official quickstart lists macOS/Linux shell install, Windows PowerShell install, npm install, and Homebrew cask installation. That multi-channel distribution reflects the current AI coding-agent pattern: meet developers in existing terminals and code repositories, then sync with team systems.

### Modes d'utilisation

Users install droid, run it from a project directory, and interact through a full-screen terminal UI. The docs cover codebase analysis, proposed code changes, approvals, security audits, version-control help, slash commands, settings, model selection, sessions, missions, MCP, hooks, plugins, and skills.

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

As a package, Droid is notable because it packages a cloud-connected AI development agent as a familiar terminal binary. Its settings file, local overrides, Homebrew cask, npm package, and direct binary download put a fast-moving AI tool into the same operational lane as classic developer CLIs.

### Chronologie

- 2025: Public Factory repository created.
- 2025: Repository copyright range begins for Factory AI.
- 2026: Homebrew cask distributes Droid CLI release binaries.

### Related projects

- Factory's TypeScript and Python SDKs are linked from the official repository.
- Droid Action is the GitHub Actions integration for reviews, scans, and PR descriptions.
- Factory plugins, MCP integrations, custom droids, hooks, and skills are documented extension surfaces.

### Sources

- <https://github.com/Factory-AI/factory>
- <https://raw.githubusercontent.com/Factory-AI/factory/main/README.md>
- <https://docs.factory.ai/cli/getting-started/overview>
- <https://docs.factory.ai/cli/getting-started/overview.md>
- <https://docs.factory.ai/cli/getting-started/quickstart.md>
- <https://docs.factory.ai/cli/configuration/settings.md>
- <https://formulae.brew.sh/cask/droid>
- <https://formulae.brew.sh/api/cask/droid.json>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour droid. 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: ~/.factory/settings.json
- Windows: %USERPROFILE%\.factory\settings.json

## Combined YAML source

View the package source record on GitHub. [combined/droid.yml](https://github.com/mxcl/pkgdb/blob/main/combined/droid.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
