# kero mit Homebrew Cask installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für kero in AI-Agent-Workflows. ## Installation ```sh sudo av install cask:kero ``` Weitere Installationsbefehle: ### macOS - Homebrew Cask (100%): ```sh brew install --cask kero ``` Evidenz: local Homebrew cask metadata ## Paketfakten - **Paketschlüssel:** cask:kero - **Paketmanager:** Homebrew Cask - **Paketmanager-Seite:** - **Version:** 2.1.32 - **Quellzusammenfassung:** Terminal app optimised for agents - **Homepage:** - **Repository:** - **Upstream-Dokumentation:** - **Quellarchiv:** - **Generiert:** 2026-11-04T12:20:42+00:00 ## Executables - Kero (Binärdatei) ## Installationsverhalten - Post-install-Hook: nicht definiert - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-11-04 - Manager-Version: 2.1.32 - lokale Daten: OK - Upstream-Repository: https://github.com/egoist/kero - Info: No package-manager update timestamp was available. - Info: No cached GitHub release or tag data was available. ## Projektgeschichte und Nutzung Kero is a cross-platform terminal and project workspace optimized for coding-agent sessions. It combines terminal panes with project navigation, Git and file views, notifications, restoration, and optional agent lifecycle integration. ### Projektgeschichte Kero was created as a terminal-centered project workspace combining shells with files, Git state, process information, browser panes, and agent-aware session management. Its official documentation presents a cross-platform application whose persistent settings use a small TOML configuration, while platform-owned preferences retain window and session state. ### Adoptionsgeschichte Kero is distributed for macOS, Windows, and Linux, with a graphical application and an optional `kero` command placed on the user's PATH. The macOS release is also available through the developer's Homebrew tap. The application supports ordinary login shells while adding project restoration, panes, file and Git views, notifications, and lifecycle coordination for supported coding agents. ### Wie es verwendet wird Users open a project directory and arrange terminal, file, browser, and diff panes around the work. Each terminal launches the user's real login shell, preserving existing prompts, aliases, functions, and dotfiles. For agent-heavy work, Kero can coordinate supported background panes and notify the user when an agent finishes, fails, or needs input. Projects, tabs, panes, and working directories are restored after relaunch, while terminal processes start fresh. ### Warum Paket-Nerds sich dafür interessieren Kero sits in the emerging category of terminals designed around long-running coding-agent sessions rather than treating agents as ordinary transient commands. It is also technically distinctive for offering two native GPU-accelerated terminal backends—libghostty and Alacritty—behind one workspace interface, with Kero owning shared behavior such as panes, themes, search, notifications, and session restoration. ### Zeitleiste - Public development: The official egoist/kero repository established Kero as a terminal-centered project workspace. - Current release line: Official documentation covers signed desktop distribution, Homebrew installation, self-updates, and cross-platform command-line integration. ### Related projects - Ghostty supplies Kero's default terminal backend through libghostty. - Alacritty is the lower-memory alternative terminal backend available from Kero's settings. - Supported coding agents can report lifecycle state to Kero when its optional AI automation integration is enabled. ### Quellen - - - - - - ## Sicherheitshinweise Für kero wurde kein passendes lokales Secret-Handling-Manifest gefunden. 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 - Unix: ~/.config/kero/config.toml ## Details aus der Quelldatenbank - **Source Database:** Homebrew cask API - **Tap:** homebrew/cask - **Full Token:** kero - **Names:** Kero - **Depends On:** Macos: >=: 12 - **Artifacts:** App: 1, Binary: 1, Target: 2, Uninstall: 1, Zap: 1 - **Auto Updates:** yes - **Deprecated:** no - **Disabled:** no ## Verwandte Links - [Homebrew Cask packages](https://pkg.so/de/homebrew-cask-packages/) - Generated from Homebrew Cask package-manager metadata. - [Homebrew Cask applications](https://pkg.so/de/homebrew-cask-applications/) - Cask artifact metadata includes an app bundle. - [Homebrew Cask binaries](https://pkg.so/de/homebrew-cask-binaries/) - Cask artifact metadata includes a binary. - [ghostty](https://pkg.so/de/cask/ghostty/) - Choose Ghostty for a focused native terminal emulator without Kero's project and coding-agent workspace layer; Kero itself uses libghostty as its default terminal backend. Quellen: · - [warp](https://pkg.so/de/cask/warp/) - Choose Warp for another agent-oriented terminal environment with structured command blocks, shared workflows, and integrated development agents. Quellen: · ## Combined YAML source View the package source record on GitHub. [combined/kero.yml](https://github.com/mxcl/pkgdb/blob/main/combined/kero.yml) ## Quellen - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - package relationship graph - cross-ecosystem install command graph