docs: document openlama launcher and NO_PROXY requirement
- openlama wrapper at ~/.local/bin/openlama sets NO_PROXY and execs opencode - Documents that opencode does not auto-fetch /v1/models (models must be listed) - Documents the NO_PROXY fix for Bun runtime + HTTP_PROXY conflict
This commit is contained in:
parent
3963eede70
commit
c8974d9998
2 changed files with 12 additions and 1 deletions
|
|
@ -99,6 +99,15 @@ no_proxy=127.0.0.1,localhost,::1
|
|||
|
||||
Or launch opencode with `NO_PROXY=127.0.0.1,localhost opencode`.
|
||||
|
||||
### `openlama` launcher
|
||||
|
||||
A convenience wrapper is installed at `~/.local/bin/openlama`. It sets `NO_PROXY`/`no_proxy` for localhost, tries to start `ollama-proxy` if it's down, and execs `opencode` with all forwarded args:
|
||||
|
||||
```sh
|
||||
openlama # TUI with ocp available as a provider
|
||||
openlama run -m ocp/gpt-oss:120b "hello" # non-interactive, specific model
|
||||
```
|
||||
|
||||
Run `/models` in the OpenCode TUI to pick a model from the pool, then chat as usual.
|
||||
|
||||
## Use with the `ollama` CLI
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue