Project settings

A project's settings are edited in the console under the project's Settings and stored by the gateway. The JSON keys are the same in the console and in self-hosted configuration files. Unknown keys are refused.

Saving and conflicts

Every save names the revision it was edited from. If someone else saved the same settings in the meantime, the save is refused with 409 revision_conflict and the current revision and value. The console keeps your unsaved changes and lets you load the current values or replace them with yours; nothing is overwritten silently.

Ignored paths

JSON key: ignore, a list of patterns such as .git, build/, *.o or /out. Ignored files are never listed or searched, and tools treat them as if they did not exist.

Language profiles

JSON key: analysis, a map from profile name to:

Field	Meaning
provider	clangd, the only provider.
compilation_database	Optional project-relative path to a compile_commands.json supplied with the source.
include_paths	Project-relative include directories.
defines	Macro definitions, name to value. Names start with a letter or _.
standard	Optional language standard, such as c++23.
server.argv	The language-service executable and arguments, such as ["clangd", "--background-index"].
server.env	Optional environment variables for the language service.
build	The build graph that produces analysis inputs.
databases	Names of compilation-database outputs used for analysis.

A profile stores the analysis inputs and the language-service command. Saving it starts nothing; analysis is prepared only by an explicit language request. The language tool queries data for a profile by name, bound to a worldline version and the profile's environment fingerprint. When no analysis data covers that version, the tool reports analyzed: false rather than an empty success.

Limits

Limits apply to every project of a workspace. Operators edit the gateway's defaults under the console's Settings → Quotas. A workspace's owners can override any of them under the workspace's Settings → Source limits; an empty field keeps the gateway's value.

Field	Applies to	Default
max_file_bytes	One file written through the tools.	4 MiB
max_project_bytes	A project's files, including worldline data.	1 GiB
max_workspace_bytes	All of a workspace's projects.	10 GiB
max_projects	Projects per workspace.	100
read_max_lines	One read.	2000
read_max_bytes	One read.	256 KiB
list_max_entries	One list or glob.	2000
search_max_matches	One search.	200

A call that would go over a limit fails with a message saying which one. Settings → General → Effective values shows a project's resolved limits.