Settings ​

GraphoOS is configured in settings.toml (open it with Open Settings File, or use the settings page: Open Settings, which has a search box). Every key below lives under its [section]; the value shown is the default. TOML, not JSON: comments are #, strings are quoted, and a missing key is the default.

Where settings live ​

• Yours, in the configuration directory: Open Settings File. That is the file to edit for this machine. Next to it live keymaps.toml (Open Keyboard Shortcuts), snippets/ (Open User Snippets), colour themes you import, and a fonts/ folder for faces this editor should load without installing them in the system.
• This workspace's, in .graphoos/settings.toml: Open Workspace Settings File, which creates the file if it is not there. They win over yours while the folder is open, they are meant to be committed, and editing the file applies them at once — no reopening the window.

The palette always opens the right file. If you need the path (* is the release channel of this build):

• macOS: ~/Library/Application Support/dev.graphoos.GraphoOS*/settings.toml
• Linux: ~/.config/graphoos*/settings.toml
• Windows: %APPDATA%\graphoos\GraphoOS*\settings.toml
• GRAPHOOS_DATA_DIR moves the whole profile (settings, plugins, caches, logs) to that folder.

The default file starts with #:schema ../extra/schemas/settings.json. That JSON Schema is generated with this page. Point the same directive at a copy of the schema so the editor that opens settings.toml can check keys as you type.

A working example ​

A workspace file only needs the keys this project disagrees with the defaults on. Leave API keys out of anything you commit: use the environment or the keychain (see Keys).

#:schema extra/schemas/settings.json

[editor]
font-size = 13
tab-width = 4
format-on-save = true
rulers = [100]
files-exclude = "**/{.git,node_modules,target,dist,.venv}"

[editor.formatters]
rust = "rustfmt --edition 2024"
python = "black -q -"
javascript = "prettier --stdin-filepath {file}"

[terminal]
font-size = 13

[terminal.env]
EDITOR = "graphoos --wait"

[ui]
language = "en"
density = "Compact"

[ai]
offline = false
chat-provider = "local"
inline-completion-provider = "local"

Coming from VS Code ​

Import Settings from VS Code reads your settings.json and this workspace's .vscode/settings.json (comments and trailing commas included) and writes the keys that mean the same thing here: font, tab width, rulers, wrapping, format on save, breadcrumbs, indent guides, sticky scroll, inlay hints, autosave and the terminal font. Everything else is listed by name instead of being guessed at, so nothing arrives translated into something it is not. What was already in your settings file is kept.

The keyboard from VS Code ​

Import Keyboard Shortcuts from VS Code reads its keybindings.json and appends the shortcuts whose commands exist here to your keymap file, keeping what is already in it: cmd becomes meta, chords stay chords (cmd+k cmd+s), the when of each binding is kept, and every command with no equivalent here is named in the message rather than dropped in silence — a shortcut that quietly does nothing is worse than one that is missing.

A theme from VS Code ​

Import a Colour Theme from VS Code takes the theme's .json open in the editor — one from an extension, or the file VS Code writes with Generate Color Theme From Current Settings — and writes it as a theme of ours in the themes directory, mapping the colors and the TextMate scopes of tokenColors onto the keys used here. It then appears in Change Color Theme. What has no equivalent is counted, not guessed at.

Generated by scripts/gen_docs.py from the editor's sources; edit those, not this file.

[core] — Core ​

Modal editing, themes and the window.

[editor] — Editor ​

Fonts, wrapping, completion, formatting, blame and more.

[terminal] — Terminal ​

The integrated terminal and its profiles.

[ui] — UI ​

Fonts and sizes of the interface, panels and tabs.

[ai] — AI ​

AiloOS providers, the assistant, the agent and ghost text.

[editor.formatters] ​

External formatters by language id: a command that reads the file on stdin and writes the formatted text on stdout ({file} in the command is replaced by the path). Used by Format Document and by format-on-save when the language server has no formatter. When a language has an entry here, it is used instead of the language server.

[editor.formatters]
rust = "rustfmt --edition 2024"
python = "black -q -"
go = "gofmt"
javascript = "prettier --stdin-filepath {file}"

[terminal.profiles] and [terminal.env] ​

Named shells for the terminal panel. [terminal.default-profile] picks one per OS (macos, linux, windows). Each profile may set command, arguments, environment and workdir.

[terminal.default-profile]
macos = "default"
linux = "default"
windows = "default"

[terminal.profiles]
default = {}

[terminal.profiles.cargo]
command = "cargo"
arguments = ["run"]
workdir = "/home/user"
environment = { KEY = "VALUE" }

[terminal.env] is added to every terminal. [terminal.env-macos], [terminal.env-linux] and [terminal.env-windows] win on that system, the same way VS Code's terminal.integrated.env.* does. Full behaviour of the panel is in Terminal.

Plugin settings ​

Each plugin adds its own section named after it (for example [graphoos-c]), with the keys its volt.toml declares; the plugin's page in the Plugins panel edits them. How to write one: Writing a plugin.

The rest of the workspace ​

settings.toml is only the editor. Developers also keep these files next to the project. Deep behaviour lives on the pages linked; this table is the map.

Assistant, agent, index and MCP: Assistant and AI.

Markdown you can copy ​

Paste these as they are. The assistant reads them as instructions (not as attached data). Each block is one file.

AGENTS.md — workspace root. Travels with every message, before .graphoos/rules.

# Agent

- Prefer this workspace's own tools (`cargo`, `npm`, `make`).
- Do not commit secrets, API keys or `.env`.
- After a code change, run the project's check (`cargo test`, `npm test`, …) before calling the task done.

.graphoos/rules.md — extra rules for this editor. .graphoos/rules/*.md are concatenated after it.

Answer in the language of the request.
Keep diffs small. Do not refactor files you were not asked to touch.

.graphoos/memory.md — /remember <note> appends a dated line. Edit freely.

# Memory

<!-- `/remember` appends here. The assistant reads this file with the project rules. -->

.graphoos/spec.md — /spec creates this template (the editor writes it in Spanish) and opens it. The agent reads it before each task.

# Especificación — {project}

<!-- El agente lee este fichero antes de tocar código y pregunta si falta algo. -->

## Objetivo

<!-- Qué problema resuelve el cambio y para quién, en dos frases. -->

## Invariantes

<!-- Lo que NUNCA puede romperse. Una línea por invariante, comprobable. -->
- 

## Criterios de aceptación

<!-- Cómo se sabe que está hecho. Cada uno debería poder ser un test. -->
- [ ] 

## Fuera de alcance

<!-- Lo que el agente no debe tocar aunque parezca relacionado. -->
- 

## Notas

.graphoos/skills/rust-tests.md — a skill. name, description and triggers in the frontmatter; the body is the procedure. User-wide copy: ~/.ailoos/skills/.

---
name: rust-tests
description: Run and write Rust tests in this workspace
triggers: [test, cargo test]
---
1. `cargo test` at the workspace root.
2. If a test fails, read the file and the assertion before changing anything else.
3. Do not ignore a failing test to make the suite green.

.graphoos/first-prompt.md — New Project… → Describe it to the agent writes your description here. The file is the prompt, nothing around it.

Build a CLI that reads a folder and prints a tree of its files. Rust, clap, tests.

Keys, not in the TOML ​

Do not commit API keys in .graphoos/settings.toml.

• ai.ailoos-api-key empty → AILOOS_API_KEY.
• ai.custom-api-key empty → GRAPHOOS_AI_API_KEY.
• [ai.providers.<name>] with api-key empty → the key kept by AI: Keep an API Key in the Keychain… (the system keychain, not the file).
• ai.offline = true never contacts AiloOS in the cloud; only the local server (ai.local-endpoint, default http://127.0.0.1:8080/v1) answers.

The assistant blanks recognisable secrets before text leaves the machine. Put keys in the environment or the keychain, not in a committed file.

See also ​

• Keyboard shortcuts
• Terminal
• Run and debug
• Assistant and AI
• Writing a plugin

Source: docs/settings.md