pkg.soopen package index

cask

Install kero with Homebrew Cask

Terminal app optimised for agents. Version 2.1.32 via Homebrew Cask; verified from local package data.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrew Caskverified · 100%
brew install --cask kero

local Homebrew cask metadata

overview

Package summary

Terminal app optimised for agents

Commands and aliases

  • Kero

From the blog

A Local Control Plane for Coding Agents
When terminals become control surfaces

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for kero. Package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

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

Config paths the tool may read or write during local use.

Unix
~/.config/kero/config.toml

executables

Installed executables

CommandKindExposureNote
KerobinaryHomebrew cask binaryKero

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04
manager version2.1.32
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/egoist/kero

  • infoNo package-manager update timestamp was available.low confidence
  • infoNo cached GitHub release or tag data was available.https://github.com/egoist/keronone confidence

install metadata

Package metadata

Package keycask:kero
Version2.1.32
Package managerHomebrew Cask
Package manager pagehttps://formulae.brew.sh/cask/kero
Homepagehttps://kero.sh/
Repositoryhttps://github.com/egoist/kero
Upstream docshttps://kero.sh/
Source archivehttps://github.com/egoist/kero/releases/download/v2.1.32/kero-2.1.32-arm64.dmg
SHA-256b6d22a65aca830a0ea14e3685941e97fed7b655ca1f6fc4b3aa222ec3242d511
Bottlenot recorded
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokenkero
Names
  • Kero
Depends On
Macos
>=: 12
Artifacts
App
1
Binary
1
Target
2
Uninstall
1
Zap
1
Auto Updatesyes
Deprecatedno
Disabledno

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment