All commands loadDocumentation Index
Fetch the complete documentation index at: https://docs.hyperterse.com/llms.txt
Use this file to discover all available pages before exploring further.
.env files from the working directory when present.
Print the installed version and exit.
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 → 3Sets log level to
4 (debug). Overrides --log-level.Configuration as an inline YAML string instead of reading from a file.Short:
-sHot-reload on
.terse and .ts file changes. Recompiles and restarts
automatically.Comma-separated tag filter. Prefix a tag with
- to exclude it.Stream logs to
/tmp/.hyperterse/logs/ in addition to stdout.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: -pLog verbosity. Overrides the value embedded in the manifest.
Sets log level to
4 (debug).Comma-separated tag filter.
Stream logs to file.
Examples
hyperterse build
Compile the project into a deployable output directory.
.hyperterse from the current directory.
Flags
Output directory for build artifacts.Short:
-oRemove the output directory before building.
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
Configuration as an inline YAML string instead of reading from a file.Short:
-sChecks
- 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
| Code | Meaning |
|---|---|
0 | Validation passed |
1 | Validation failed — errors printed to stderr |
Examples
hyperterse init
Scaffold a new project with starter files.
Created files
| Path | Content |
|---|---|
.hyperterse | Root config with defaults |
app/tools/hello-world/config.terse | Hello world script-backed tool |
app/tools/hello-world/handler.ts | TypeScript handler |
.agents/skills/hyperterse-docs/SKILL.md | Agent Skills skill pointing to docs |
.agents/skills/hyperterse-agents/SKILL.md | Agent Skills skill for creating agents with Hyperterse |
Does not overwrite existing files.
hyperterse upgrade
Upgrade the installed binary.
Flags
Include pre-release versions in the upgrade check.
Target a specific major version number, or
next for the latest major.