dongarandClaude Opus 5.5
df449c7e34
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 51s
The thresholds Part H says to tune on the real inference hardware were hardcoded, so every adjustment would have been a PR. They now live in a `tuning:` section of a YAML config file, which also replaces flat environment variables as the home for structure (#32). - The file (NISSE_CONFIG, default ./nisse-dev.yaml) carries structure and holds no secrets: credentials are ${VAR} references resolved from the environment, and a reference to an unset variable is an error - The environment still wins: every existing NISSE_* variable overrides its key, and the file is optional, so .env and CI work unchanged - Validation stays fail-fast and reports every problem at once; unknown keys are errors, so a misspelt knob fails at startup instead of silently doing nothing - The config file joins the state store and .env in the check that refuses to start when they sit inside the workspace clone - Tuning covers the executor's turn and failure limits, the consult budget, the delegation caps, the command timeout and the tool output limit, which Workspace now takes as a setting; the defaults are the values the agent already ran with - llm.max_output_tokens reaches both LLM clients from the config docs/Tuning-Guide.md explains the knobs for someone learning local model tuning: how weights, quantization and the KV cache spend VRAM, what each knob does and what goes wrong at either extreme, and an order to tune in. nisse-dev.example.yaml documents every key and is checked by a test so it cannot drift. Closes #32 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
65 lines
3.0 KiB
Bash
65 lines
3.0 KiB
Bash
# Copy to .env (chmod 600). Real environment variables win over this file.
|
|
# .env is gitignored; never commit real values.
|
|
#
|
|
# Settings can also live in a YAML file (nisse-dev.example.yaml), which keeps
|
|
# structure and the tuning knobs; secrets stay here and are referenced from
|
|
# the file as ${NISSE_LLM_TOKEN} and so on. Every variable below overrides the
|
|
# matching key in that file.
|
|
|
|
# --- LLM access (A5): the LiteLLM proxy is the single LLM destination ---
|
|
NISSE_LLM_BASE_URL=http://litellm.example:4000
|
|
NISSE_LLM_TOKEN=sk-your-litellm-virtual-key
|
|
|
|
# --- Role mapping (A11): roles resolve to concrete model strings ---
|
|
NISSE_ROLE_EXECUTOR=anthropic/claude-haiku-4-5-20251001
|
|
NISSE_ROLE_PLANNER=anthropic/claude-opus-5
|
|
NISSE_ROLE_DELEGATE=anthropic/claude-opus-5
|
|
NISSE_ROLE_CONSULTANT=anthropic/claude-opus-5
|
|
|
|
# Opt-in for the live planning test: a model the virtual key can reach that
|
|
# holds the tool-call contract. Planning escalates unconditionally (A12), and
|
|
# small local models do not hold the contract reliably — llama3.2 returns
|
|
# truncated tool arguments, Haiku-class and up are solid.
|
|
NISSE_LIVE_PLANNER_MODEL=claude-haiku-4-5
|
|
|
|
# --- Matrix transport (A1), used by nisse-dev's MatrixTransport ---
|
|
NISSE_MATRIX_HOMESERVER=https://matrix.example
|
|
NISSE_MATRIX_USER_ID=@nisse-dev:example
|
|
NISSE_MATRIX_TOKEN=syt_your_matrix_access_token
|
|
NISSE_MATRIX_ROOM_ID=!roomid:example
|
|
# Dedicated room for the live integration test; never the production room.
|
|
NISSE_MATRIX_TEST_ROOM_ID=!testroomid:example
|
|
NISSE_MATRIX_OPERATORS=@you:example
|
|
|
|
# --- Gitea (B2): service account for branches, PRs, and comment intake ---
|
|
NISSE_GITEA_URL=https://gitea.example
|
|
NISSE_GITEA_TOKEN=your-scoped-service-account-token
|
|
# Sandbox repo for live tests; never the real project repo.
|
|
NISSE_GITEA_TEST_REPO=owner/sandbox-repo
|
|
# Gitea logins allowed to drive the agent via PR comments (A4 per-channel
|
|
# allowlist; a Matrix MXID and a Gitea login are different names).
|
|
NISSE_GITEA_OPERATORS=your-gitea-login
|
|
|
|
# --- Running the agent (the demo, not the tests) ---
|
|
# The tests use NISSE_GITEA_TEST_REPO; a running agent uses these.
|
|
#
|
|
# Layout. NISSE_WORKSPACE is the *clone the agent works in*, not the directory
|
|
# the agent runs from — they must not be the same place:
|
|
#
|
|
# ~/nisse-demo-workspace/ deployment root, not a git repo
|
|
# ├── .env this file
|
|
# ├── state.db the A2 state store
|
|
# └── project/ NISSE_WORKSPACE, the clone
|
|
#
|
|
# The agent commits its workspace with `git add -A` and pushes it, so anything
|
|
# inside the clone reaches the project repository. A .env or state store placed
|
|
# there would publish credentials as a side effect of the agent working
|
|
# correctly; startup refuses to proceed if either is inside the workspace.
|
|
NISSE_STATE_DB=~/nisse-demo-workspace/state.db
|
|
NISSE_WORKSPACE=~/nisse-demo-workspace/project
|
|
NISSE_PROJECT=demo
|
|
NISSE_GITEA_REPO=owner/demo-repo
|
|
# NISSE_BASE_BRANCH=main
|
|
# Path to this file, if not ./.env
|
|
# NISSE_ENV=~/nisse-demo-workspace/.env
|