Skip to main content
The root configuration file (.hyperterse) defines service-level settings and discovery settings. Adapter and tool definitions are discovered from the filesystem, and prompts/resources can be configured through discovery directories or optional inline lists.

Full schema

.hyperterse

Field reference

name
string
required
Service identifier. Used in logging, tracing, and manifest metadata. Must match ^[a-z][a-z0-9_-]*$.
version
string
Service version. Informational. Included in manifest metadata and startup logs.
root
string
default:"app"
Base directory for adapter/tool discovery. Relative to the root config path.
tools
object
Tool discovery and global tool cache defaults.
adapters
object
Adapter discovery settings.
prompts
object | array
Prompt configuration:
resources
object | array
Resource configuration:
resource_templates
array
Optional inline URI-template resources. Each item defines uri_template, metadata, template content (text_template or file_template), and optional arguments.
agents
object
Agent discovery settings and project-level default tool access policy.
For file-based prompt/resource configs, see Prompt configuration and Resource configuration.
server
object
Server runtime settings.
build
object
Build output settings.

Environment variable substitution

String values support {{ env.VAR_NAME }} placeholders, resolved at runtime:
Missing variables cause a startup failure. Verify all referenced variables are set before deploying.

JSON Schema

Editor validation: schema/root.terse.schema.json. See Configuration schemas.

Examples

.hyperterse
All other fields use defaults: port 8080, log level 3, caching disabled.