llman 0.0.69

A tool for managing LLM application rules(prompts) ...
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

# llman codex provider configuration
# Each [model_providers.<group_name>] block defines a provider.
# The [model_providers.<group_name>.env] sub-table holds the actual API key
# that will be injected as an environment variable when running codex.
#
# Optional: override the provider identity written into `~/.codex/config.toml`.
# This is useful when you want Codex sessions/history to stay stable even if
# you rename or reuse llman group names.
#
# When set, llman will:
# - upsert to `[model_providers.<override_name>]` (instead of `<group_name>`)
# - set `model_provider = "<override_name>"`
# - force the provider table's `name = "<override_name>"`
#
# Example:
#
# [model_providers.minimax]
# name = "minimax"
# base_url = "https://api.minimaxi.com/v1"
# wire_api = "responses"
# env_key = "MINIMAX_CODEX_API_KEY"
#
# [model_providers.minimax.env]
# MINIMAX_CODEX_API_KEY = "sk-your-key-here"
#
# [model_providers.minimax.llman_configs]
# override_name = "minimax-stable"
#
# Usage:
#   llman x codex                    # interactive select & run
#   llman x codex run --group minimax  # direct run
#   llman x codex account import     # add a new provider interactively
#   llman x codex account edit       # edit this file