config.example.toml

default_provider = "deepseek"
 
[providers.deepseek]
type = "openai"
api_key = "sk-..."
model = "deepseek-chat"
base_url = "https://api.deepseek.com/v1"
context_window = 64000
# Override the reasoning_content history-echo policy. Unset = auto-detect
# from model name (deepseek-v4* → include, deepseek-reasoner/r1 → exclude,
# kimi-* / moonshot → include, rest → exclude). Set explicitly when hitting
# a 400 like "reasoning_content ... must be passed back to the API" or
# "reasoning_content is missing in assistant tool call message".
# reasoning_history = "include"  # or "exclude"
# reasoning_effort = "high"

# Per-turn datalog. Each turn writes a markdown summary; each LLM
# round writes a JSON request/response pair under `<dir>/<project>/llm/`.
# A per-project subdirectory is always appended under `dir` so multiple
# projects never share a bucket.
# - enabled = false        -> disable logging entirely
# - dir = "~/.atomcode/datalog" -> default (follows $HOME, ignores /cd)
# - dir = "/abs/path"      -> absolute, fixed (unaffected by /cd)
# - dir = "rel/path"       -> joined with current working_dir, follows /cd
[datalog]
enabled = true
dir = "~/.atomcode/datalog"

# Long-running task completion notifications.
# Strategy: terminal-native notifications first (kitty / WezTerm / iTerm2),
# then OS-native fallback when available (macOS osascript, Linux notify-send).
# Windows mainly relies on BEL + terminal attention/taskbar flash.
# `background_only` is best-effort: focus-aware terminal protocols honor it,
# while some OS fallbacks may still notify even if AtomCode is focused.
[notifications]
enabled = true
min_duration_secs = 8
terminal = true
system = true
bell = true
background_only = true

# Network proxy policy shared by every outbound HTTP client.
# - "follow_system" -> follow the launch environment / system proxy state
# - "default_proxy" -> pin the values below and reuse them on later launches
# - "no_proxy"      -> disable proxy resolution entirely
[network.proxy]
mode = "no_proxy"
# http = "http://127.0.0.1:7890"
# https = "http://127.0.0.1:7890"
# all = "socks5://127.0.0.1:7890"
# no_proxy = "localhost,127.0.0.1"

# Lifecycle hooks — run custom scripts on key events.
# Hooks are NOT configured in this file. Use separate config files instead:
#   TOML: ~/.atomcode/hooks/hooks.toml (recommended, supports ScriptHook + Webhook)
#   JSON: ~/.atomcode/hooks.json (CC-compatible, lightweight)
# See docs/hooks.md for full reference.
#
# Available events (JSON CC format; TOML ScriptHook uses different trigger names — see docs/hooks.md):
#   pre_tool_use    — before each tool call (can block via stdout {"action":"block","reason":"..."})
#   post_tool_use   — after each tool call
#   user_prompt_submit — when the user submits a prompt (can block via stdout {"decision":"block","reason":"..."} or inject context via {"hookSpecificOutput":{"additionalContext":"..."}})
#   session_start   — when a new session begins
#   session_end     — when a session ends
#
# JSON CC scripts receive context via env vars: ATOMCODE_HOOK_EVENT, ATOMCODE_TOOL_NAME,
# ATOMCODE_HOOK_CONTEXT (JSON string). TOML ScriptHook uses stdin instead — see docs/hooks.md.
# JSON CC PreToolUse stdout supports (TOML ScriptHook uses text protocol ok/deny:/modify: — see docs/hooks.md):
#   {"action":"allow"} or {"action":"block","reason":"..."} or {"action":"modify","args":{...}}
#
# Example ~/.atomcode/hooks.json (JSON CC format; TOML uses [[hooks]] with trigger/script/timeout_secs — see docs/hooks.md):
# {
#   "hooks": {
#     "verify-gate": {
#       "event": "post_tool_use",
#       "command": "python ~/.atomcode/scripts/verify-gate.py",  # ~ 不会自动展开，需用绝对路径（如 C:\Users\you\.atomcode\scripts\verify-gate.py 或 /home/you/.atomcode/scripts/verify-gate.py）
#       "timeout_ms": 30000  # default is 10000 (10s); set 30s here because verify may be slow
#     }
#   }
# }