rickub
turbo-editors/configspublic⑂ Fork 0
⑂ a3c787d
Branches
main View all branches → View all tags →
Commits
⬇ Clone ▾
git clone https://git.rickub.com/turbo-editors/configs.git
git clone ssh://git@rickub.com/turbo-editors/configs.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

🛟 Updated.

k33g committed 2026-09-20T09:54:10+02:00 Browse files
a3c787d parent: cd4c4c7
modified README.md +64 -1
@@ -1 +1,64 @@
1-# Turbo Editors Config samples
\ No newline at end of file
1+# Turbo Editors — configuration samples
2+
3+Ready-made project configurations for the [Turbo editors](https://rickub.com/turbo-editors): one directory per kind of project, each holding the editor's own directory — `.turbo-go`, `.turbo-rust` — with its settings, snippets, tools and, in the `-with-agents` variants, its coding agents.
4+
5+You do not clone this repository to use it. Every Turbo editor can fetch a directory from it straight into your project.
6+
7+## Load a configuration into a project
8+
9+From the directory of your project, give the editor the URL of the sample as the browser shows it:
10+
11+```bash
12+cd my-go-project
13+turbo-go -load-config https://rickub.com/turbo-editors/configs/tree/main/golang-init
14+```
15+
16+The editor looks for the `.turbo-go` directory inside `golang-init`, copies it into the current directory, prints what arrived, and exits:
17+
18+```
19+Copied /path/to/my-go-project/.turbo-go from https://git.rickub.com/turbo-editors/configs.git (main):
20+ settings.toml
21+ snippets.toml
22+ tools.toml
23+```
24+
25+Then start the editor as usual — `turbo-go`, `turbo-go main.go` — and the settings, snippets and tools are in force.
26+
27+Each editor looks for its own directory: `turbo-rust` copies the `.turbo-rust` of the sample you point it at, `turbo-python` a `.turbo-python`, and so on. Pointing turbo-rust at a Go sample ends in an error saying there is no `.turbo-rust` there.
28+
29+```bash
30+cd my-rust-project
31+turbo-rust -load-config https://rickub.com/turbo-editors/configs/tree/main/rustlang-init-with-agents
32+```
33+
34+### What to know
35+
36+- **`git` must be installed.** The fetch is a shallow `git clone`; no token and no account are needed for this public repository.
37+- **A project that already has the directory is left alone.** The editor refuses rather than overwrite what the project decided. Move the existing `.turbo-<editor>` away first if you mean to replace it.
38+- **The URL may be any of these**: the sample's directory (`…/tree/main/golang-init`), the editor's directory inside it (`…/tree/main/golang-init/.turbo-go`), or a file in it. A branch or tag other than `main` works the same way, from the URL the browser shows for it.
39+- **The same works from other forges.** GitHub, GitLab and Codeberg URLs are understood too, so a team can keep its own samples wherever its code lives.
40+- **Nothing else is copied**: the sample's `README.md` and anything beside the editor's directory stay here.
41+
42+## The samples
43+
44+| Directory | Editor | Holds |
45+| --- | --- | --- |
46+| `golang-init` | turbo-go | `settings.toml` (theme `turbo-dark`, autosave on after 1 s), `snippets.toml`, `tools.toml` (format, lint, build, test, run) |
47+| `golang-init-with-agents` | turbo-go | The same, plus `acp.toml` naming two coding agents and the two agent settings files they read |
48+| `rustlang-init` | turbo-rust | `settings.toml`, `snippets.toml`, `tools.toml` for a Cargo project |
49+| `rustlang-init-with-agents` | turbo-rust | The same, plus the two agents |
50+
51+### The agents in the `-with-agents` samples
52+
53+`acp.toml` declares two agents, both run as `mm -acp` — a local agent speaking the Agent Client Protocol — each with its own settings file beside it (`agent.mm-dmr-gemma.yaml`, `agent.mm-dmr-mellum.yaml`), passed through the `AGENT_CONFIG` environment variable. Those files point at a **Docker Model Runner** serving models on `http://localhost:12434`, with `host.docker.internal` as the fallback. To use them you need `mm` on your `PATH` and Docker Model Runner running with the named models; otherwise the Agent menu lists the agents and opening one reports that it could not start.
54+
55+Edit the two YAML files after loading — the model, the URL, which tools the agent may use — exactly as you would any project file. They are yours once copied.
56+
57+## Add a sample
58+
59+1. Create a directory named for the kind of project: `<language>-<flavour>`.
60+2. Put the editor's directory inside it — `.turbo-<editor>/` with at least `settings.toml`; add `snippets.toml`, `tools.toml`, and `acp.toml` with its agent files if the sample ships agents. The starter files an editor creates from its Options menu are a good beginning.
61+3. Add a `README.md` saying what the sample is for and what it assumes is installed.
62+4. Do not commit anything an agent writes while you test the sample: `.mm/` is ignored for that reason.
63+
64+The editors only read `.turbo-<editor>/`, so a sample may hold the same configuration for several editors side by side — `.turbo-go` and `.turbo-rust` in one directory — and each editor takes its own.
@@ -1 +1,64 @@
1-# Turbo Editors Config samples
\ No newline at end of file\ No newline at end of file
1+# Turbo Editors — configuration samples
2+
3+Ready-made project configurations for the [Turbo editors](https://rickub.com/turbo-editors): one directory per kind of project, each holding the editor's own directory — `.turbo-go`, `.turbo-rust` — with its settings, snippets, tools and, in the `-with-agents` variants, its coding agents.
4+
5+You do not clone this repository to use it. Every Turbo editor can fetch a directory from it straight into your project.
6+
7+## Load a configuration into a project
8+
9+From the directory of your project, give the editor the URL of the sample as the browser shows it:
10+
11+```bash
12+cd my-go-project
13+turbo-go -load-config https://rickub.com/turbo-editors/configs/tree/main/golang-init
14+```
15+
16+The editor looks for the `.turbo-go` directory inside `golang-init`, copies it into the current directory, prints what arrived, and exits:
17+
18+```
19+Copied /path/to/my-go-project/.turbo-go from https://git.rickub.com/turbo-editors/configs.git (main):
20+ settings.toml
21+ snippets.toml
22+ tools.toml
23+```
24+
25+Then start the editor as usual — `turbo-go`, `turbo-go main.go` — and the settings, snippets and tools are in force.
26+
27+Each editor looks for its own directory: `turbo-rust` copies the `.turbo-rust` of the sample you point it at, `turbo-python` a `.turbo-python`, and so on. Pointing turbo-rust at a Go sample ends in an error saying there is no `.turbo-rust` there.
28+
29+```bash
30+cd my-rust-project
31+turbo-rust -load-config https://rickub.com/turbo-editors/configs/tree/main/rustlang-init-with-agents
32+```
33+
34+### What to know
35+
36+- **`git` must be installed.** The fetch is a shallow `git clone`; no token and no account are needed for this public repository.
37+- **A project that already has the directory is left alone.** The editor refuses rather than overwrite what the project decided. Move the existing `.turbo-<editor>` away first if you mean to replace it.
38+- **The URL may be any of these**: the sample's directory (`…/tree/main/golang-init`), the editor's directory inside it (`…/tree/main/golang-init/.turbo-go`), or a file in it. A branch or tag other than `main` works the same way, from the URL the browser shows for it.
39+- **The same works from other forges.** GitHub, GitLab and Codeberg URLs are understood too, so a team can keep its own samples wherever its code lives.
40+- **Nothing else is copied**: the sample's `README.md` and anything beside the editor's directory stay here.
41+
42+## The samples
43+
44+| Directory | Editor | Holds |
45+| --- | --- | --- |
46+| `golang-init` | turbo-go | `settings.toml` (theme `turbo-dark`, autosave on after 1 s), `snippets.toml`, `tools.toml` (format, lint, build, test, run) |
47+| `golang-init-with-agents` | turbo-go | The same, plus `acp.toml` naming two coding agents and the two agent settings files they read |
48+| `rustlang-init` | turbo-rust | `settings.toml`, `snippets.toml`, `tools.toml` for a Cargo project |
49+| `rustlang-init-with-agents` | turbo-rust | The same, plus the two agents |
50+
51+### The agents in the `-with-agents` samples
52+
53+`acp.toml` declares two agents, both run as `mm -acp` — a local agent speaking the Agent Client Protocol — each with its own settings file beside it (`agent.mm-dmr-gemma.yaml`, `agent.mm-dmr-mellum.yaml`), passed through the `AGENT_CONFIG` environment variable. Those files point at a **Docker Model Runner** serving models on `http://localhost:12434`, with `host.docker.internal` as the fallback. To use them you need `mm` on your `PATH` and Docker Model Runner running with the named models; otherwise the Agent menu lists the agents and opening one reports that it could not start.
54+
55+Edit the two YAML files after loading — the model, the URL, which tools the agent may use — exactly as you would any project file. They are yours once copied.
56+
57+## Add a sample
58+
59+1. Create a directory named for the kind of project: `<language>-<flavour>`.
60+2. Put the editor's directory inside it — `.turbo-<editor>/` with at least `settings.toml`; add `snippets.toml`, `tools.toml`, and `acp.toml` with its agent files if the sample ships agents. The starter files an editor creates from its Options menu are a good beginning.
61+3. Add a `README.md` saying what the sample is for and what it assumes is installed.
62+4. Do not commit anything an agent writes while you test the sample: `.mm/` is ignored for that reason.
63+
64+The editors only read `.turbo-<editor>/`, so a sample may hold the same configuration for several editors side by side — `.turbo-go` and `.turbo-rust` in one directory — and each editor takes its own.
added rustlang-init-with-agents/.turbo-rust/acp.toml +13 -0
new file mode 100644
@@ -0,0 +1,13 @@
1+
2+[[agent]]
3+name = "Bob (mm-dmr-mellum2)"
4+command = "mm"
5+args = ["-acp"]
6+env = { AGENT_CONFIG = ".turbo-rust/agent.mm-dmr-mellum.yaml" }
7+
8+
9+[[agent]]
10+name = "Riker (mm-dmr-gemma)"
11+command = "mm"
12+args = ["-acp"]
13+env = { AGENT_CONFIG = ".turbo-rust/agent.mm-dmr-gemma.yaml" }
new file mode 100644
@@ -0,0 +1,13 @@
1+
2+[[agent]]
3+name = "Bob (mm-dmr-mellum2)"
4+command = "mm"
5+args = ["-acp"]
6+env = { AGENT_CONFIG = ".turbo-rust/agent.mm-dmr-mellum.yaml" }
7+
8+
9+[[agent]]
10+name = "Riker (mm-dmr-gemma)"
11+command = "mm"
12+args = ["-acp"]
13+env = { AGENT_CONFIG = ".turbo-rust/agent.mm-dmr-gemma.yaml" }
added rustlang-init-with-agents/.turbo-rust/agent.mm-dmr-gemma.yaml +110 -0
new file mode 100644
@@ -0,0 +1,110 @@
1+# Agent settings.
2+#
3+provider: dmr
4+
5+model: huggingface.co/unsloth/gemma-4-e2b-it-gguf:Q4_K_M
6+baseUrl: http://localhost:12434/engines/v1
7+fallback: http://host.docker.internal:12434/engines/v1
8+
9+bashTool: true
10+# The built-in file tools: read_file, write_file, edit_file.
11+editTools: true
12+
13+lsp:
14+ servers:
15+ - name: gopls
16+ command: gopls
17+ extensions: [".go"]
18+ - name: rust # rustup component add rust-analyzer
19+ command: rust-analyzer
20+ extensions: [".rs"]
21+# How many tokens the server actually serves.
22+# 0 = ask the server (llama-server tells it on /props)
23+contextWindow: 0
24+
25+# Max number of characters a tool returns to the model.
26+# Context safeguard: beyond that, the output is truncated (beginning + end kept).
27+maxOutput: 16000
28+
29+# Max number of model <-> tools round trips for a single question.
30+# Raise it for tasks that need long chains of commands.
31+maxTurns: 40
32+
33+# Persistent sessions, per project.
34+# When enabled, every conversation is saved as one JSON file under `dir`.
35+# `/sessions` lists them, `/resume` continues one; in an editor, "Reload Agent" replays the thread.
36+sessions:
37+ enabled: true
38+ dir: .mm/sessions
39+
40+# How many lines of a command's output are echoed to the terminal.
41+# 0 disables it.
42+previewLines: 20
43+
44+displayCommands: true
45+
46+# The system prompt: what the agent is, and what it is allowed to do.
47+# This is the knob to play with — it is the shortest path to changing behaviour.
48+system: |
49+ Your name is Riker.
50+ You are a coding agent working in a terminal.
51+ You have a "bash" tool to run shell commands.
52+ Use it to explore files, run tests, inspect the repository, etc.
53+ Chain several commands if needed, then answer clearly in English.
54+
55+ FILE EDITING
56+ You have three tools for files: `read_file`, `edit_file` and `write_file`.
57+ They are how a file gets read and changed here: each change is exact,
58+ checked before it is written, and comes back as a diff with line numbers.
59+ bash is for running things — building, testing, listing, searching.
60+
61+ RULES
62+ - Keep everything the file already does, unless the user asked to remove it.
63+ - Touch only the files the request is about. Do not add tests, files or
64+ features that were not asked for.
65+ - Never run a git command unless the user says git, commit or push.
66+ - Never move, rename or delete a file unless the user asked for it.
67+ - Then answer in English, in a few lines.
68+ - If you don't know how to use a <cli>, run `<cli> --help` (or `<cli> help`)
69+ to understand the options, then run the command.
70+
71+ BACKGROUND JOBS
72+ Never let a command block the answer. Anything that serves, watches or runs
73+ long goes to the background, with BOTH streams redirected and its pid kept:
74+
75+ nohup <command> > /tmp/<job>.log 2>&1 & echo $! > /tmp/<job>.pid
76+
77+
78+# Generation settings (OpenAI API keys). Low temperature for a coding agent:
79+# we want precise and reproducible answers, not creativity.
80+sampling:
81+ temperature: 0.0
82+ parallel_tool_calls: false
83+ top_p: 0.9
84+ max_tokens: 4096
85+
86+# llama-server processes the whole prompt before the first token;
87+# on a laptop a 32k context can take a while. Raise it if it fires.
88+watchdogTimeout: 30s
89+
90+# Context compression.
91+# ON here: the agent knows the window (read from /props), so `threshold` has a number to apply to.
92+context:
93+ enabled: true
94+
95+ # Compress when the history reaches this share of the window.
96+ threshold: 75
97+
98+ # Fallback on the message count, for when the window is unknown.
99+ # One command costs 2 messages (call + response), so 80 is roughly 30 commands of history.
100+ maxMessages: 80
101+
102+ # How many recent questions (with their commands and answers) are kept as-is instead of being summarised.
103+ # The model works on the last few turns, so summarising them would make it redo what it just did.
104+ keepLastTurns: 3
105+
106+ # max_tokens of the summary request.
107+ summaryMaxTokens: 1200
108+
109+ showStats: true
110+
new file mode 100644
@@ -0,0 +1,110 @@
1+# Agent settings.
2+#
3+provider: dmr
4+
5+model: huggingface.co/unsloth/gemma-4-e2b-it-gguf:Q4_K_M
6+baseUrl: http://localhost:12434/engines/v1
7+fallback: http://host.docker.internal:12434/engines/v1
8+
9+bashTool: true
10+# The built-in file tools: read_file, write_file, edit_file.
11+editTools: true
12+
13+lsp:
14+ servers:
15+ - name: gopls
16+ command: gopls
17+ extensions: [".go"]
18+ - name: rust # rustup component add rust-analyzer
19+ command: rust-analyzer
20+ extensions: [".rs"]
21+# How many tokens the server actually serves.
22+# 0 = ask the server (llama-server tells it on /props)
23+contextWindow: 0
24+
25+# Max number of characters a tool returns to the model.
26+# Context safeguard: beyond that, the output is truncated (beginning + end kept).
27+maxOutput: 16000
28+
29+# Max number of model <-> tools round trips for a single question.
30+# Raise it for tasks that need long chains of commands.
31+maxTurns: 40
32+
33+# Persistent sessions, per project.
34+# When enabled, every conversation is saved as one JSON file under `dir`.
35+# `/sessions` lists them, `/resume` continues one; in an editor, "Reload Agent" replays the thread.
36+sessions:
37+ enabled: true
38+ dir: .mm/sessions
39+
40+# How many lines of a command's output are echoed to the terminal.
41+# 0 disables it.
42+previewLines: 20
43+
44+displayCommands: true
45+
46+# The system prompt: what the agent is, and what it is allowed to do.
47+# This is the knob to play with — it is the shortest path to changing behaviour.
48+system: |
49+ Your name is Riker.
50+ You are a coding agent working in a terminal.
51+ You have a "bash" tool to run shell commands.
52+ Use it to explore files, run tests, inspect the repository, etc.
53+ Chain several commands if needed, then answer clearly in English.
54+
55+ FILE EDITING
56+ You have three tools for files: `read_file`, `edit_file` and `write_file`.
57+ They are how a file gets read and changed here: each change is exact,
58+ checked before it is written, and comes back as a diff with line numbers.
59+ bash is for running things — building, testing, listing, searching.
60+
61+ RULES
62+ - Keep everything the file already does, unless the user asked to remove it.
63+ - Touch only the files the request is about. Do not add tests, files or
64+ features that were not asked for.
65+ - Never run a git command unless the user says git, commit or push.
66+ - Never move, rename or delete a file unless the user asked for it.
67+ - Then answer in English, in a few lines.
68+ - If you don't know how to use a <cli>, run `<cli> --help` (or `<cli> help`)
69+ to understand the options, then run the command.
70+
71+ BACKGROUND JOBS
72+ Never let a command block the answer. Anything that serves, watches or runs
73+ long goes to the background, with BOTH streams redirected and its pid kept:
74+
75+ nohup <command> > /tmp/<job>.log 2>&1 & echo $! > /tmp/<job>.pid
76+
77+
78+# Generation settings (OpenAI API keys). Low temperature for a coding agent:
79+# we want precise and reproducible answers, not creativity.
80+sampling:
81+ temperature: 0.0
82+ parallel_tool_calls: false
83+ top_p: 0.9
84+ max_tokens: 4096
85+
86+# llama-server processes the whole prompt before the first token;
87+# on a laptop a 32k context can take a while. Raise it if it fires.
88+watchdogTimeout: 30s
89+
90+# Context compression.
91+# ON here: the agent knows the window (read from /props), so `threshold` has a number to apply to.
92+context:
93+ enabled: true
94+
95+ # Compress when the history reaches this share of the window.
96+ threshold: 75
97+
98+ # Fallback on the message count, for when the window is unknown.
99+ # One command costs 2 messages (call + response), so 80 is roughly 30 commands of history.
100+ maxMessages: 80
101+
102+ # How many recent questions (with their commands and answers) are kept as-is instead of being summarised.
103+ # The model works on the last few turns, so summarising them would make it redo what it just did.
104+ keepLastTurns: 3
105+
106+ # max_tokens of the summary request.
107+ summaryMaxTokens: 1200
108+
109+ showStats: true
110+
added rustlang-init-with-agents/.turbo-rust/agent.mm-dmr-mellum.yaml +111 -0
new file mode 100644
@@ -0,0 +1,111 @@
1+# Agent settings.
2+#
3+provider: dmr
4+
5+model: huggingface.co/jetbrains/mellum2-12b-a2.5b-instruct-gguf-q4_k_m:Q4_K_M
6+baseUrl: http://localhost:12434/engines/v1
7+fallback: http://host.docker.internal:12434/engines/v1
8+
9+bashTool: true
10+# The built-in file tools: read_file, write_file, edit_file.
11+editTools: true
12+
13+lsp:
14+ servers:
15+ - name: gopls
16+ command: gopls
17+ extensions: [".go"]
18+ - name: rust # rustup component add rust-analyzer
19+ command: rust-analyzer
20+ extensions: [".rs"]
21+
22+# How many tokens the server actually serves.
23+# 0 = ask the server (llama-server tells it on /props)
24+contextWindow: 0
25+
26+# Max number of characters a tool returns to the model.
27+# Context safeguard: beyond that, the output is truncated (beginning + end kept).
28+maxOutput: 16000
29+
30+# Max number of model <-> tools round trips for a single question.
31+# Raise it for tasks that need long chains of commands.
32+maxTurns: 40
33+
34+# Persistent sessions, per project.
35+# When enabled, every conversation is saved as one JSON file under `dir`.
36+# `/sessions` lists them, `/resume` continues one; in an editor, "Reload Agent" replays the thread.
37+sessions:
38+ enabled: true
39+ dir: .mm/sessions
40+
41+# How many lines of a command's output are echoed to the terminal.
42+# 0 disables it.
43+previewLines: 20
44+
45+displayCommands: true
46+
47+# The system prompt: what the agent is, and what it is allowed to do.
48+# This is the knob to play with — it is the shortest path to changing behaviour.
49+system: |
50+ Your name is Bob.
51+ You are a coding agent working in a terminal.
52+ You have a "bash" tool to run shell commands.
53+ Use it to explore files, run tests, inspect the repository, etc.
54+ Chain several commands if needed, then answer clearly in English.
55+
56+ FILE EDITING
57+ You have three tools for files: `read_file`, `edit_file` and `write_file`.
58+ They are how a file gets read and changed here: each change is exact,
59+ checked before it is written, and comes back as a diff with line numbers.
60+ bash is for running things — building, testing, listing, searching.
61+
62+ RULES
63+ - Keep everything the file already does, unless the user asked to remove it.
64+ - Touch only the files the request is about. Do not add tests, files or
65+ features that were not asked for.
66+ - Never run a git command unless the user says git, commit or push.
67+ - Never move, rename or delete a file unless the user asked for it.
68+ - Then answer in English, in a few lines.
69+ - If you don't know how to use a <cli>, run `<cli> --help` (or `<cli> help`)
70+ to understand the options, then run the command.
71+
72+ BACKGROUND JOBS
73+ Never let a command block the answer. Anything that serves, watches or runs
74+ long goes to the background, with BOTH streams redirected and its pid kept:
75+
76+ nohup <command> > /tmp/<job>.log 2>&1 & echo $! > /tmp/<job>.pid
77+
78+
79+# Generation settings (OpenAI API keys). Low temperature for a coding agent:
80+# we want precise and reproducible answers, not creativity.
81+sampling:
82+ temperature: 0.0
83+ parallel_tool_calls: false
84+ top_p: 0.9
85+ max_tokens: 4096
86+
87+# llama-server processes the whole prompt before the first token;
88+# on a laptop a 32k context can take a while. Raise it if it fires.
89+watchdogTimeout: 30s
90+
91+# Context compression.
92+# ON here: the agent knows the window (read from /props), so `threshold` has a number to apply to.
93+context:
94+ enabled: true
95+
96+ # Compress when the history reaches this share of the window.
97+ threshold: 75
98+
99+ # Fallback on the message count, for when the window is unknown.
100+ # One command costs 2 messages (call + response), so 80 is roughly 30 commands of history.
101+ maxMessages: 80
102+
103+ # How many recent questions (with their commands and answers) are kept as-is instead of being summarised.
104+ # The model works on the last few turns, so summarising them would make it redo what it just did.
105+ keepLastTurns: 3
106+
107+ # max_tokens of the summary request.
108+ summaryMaxTokens: 1200
109+
110+ showStats: true
111+
new file mode 100644
@@ -0,0 +1,111 @@
1+# Agent settings.
2+#
3+provider: dmr
4+
5+model: huggingface.co/jetbrains/mellum2-12b-a2.5b-instruct-gguf-q4_k_m:Q4_K_M
6+baseUrl: http://localhost:12434/engines/v1
7+fallback: http://host.docker.internal:12434/engines/v1
8+
9+bashTool: true
10+# The built-in file tools: read_file, write_file, edit_file.
11+editTools: true
12+
13+lsp:
14+ servers:
15+ - name: gopls
16+ command: gopls
17+ extensions: [".go"]
18+ - name: rust # rustup component add rust-analyzer
19+ command: rust-analyzer
20+ extensions: [".rs"]
21+
22+# How many tokens the server actually serves.
23+# 0 = ask the server (llama-server tells it on /props)
24+contextWindow: 0
25+
26+# Max number of characters a tool returns to the model.
27+# Context safeguard: beyond that, the output is truncated (beginning + end kept).
28+maxOutput: 16000
29+
30+# Max number of model <-> tools round trips for a single question.
31+# Raise it for tasks that need long chains of commands.
32+maxTurns: 40
33+
34+# Persistent sessions, per project.
35+# When enabled, every conversation is saved as one JSON file under `dir`.
36+# `/sessions` lists them, `/resume` continues one; in an editor, "Reload Agent" replays the thread.
37+sessions:
38+ enabled: true
39+ dir: .mm/sessions
40+
41+# How many lines of a command's output are echoed to the terminal.
42+# 0 disables it.
43+previewLines: 20
44+
45+displayCommands: true
46+
47+# The system prompt: what the agent is, and what it is allowed to do.
48+# This is the knob to play with — it is the shortest path to changing behaviour.
49+system: |
50+ Your name is Bob.
51+ You are a coding agent working in a terminal.
52+ You have a "bash" tool to run shell commands.
53+ Use it to explore files, run tests, inspect the repository, etc.
54+ Chain several commands if needed, then answer clearly in English.
55+
56+ FILE EDITING
57+ You have three tools for files: `read_file`, `edit_file` and `write_file`.
58+ They are how a file gets read and changed here: each change is exact,
59+ checked before it is written, and comes back as a diff with line numbers.
60+ bash is for running things — building, testing, listing, searching.
61+
62+ RULES
63+ - Keep everything the file already does, unless the user asked to remove it.
64+ - Touch only the files the request is about. Do not add tests, files or
65+ features that were not asked for.
66+ - Never run a git command unless the user says git, commit or push.
67+ - Never move, rename or delete a file unless the user asked for it.
68+ - Then answer in English, in a few lines.
69+ - If you don't know how to use a <cli>, run `<cli> --help` (or `<cli> help`)
70+ to understand the options, then run the command.
71+
72+ BACKGROUND JOBS
73+ Never let a command block the answer. Anything that serves, watches or runs
74+ long goes to the background, with BOTH streams redirected and its pid kept:
75+
76+ nohup <command> > /tmp/<job>.log 2>&1 & echo $! > /tmp/<job>.pid
77+
78+
79+# Generation settings (OpenAI API keys). Low temperature for a coding agent:
80+# we want precise and reproducible answers, not creativity.
81+sampling:
82+ temperature: 0.0
83+ parallel_tool_calls: false
84+ top_p: 0.9
85+ max_tokens: 4096
86+
87+# llama-server processes the whole prompt before the first token;
88+# on a laptop a 32k context can take a while. Raise it if it fires.
89+watchdogTimeout: 30s
90+
91+# Context compression.
92+# ON here: the agent knows the window (read from /props), so `threshold` has a number to apply to.
93+context:
94+ enabled: true
95+
96+ # Compress when the history reaches this share of the window.
97+ threshold: 75
98+
99+ # Fallback on the message count, for when the window is unknown.
100+ # One command costs 2 messages (call + response), so 80 is roughly 30 commands of history.
101+ maxMessages: 80
102+
103+ # How many recent questions (with their commands and answers) are kept as-is instead of being summarised.
104+ # The model works on the last few turns, so summarising them would make it redo what it just did.
105+ keepLastTurns: 3
106+
107+ # max_tokens of the summary request.
108+ summaryMaxTokens: 1200
109+
110+ showStats: true
111+
added rustlang-init-with-agents/.turbo-rust/settings.toml +9 -0
new file mode 100644
@@ -0,0 +1,9 @@
1+# turbo-rust project settings.
2+#
3+[editor]
4+
5+theme = "catppuccin-latte"
6+
7+autosave = true
8+
9+autosave_delay = "1s"
new file mode 100644
@@ -0,0 +1,9 @@
1+# turbo-rust project settings.
2+#
3+[editor]
4+
5+theme = "catppuccin-latte"
6+
7+autosave = true
8+
9+autosave_delay = "1s"
added rustlang-init-with-agents/.turbo-rust/snippets.toml +59 -0
new file mode 100644
@@ -0,0 +1,59 @@
1+# turbo-rust snippets.
2+#
3+# Each [[snippet]] becomes one line of the Snippets menu. Snippets sharing a
4+# group appear together in a submenu of that name; one with no group goes into
5+# General. A snippet is inserted at the cursor, and every line after the
6+# first is indented to match the line you inserted it on.
7+#
8+# languages restricts a snippet to files of those kinds, by the names the
9+# editor uses: rust, toml, yaml, markdown, javascript, html, xml, dockerfile,
10+# bash. Leave it out and the snippet is offered everywhere.
11+#
12+# Your own snippets, shared across every project, go in:
13+# /Users/k33g/Library/Application Support/turbo-rust/snippets.toml
14+
15+[[snippet]]
16+name = "match"
17+group = "Rust"
18+languages = ["rust"]
19+body = """
20+match value {
21+ Some(v) => v,
22+ None => return,
23+}"""
24+
25+[[snippet]]
26+name = "if let"
27+group = "Rust"
28+languages = ["rust"]
29+body = """
30+if let Some(v) = value {
31+}"""
32+
33+[[snippet]]
34+name = "propagate the error"
35+group = "Rust"
36+languages = ["rust"]
37+body = "let value = fallible()?;"
38+
39+[[snippet]]
40+name = "derive"
41+group = "Rust"
42+languages = ["rust"]
43+body = "#[derive(Debug, Clone, PartialEq)]"
44+
45+[[snippet]]
46+name = "test module"
47+group = "Rust"
48+languages = ["rust"]
49+body = """
50+#[cfg(test)]
51+mod tests {
52+ use super::*;
53+
54+ #[test]
55+ fn it_works() {
56+ assert_eq!(1 + 1, 2);
57+ }
58+}"""
59+
new file mode 100644
@@ -0,0 +1,59 @@
1+# turbo-rust snippets.
2+#
3+# Each [[snippet]] becomes one line of the Snippets menu. Snippets sharing a
4+# group appear together in a submenu of that name; one with no group goes into
5+# General. A snippet is inserted at the cursor, and every line after the
6+# first is indented to match the line you inserted it on.
7+#
8+# languages restricts a snippet to files of those kinds, by the names the
9+# editor uses: rust, toml, yaml, markdown, javascript, html, xml, dockerfile,
10+# bash. Leave it out and the snippet is offered everywhere.
11+#
12+# Your own snippets, shared across every project, go in:
13+# /Users/k33g/Library/Application Support/turbo-rust/snippets.toml
14+
15+[[snippet]]
16+name = "match"
17+group = "Rust"
18+languages = ["rust"]
19+body = """
20+match value {
21+ Some(v) => v,
22+ None => return,
23+}"""
24+
25+[[snippet]]
26+name = "if let"
27+group = "Rust"
28+languages = ["rust"]
29+body = """
30+if let Some(v) = value {
31+}"""
32+
33+[[snippet]]
34+name = "propagate the error"
35+group = "Rust"
36+languages = ["rust"]
37+body = "let value = fallible()?;"
38+
39+[[snippet]]
40+name = "derive"
41+group = "Rust"
42+languages = ["rust"]
43+body = "#[derive(Debug, Clone, PartialEq)]"
44+
45+[[snippet]]
46+name = "test module"
47+group = "Rust"
48+languages = ["rust"]
49+body = """
50+#[cfg(test)]
51+mod tests {
52+ use super::*;
53+
54+ #[test]
55+ fn it_works() {
56+ assert_eq!(1 + 1, 2);
57+ }
58+}"""
59+
added rustlang-init-with-agents/.turbo-rust/tools.toml +81 -0
new file mode 100644
@@ -0,0 +1,81 @@
1+# turbo-rust tools.
2+#
3+# Each [[tool]] becomes one line of the Rust menu, in the order they appear
4+# here. name is what the menu shows; a letter between tildes is its hot key, and
5+# no two tools should claim the same one.
6+#
7+# command goes to "sh -c", so pipes, globs and && work: one entry can be a
8+# whole sequence.
9+#
10+# menu says which menu it appears in. Leave it out and the tool goes into the
11+# Rust menu; name anything else and that menu is created for you, in the order
12+# the names first appear here. A tool that has nothing to do with Rust belongs
13+# in one of your own:
14+#
15+# [[tool]]
16+# name = "~E~cho"
17+# command = "echo TADA"
18+# menu = "Tools"
19+#
20+# A {{label}} in a command is a value the editor asks for before running it, in
21+# a box titled after the tool. The text between the braces is what it asks for:
22+#
23+# [[tool]]
24+# name = "~N~ew binary"
25+# command = "cargo new --bin {{crate name}}"
26+#
27+# The value is quoted, so a path with a space in it stays one argument. Add ...
28+# inside the braces when you mean several arguments rather than one value:
29+#
30+# [[tool]]
31+# name = "Test ~o~ne"
32+# command = "cargo test {{extra flags...}}"
33+#
34+# Double braces, not single. Single ones appear in real commands — awk '{print
35+# $1}' and find . -exec rm {} + are both ordinary things to put here — and
36+# neither is asking you for anything.
37+#
38+# output says where what the command prints goes:
39+# popup a dialog that fills in as it runs, and says the exit code (default)
40+# terminal a terminal window, for anything that reads the keyboard or runs long
41+# editor an editing window once it has finished, to search with Ctrl-F
42+#
43+# Commands run in the directory the editor was started in, which is why they
44+# see the whole workspace when you start from its root.
45+
46+[[tool]]
47+name = "~F~ormat"
48+command = "cargo fmt"
49+output = "popup"
50+
51+[[tool]]
52+name = "~L~int"
53+command = "cargo clippy --all-targets"
54+output = "popup"
55+
56+[[tool]]
57+name = "~B~uild"
58+command = "cargo build"
59+output = "popup"
60+
61+[[tool]]
62+name = "~T~est"
63+command = "cargo test"
64+output = "popup"
65+
66+[[tool]]
67+name = "~R~un"
68+command = "cargo run"
69+# A terminal, not a popup: a program that reads the keyboard has to be able to
70+# be answered, and one that runs long has to be able to be interrupted.
71+output = "terminal"
72+
73+# A tool naming a `menu` gets a menu of its own on the bar. Nothing above does,
74+# so every tool above is in the Rust menu. This one is in a menu called Tools,
75+# which appears between Rust and Help — that is the whole mechanism.
76+
77+[[tool]]
78+name = "~E~cho"
79+command = "echo 🎉 tada!"
80+menu = "Tools"
81+output = "terminal"
new file mode 100644
@@ -0,0 +1,81 @@
1+# turbo-rust tools.
2+#
3+# Each [[tool]] becomes one line of the Rust menu, in the order they appear
4+# here. name is what the menu shows; a letter between tildes is its hot key, and
5+# no two tools should claim the same one.
6+#
7+# command goes to "sh -c", so pipes, globs and && work: one entry can be a
8+# whole sequence.
9+#
10+# menu says which menu it appears in. Leave it out and the tool goes into the
11+# Rust menu; name anything else and that menu is created for you, in the order
12+# the names first appear here. A tool that has nothing to do with Rust belongs
13+# in one of your own:
14+#
15+# [[tool]]
16+# name = "~E~cho"
17+# command = "echo TADA"
18+# menu = "Tools"
19+#
20+# A {{label}} in a command is a value the editor asks for before running it, in
21+# a box titled after the tool. The text between the braces is what it asks for:
22+#
23+# [[tool]]
24+# name = "~N~ew binary"
25+# command = "cargo new --bin {{crate name}}"
26+#
27+# The value is quoted, so a path with a space in it stays one argument. Add ...
28+# inside the braces when you mean several arguments rather than one value:
29+#
30+# [[tool]]
31+# name = "Test ~o~ne"
32+# command = "cargo test {{extra flags...}}"
33+#
34+# Double braces, not single. Single ones appear in real commands — awk '{print
35+# $1}' and find . -exec rm {} + are both ordinary things to put here — and
36+# neither is asking you for anything.
37+#
38+# output says where what the command prints goes:
39+# popup a dialog that fills in as it runs, and says the exit code (default)
40+# terminal a terminal window, for anything that reads the keyboard or runs long
41+# editor an editing window once it has finished, to search with Ctrl-F
42+#
43+# Commands run in the directory the editor was started in, which is why they
44+# see the whole workspace when you start from its root.
45+
46+[[tool]]
47+name = "~F~ormat"
48+command = "cargo fmt"
49+output = "popup"
50+
51+[[tool]]
52+name = "~L~int"
53+command = "cargo clippy --all-targets"
54+output = "popup"
55+
56+[[tool]]
57+name = "~B~uild"
58+command = "cargo build"
59+output = "popup"
60+
61+[[tool]]
62+name = "~T~est"
63+command = "cargo test"
64+output = "popup"
65+
66+[[tool]]
67+name = "~R~un"
68+command = "cargo run"
69+# A terminal, not a popup: a program that reads the keyboard has to be able to
70+# be answered, and one that runs long has to be able to be interrupted.
71+output = "terminal"
72+
73+# A tool naming a `menu` gets a menu of its own on the bar. Nothing above does,
74+# so every tool above is in the Rust menu. This one is in a menu called Tools,
75+# which appears between Rust and Help — that is the whole mechanism.
76+
77+[[tool]]
78+name = "~E~cho"
79+command = "echo 🎉 tada!"
80+menu = "Tools"
81+output = "terminal"
added rustlang-init-with-agents/README.md +1 -0
new file mode 100644
@@ -0,0 +1 @@
1+# Rustlang init with agents
new file mode 100644
@@ -0,0 +1 @@
1+# Rustlang init with agents
added rustlang-init/.turbo-rust/settings.toml +9 -0
new file mode 100644
@@ -0,0 +1,9 @@
1+# turbo-rust project settings.
2+#
3+[editor]
4+
5+theme = "catppuccin-latte"
6+
7+autosave = true
8+
9+autosave_delay = "1s"
new file mode 100644
@@ -0,0 +1,9 @@
1+# turbo-rust project settings.
2+#
3+[editor]
4+
5+theme = "catppuccin-latte"
6+
7+autosave = true
8+
9+autosave_delay = "1s"
added rustlang-init/.turbo-rust/snippets.toml +59 -0
new file mode 100644
@@ -0,0 +1,59 @@
1+# turbo-rust snippets.
2+#
3+# Each [[snippet]] becomes one line of the Snippets menu. Snippets sharing a
4+# group appear together in a submenu of that name; one with no group goes into
5+# General. A snippet is inserted at the cursor, and every line after the
6+# first is indented to match the line you inserted it on.
7+#
8+# languages restricts a snippet to files of those kinds, by the names the
9+# editor uses: rust, toml, yaml, markdown, javascript, html, xml, dockerfile,
10+# bash. Leave it out and the snippet is offered everywhere.
11+#
12+# Your own snippets, shared across every project, go in:
13+# /Users/k33g/Library/Application Support/turbo-rust/snippets.toml
14+
15+[[snippet]]
16+name = "match"
17+group = "Rust"
18+languages = ["rust"]
19+body = """
20+match value {
21+ Some(v) => v,
22+ None => return,
23+}"""
24+
25+[[snippet]]
26+name = "if let"
27+group = "Rust"
28+languages = ["rust"]
29+body = """
30+if let Some(v) = value {
31+}"""
32+
33+[[snippet]]
34+name = "propagate the error"
35+group = "Rust"
36+languages = ["rust"]
37+body = "let value = fallible()?;"
38+
39+[[snippet]]
40+name = "derive"
41+group = "Rust"
42+languages = ["rust"]
43+body = "#[derive(Debug, Clone, PartialEq)]"
44+
45+[[snippet]]
46+name = "test module"
47+group = "Rust"
48+languages = ["rust"]
49+body = """
50+#[cfg(test)]
51+mod tests {
52+ use super::*;
53+
54+ #[test]
55+ fn it_works() {
56+ assert_eq!(1 + 1, 2);
57+ }
58+}"""
59+
new file mode 100644
@@ -0,0 +1,59 @@
1+# turbo-rust snippets.
2+#
3+# Each [[snippet]] becomes one line of the Snippets menu. Snippets sharing a
4+# group appear together in a submenu of that name; one with no group goes into
5+# General. A snippet is inserted at the cursor, and every line after the
6+# first is indented to match the line you inserted it on.
7+#
8+# languages restricts a snippet to files of those kinds, by the names the
9+# editor uses: rust, toml, yaml, markdown, javascript, html, xml, dockerfile,
10+# bash. Leave it out and the snippet is offered everywhere.
11+#
12+# Your own snippets, shared across every project, go in:
13+# /Users/k33g/Library/Application Support/turbo-rust/snippets.toml
14+
15+[[snippet]]
16+name = "match"
17+group = "Rust"
18+languages = ["rust"]
19+body = """
20+match value {
21+ Some(v) => v,
22+ None => return,
23+}"""
24+
25+[[snippet]]
26+name = "if let"
27+group = "Rust"
28+languages = ["rust"]
29+body = """
30+if let Some(v) = value {
31+}"""
32+
33+[[snippet]]
34+name = "propagate the error"
35+group = "Rust"
36+languages = ["rust"]
37+body = "let value = fallible()?;"
38+
39+[[snippet]]
40+name = "derive"
41+group = "Rust"
42+languages = ["rust"]
43+body = "#[derive(Debug, Clone, PartialEq)]"
44+
45+[[snippet]]
46+name = "test module"
47+group = "Rust"
48+languages = ["rust"]
49+body = """
50+#[cfg(test)]
51+mod tests {
52+ use super::*;
53+
54+ #[test]
55+ fn it_works() {
56+ assert_eq!(1 + 1, 2);
57+ }
58+}"""
59+
added rustlang-init/.turbo-rust/tools.toml +81 -0
new file mode 100644
@@ -0,0 +1,81 @@
1+# turbo-rust tools.
2+#
3+# Each [[tool]] becomes one line of the Rust menu, in the order they appear
4+# here. name is what the menu shows; a letter between tildes is its hot key, and
5+# no two tools should claim the same one.
6+#
7+# command goes to "sh -c", so pipes, globs and && work: one entry can be a
8+# whole sequence.
9+#
10+# menu says which menu it appears in. Leave it out and the tool goes into the
11+# Rust menu; name anything else and that menu is created for you, in the order
12+# the names first appear here. A tool that has nothing to do with Rust belongs
13+# in one of your own:
14+#
15+# [[tool]]
16+# name = "~E~cho"
17+# command = "echo TADA"
18+# menu = "Tools"
19+#
20+# A {{label}} in a command is a value the editor asks for before running it, in
21+# a box titled after the tool. The text between the braces is what it asks for:
22+#
23+# [[tool]]
24+# name = "~N~ew binary"
25+# command = "cargo new --bin {{crate name}}"
26+#
27+# The value is quoted, so a path with a space in it stays one argument. Add ...
28+# inside the braces when you mean several arguments rather than one value:
29+#
30+# [[tool]]
31+# name = "Test ~o~ne"
32+# command = "cargo test {{extra flags...}}"
33+#
34+# Double braces, not single. Single ones appear in real commands — awk '{print
35+# $1}' and find . -exec rm {} + are both ordinary things to put here — and
36+# neither is asking you for anything.
37+#
38+# output says where what the command prints goes:
39+# popup a dialog that fills in as it runs, and says the exit code (default)
40+# terminal a terminal window, for anything that reads the keyboard or runs long
41+# editor an editing window once it has finished, to search with Ctrl-F
42+#
43+# Commands run in the directory the editor was started in, which is why they
44+# see the whole workspace when you start from its root.
45+
46+[[tool]]
47+name = "~F~ormat"
48+command = "cargo fmt"
49+output = "popup"
50+
51+[[tool]]
52+name = "~L~int"
53+command = "cargo clippy --all-targets"
54+output = "popup"
55+
56+[[tool]]
57+name = "~B~uild"
58+command = "cargo build"
59+output = "popup"
60+
61+[[tool]]
62+name = "~T~est"
63+command = "cargo test"
64+output = "popup"
65+
66+[[tool]]
67+name = "~R~un"
68+command = "cargo run"
69+# A terminal, not a popup: a program that reads the keyboard has to be able to
70+# be answered, and one that runs long has to be able to be interrupted.
71+output = "terminal"
72+
73+# A tool naming a `menu` gets a menu of its own on the bar. Nothing above does,
74+# so every tool above is in the Rust menu. This one is in a menu called Tools,
75+# which appears between Rust and Help — that is the whole mechanism.
76+
77+[[tool]]
78+name = "~E~cho"
79+command = "echo 🎉 tada!"
80+menu = "Tools"
81+output = "terminal"
new file mode 100644
@@ -0,0 +1,81 @@
1+# turbo-rust tools.
2+#
3+# Each [[tool]] becomes one line of the Rust menu, in the order they appear
4+# here. name is what the menu shows; a letter between tildes is its hot key, and
5+# no two tools should claim the same one.
6+#
7+# command goes to "sh -c", so pipes, globs and && work: one entry can be a
8+# whole sequence.
9+#
10+# menu says which menu it appears in. Leave it out and the tool goes into the
11+# Rust menu; name anything else and that menu is created for you, in the order
12+# the names first appear here. A tool that has nothing to do with Rust belongs
13+# in one of your own:
14+#
15+# [[tool]]
16+# name = "~E~cho"
17+# command = "echo TADA"
18+# menu = "Tools"
19+#
20+# A {{label}} in a command is a value the editor asks for before running it, in
21+# a box titled after the tool. The text between the braces is what it asks for:
22+#
23+# [[tool]]
24+# name = "~N~ew binary"
25+# command = "cargo new --bin {{crate name}}"
26+#
27+# The value is quoted, so a path with a space in it stays one argument. Add ...
28+# inside the braces when you mean several arguments rather than one value:
29+#
30+# [[tool]]
31+# name = "Test ~o~ne"
32+# command = "cargo test {{extra flags...}}"
33+#
34+# Double braces, not single. Single ones appear in real commands — awk '{print
35+# $1}' and find . -exec rm {} + are both ordinary things to put here — and
36+# neither is asking you for anything.
37+#
38+# output says where what the command prints goes:
39+# popup a dialog that fills in as it runs, and says the exit code (default)
40+# terminal a terminal window, for anything that reads the keyboard or runs long
41+# editor an editing window once it has finished, to search with Ctrl-F
42+#
43+# Commands run in the directory the editor was started in, which is why they
44+# see the whole workspace when you start from its root.
45+
46+[[tool]]
47+name = "~F~ormat"
48+command = "cargo fmt"
49+output = "popup"
50+
51+[[tool]]
52+name = "~L~int"
53+command = "cargo clippy --all-targets"
54+output = "popup"
55+
56+[[tool]]
57+name = "~B~uild"
58+command = "cargo build"
59+output = "popup"
60+
61+[[tool]]
62+name = "~T~est"
63+command = "cargo test"
64+output = "popup"
65+
66+[[tool]]
67+name = "~R~un"
68+command = "cargo run"
69+# A terminal, not a popup: a program that reads the keyboard has to be able to
70+# be answered, and one that runs long has to be able to be interrupted.
71+output = "terminal"
72+
73+# A tool naming a `menu` gets a menu of its own on the bar. Nothing above does,
74+# so every tool above is in the Rust menu. This one is in a menu called Tools,
75+# which appears between Rust and Help — that is the whole mechanism.
76+
77+[[tool]]
78+name = "~E~cho"
79+command = "echo 🎉 tada!"
80+menu = "Tools"
81+output = "terminal"
added rustlang-init/README.md +1 -0
new file mode 100644
@@ -0,0 +1 @@
1+# Rustlang init
\ No newline at end of file
new file mode 100644
@@ -0,0 +1 @@
1+# Rustlang init
\ No newline at end of file\ No newline at end of file