Skip to content

Entry points and services ​

Switches and listen addresses for ACP, Dashboard, and AppServer, plus operational logging. For AppServer in a running host, read AppServer mode; channel registration is in Channels.

Entry points ​

FieldDescriptionDefault
Acp.EnabledEnables ACP modefalse
DashBoard.EnabledEnables Dashboardtrue
DashBoard.HostDashboard listen address127.0.0.1
DashBoard.PortDashboard listen port8080
AppServer.ModeAppServer transport mode: Disabled, Stdio, WebSocket, or StdioAndWebSocketDisabled
AppServer.WebSocket.HostWebSocket listen host127.0.0.1
AppServer.WebSocket.PortWebSocket listen port9100
AppServer.WebSocket.TokenToken required by remote WebSocket clientsEmpty

Dashboard example:

json
{
  "DashBoard": {
    "Enabled": true,
    "Host": "127.0.0.1",
    "Port": 8080
  }
}

Logging ​

DotCraft writes workspace host diagnostics to <workspace>/.craft/logs and Hub diagnostics to ~/.craft/logs.

FieldDescriptionDefault
Logging.EnabledWrites operational diagnostics to rolling filestrue
Logging.ConsoleAlso writes diagnostics to the console. Protocol hosts use stderr so stdout remains protocol-onlyfalse
Logging.MinLevelMinimum level: Trace, Debug, Information, Warning, Error, or CriticalInformation
Logging.DirectoryLog directory relative to the host's .craft directorylogs
Logging.RetentionDaysDeletes older rolled files at startup; 0 disables cleanup7
DebugModePrints untruncated tool arguments in the consolefalse
json
{
  "Logging": {
    "Enabled": true,
    "Console": false,
    "MinLevel": "Information",
    "Directory": "logs",
    "RetentionDays": 7
  }
}

Operational logs contain timestamps, severity, process ID, category, messages, exceptions, and active diagnostic scopes. Raw ACP traffic and opt-in session stream debug records use separate files because they can contain sensitive or high-volume payloads.