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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
# Agent settings.
#
provider: dmr
model: huggingface.co/jetbrains/mellum2-12b-a2.5b-instruct-gguf-q4_k_m:Q4_K_M
baseUrl: http://localhost:12434/engines/v1
fallback: http://host.docker.internal:12434/engines/v1
bashTool: true
# The built-in file tools: read_file, write_file, edit_file.
editTools: true
lsp:
servers:
- name: gopls
command: gopls
extensions: [".go"]
- name: rust # rustup component add rust-analyzer
command: rust-analyzer
extensions: [".rs"]
# How many tokens the server actually serves.
# 0 = ask the server (llama-server tells it on /props)
contextWindow: 0
# Max number of characters a tool returns to the model.
# Context safeguard: beyond that, the output is truncated (beginning + end kept).
maxOutput: 16000
# Max number of model <-> tools round trips for a single question.
# Raise it for tasks that need long chains of commands.
maxTurns: 40
# Persistent sessions, per project.
# When enabled, every conversation is saved as one JSON file under `dir`.
# `/sessions` lists them, `/resume` continues one; in an editor, "Reload Agent" replays the thread.
sessions:
enabled: true
dir: .mm/sessions
# How many lines of a command's output are echoed to the terminal.
# 0 disables it.
previewLines: 20
displayCommands: true
# The system prompt: what the agent is, and what it is allowed to do.
# This is the knob to play with — it is the shortest path to changing behaviour.
system: |
Your name is Bob.
You are a coding agent working in a terminal.
You have a "bash" tool to run shell commands.
Use it to explore files, run tests, inspect the repository, etc.
Chain several commands if needed, then answer clearly in English.
FILE EDITING
You have three tools for files: `read_file`, `edit_file` and `write_file`.
They are how a file gets read and changed here: each change is exact,
checked before it is written, and comes back as a diff with line numbers.
bash is for running things — building, testing, listing, searching.
RULES
- Keep everything the file already does, unless the user asked to remove it.
- Touch only the files the request is about. Do not add tests, files or
features that were not asked for.
- Never run a git command unless the user says git, commit or push.
- Never move, rename or delete a file unless the user asked for it.
- Then answer in English, in a few lines.
- If you don't know how to use a <cli>, run `<cli> --help` (or `<cli> help`)
to understand the options, then run the command.
BACKGROUND JOBS
Never let a command block the answer. Anything that serves, watches or runs
long goes to the background, with BOTH streams redirected and its pid kept:
nohup <command> > /tmp/<job>.log 2>&1 & echo $! > /tmp/<job>.pid
# Generation settings (OpenAI API keys). Low temperature for a coding agent:
# we want precise and reproducible answers, not creativity.
sampling:
temperature: 0.0
parallel_tool_calls: false
top_p: 0.9
max_tokens: 4096
# llama-server processes the whole prompt before the first token;
# on a laptop a 32k context can take a while. Raise it if it fires.
watchdogTimeout: 30s
# Context compression.
# ON here: the agent knows the window (read from /props), so `threshold` has a number to apply to.
context:
enabled: true
# Compress when the history reaches this share of the window.
threshold: 75
# Fallback on the message count, for when the window is unknown.
# One command costs 2 messages (call + response), so 80 is roughly 30 commands of history.
maxMessages: 80
# How many recent questions (with their commands and answers) are kept as-is instead of being summarised.
# The model works on the last few turns, so summarising them would make it redo what it just did.
keepLastTurns: 3
# max_tokens of the summary request.
summaryMaxTokens: 1200
showStats: true
|
