.env files from the working directory when present.
hyperterse start
Read config, validate the project, package tool scripts, open database connections, and start the HTTP server (MCP and optional A2A routes).
.hyperterse from the current directory. A positional path can point to a directory containing .hyperterse or directly to a config file.
Flags
Server port. Overrides config and
PORT env var.Short: -pResolution order: --port → server.port → PORT env → 8080Log verbosity.
1 = error, 2 = warn, 3 = info, 4 = debug. Overrides config.Resolution order: --verbose (4) → --log-level → server.log_level → 3Hot-reload on
.terse and .ts file changes. Recompiles and restarts
automatically.Examples
hyperterse serve
Boot from a pre-built manifest without re-parsing source files.
model.bin in the current directory. A positional argument can point to a directory containing model.bin or directly to a manifest file.
Flags
Server port. Overrides the value embedded in the manifest and
PORT env var.Short: -pExamples
hyperterse build
Compile the project into a deployable output directory.
.hyperterse from the current directory.
Flags
Output
dist
hyperterse
model.bin
build
vendor.js
tools
<name>
handler.js
input_transform.js
output_transform.js
Examples
hyperterse validate
Check configuration and project structure without starting the server.
Flags
Checks
- Root config schema compliance
- Adapter completeness (
connectorandconnection_stringrequired) - Tool validity (exactly one of
useorhandler) - Adapter name uniqueness
- Input type correctness
- Script file resolution
- Bundle compilation
Exit codes
Examples
hyperterse init
Scaffold a new project with starter files.
Created files
Does not overwrite existing files.