Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

amodal dev

Start a local runtime server for development. The server watches your repo config files and hot-reloads on every change.

amodal dev

Options

FlagDefaultDescription
--port3847Server port
--hostlocalhostServer host
--resumeResume a previous session by ID or latest
-vIncrease log verbosity (-v for debug, -vv for trace)
-q / --quietOnly show errors

Log Levels

The default log level is info — startup messages, connection status, and warnings. Use -v or -vv to see more, or -q to see less.

FlagLevelWhat you see
-qerrorErrors and fatal only
(default)infoStartup, connections, warnings
-vdebugSession init, MCP, store ops, config reload
-vvtraceTool execution, upstream library output

You can also set the LOG_LEVEL environment variable (trace, debug, info, warn, error, fatal, none). The env var takes precedence over CLI flags.

# Quiet mode
amodal dev -q
 
# Debug output
amodal dev -v
 
# Full trace (including upstream library noise)
amodal dev -vv
 
# Via environment variable
LOG_LEVEL=debug amodal dev

What It Does

  1. Loads your repo configuration from the project root
  2. Starts an Express server with SSE streaming
  3. Watches all config files with 300ms debounce
  4. Manages sessions with TTL-based cleanup

Endpoints

The dev server exposes:

MethodPathDescription
POST/chatSend a message, receive SSE stream
POST/taskStart a background task
GET/task/:idGet task status
GET/task/:id/streamStream task output
GET/inspect/contextView compiled context with token counts
GET/healthHealth check

SSE Events

The chat endpoint returns a Server-Sent Events stream with these event types:

EventDescription
textAssistant text output
tool_callTool invocation
ExploreStart / ExploreEndSystem exploration phase
PlanModePlanning phase
skill_activatedSkill activation
FieldScrubSensitive field redaction
ConfirmationRequiredWrite operation needs approval
kb_proposalKnowledge base update proposal

Hot Reload

Edit any config file and the runtime picks up changes immediately:

  • Connection specs, skills, knowledge, tools, automations
  • Config changes (provider, model, etc.)
  • No server restart needed