luxferre/bantam
1
0
Fork 0
Code Actions Activity

switched to kilo-auto/free as the default model

Browse Source
This commit is contained in:
Luxferre
2026-09-01 11:42:15 +03:00
parent 9a8e7af831
commit 8efd5a5fa6
4 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -5
View File
@@ -39,8 +39,8 @@ All implementations read `model.cfg` (or `.bantam.cfg`, which takes priority if
1. Configure `model.cfg` (or `.bantam.cfg`, which takes priority) with your API settings:
```ini
endpoint=https://opencode.ai/zen/v1
model=deepseek-v4-flash-free
endpoint=https://api.kilo.ai/api/openrouter
model=kilo-auto/free
temperature=0.7
api_key=your_api_key_here
stream=true
@@ -140,8 +140,8 @@ If the API rejects the request with an `Invalid assistant message: content or to
(shared by all implementations; the config file — `.bantam.cfg` takes priority over `model.cfg` when both exist — is plain `key=value` with `#` comments)
- `endpoint` (base OpenAI-compatible API URL, default `https://opencode.ai/zen/v1`)
- `model` (model name, e.g. `gpt-4o`)
- `endpoint` (base OpenAI-compatible API URL, default `https://api.kilo.ai/api/openrouter`)
- `model` (model name, default `kilo-auto/free`)
- `temperature` (model temperature, default 0.7)
- `api_key` (API key / Bearer token, optional; fall back to `OPENAI_API_KEY` env var)
- `stream` (stream response tokens in real-time, default `true`)
@@ -307,7 +307,7 @@ Set the `BANTAM_TOOLS_DIR` environment variable (or the `bantam_tools_dir` key i
### Is there any common config place for Bantam?
No, loading the config file (`.bantam.cfg` if present, else `model.cfg`) is deliberately only supported from the current working directory. This allows natural separation of configs per project. In case there's no config file inside the project, Bantam will use the free Big Pickle model from OpenCode Zen with the temperature 0.7. Big Pickle has been chosen as the default because it has no set expiration date, unlike other OpenCode's keyless tiers.
No, loading the config file (`.bantam.cfg` if present, else `model.cfg`) is deliberately only supported from the current working directory. This allows natural separation of configs per project. In case there's no config file inside the project, Bantam will use the `kilo/auto-free` model from Kilo Code with the temperature 0.7.
### Why no MCP support?