Automic VaultAutomic Vault

brew

oterm mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install oterm

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#oterm

nixpkgs package indexes · pkgs/by-name/ot/oterm/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Terminal client for Ollama

Befehle und Aliase

  • oterm

Verlauf

Projektgeschichte und Nutzung

oterm is a Python terminal UI for chatting with LLMs. It began as a text-based terminal client for Ollama and evolved into a multi-provider terminal client for Ollama, OpenAI, Anthropic, Google, Groq, Mistral, Cohere, Bedrock, OpenAI-compatible endpoints, and other pydantic-ai-supported providers.

Projektgeschichte

GitHub records `ggozad/oterm` as created on 2023-10-10, during the wave of local-LLM tooling around Ollama. Early package descriptions and PyPI metadata framed it as a text-based terminal client for Ollama with persistent chat sessions, SQLite storage, model selection, system prompts, and parameter customization.

The 2026 release line changed the project's scope. Release 0.15.0, published on 2026-04-27, is described as the multi-provider release: chats moved through pydantic-ai, MCP integration was rewritten, the UI was refreshed, streaming improved, and old Ollama-only assumptions such as an internal pull-model command were removed. The README describes oterm as a terminal client for Ollama, OpenAI, Anthropic, and any pydantic-ai-supported provider.

Adoptionsgeschichte

oterm's adoption follows the developer interest in local and terminal-first LLM workflows. It is listed in the Ollama repository's terminal/CLI ecosystem list, and Homebrew/Nix packaging made it installable in the same package-manager channels as other developer CLIs.

The tool's multi-provider turn broadened its appeal from an Ollama companion to a terminal chat front end that can sit over local models, hosted APIs, and OpenAI-compatible servers such as vLLM, LM Studio, llama.cpp, OpenRouter, and LiteLLM.

Wie es verwendet wird

Users install and run `oterm` to get a terminal UI with persistent chat sessions, provider/model selection, streamed Markdown output, configurable system prompts and parameters, and optional MCP tool configuration. The documented config locations in the av.db input show it stores per-user configuration under the platform's application data directory, with environment-variable overrides for secrets and data directory selection.

For package nerds, the interesting usage pattern is that oterm packages a full TUI experience as a CLI entry point: the Python package is not merely a library, but an end-user application distributed through PyPI-style tooling and system package managers.

Warum Paket-Nerds sich dafür interessieren

oterm is a good example of the fast-moving LLM CLI package category: a small terminal app can quickly become a package-manager target because users want one-command installation, upgrades, and config discovery. Its 0.15.0 migration also shows how model-provider abstraction moved from app-specific integrations to library-mediated provider layers such as pydantic-ai.

Zeitleiste

  • 2023-10-10: GitHub records creation of `ggozad/oterm`.
  • 2024: PyPI release 0.6.0 described oterm as a text-based terminal client for Ollama with persistent SQLite sessions and model customization.
  • 2026-04-27: release 0.15.0 changed oterm into a multi-provider pydantic-ai-based terminal client and rewrote MCP configuration.
  • 2026-06-30: release 0.20.0 updated pydantic dependencies and improved Modelfile-based prompt/parameter prepopulation.

Related projects

  • Ollama is the original local-model runtime oterm was built around.
  • pydantic-ai became the provider abstraction layer for oterm's multi-provider architecture.
  • MCP-compatible configuration connects oterm to the same tool-server ecosystem used by desktop AI clients and editors.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

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

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 7 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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.

Linux
~/.local/share/oterm/config.json${XDG_DATA_HOME}/oterm/config.json${OTERM_DATA_DIR}/config.json
macOS
~/Library/Application Support/oterm/config.json${XDG_DATA_HOME}/oterm/config.json${OTERM_DATA_DIR}/config.json
Windows
C:/Users/<USER>/AppData/Roaming/oterm/config.json

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
./.env${OTERM_DATA_DIR}/config.json
Windows
./.envC:/Users/<USER>/AppData/Roaming/oterm/config.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
otermcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version0.20.0
Manager aktualisiert2026-07-23
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/ggozad/oterm

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:oterm
Version0.20.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/oterm
Homepagehttps://github.com/ggozad/oterm
Repositoryhttps://github.com/ggozad/oterm
Upstream-Dokumentationhttps://ggozad.github.io/oterm
LizenzMIT
Quellarchivhttps://files.pythonhosted.org/packages/1d/19/23455c1d66786bca4d4c35fec11dfd92cd1b7eaad53d04ef4465b39950ca/oterm-0.20.0.tar.gz
Zuletzt aktualisiert2026-07-23T03:55:57Z
Pulseupdated
Abhängigkeitencertifi, cryptography, libyaml, pillow, pydantic, python@3.14, rpds-py
Build-Abhängigkeitenpkgconf, rust
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameoterm
Version Scheme0
Revision2
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

oterm

nix profile install nixpkgs#oterm
  • normalized package name match
  • Abgeglichen nach: Oterm
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ot/oterm/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment