import { createSubsystemLogger } from "../../logging/subsystem.js";

import { collectEnabledInsecureOrDangerousFlags } from "../../security/dangerous-config-flags.js";

import { normalizeOptionalString, readStringValue } from "../../shared/string-coerce.js";

import { optionalStringEnum, stringEnum } from "../schema/typebox.js";

import { stringEnum } from "../schema/typebox.js";

import { type AnyAgentTool, jsonResult, readStringParam } from "./common.js";

import { callGatewayTool, readGatewayCallOptions } from "./gateway.js";

import { isOpenClawOwnerOnlyCoreToolName } from "./owner-only-tools.js";

// restart

delayMs: Type.Optional(Type.Number()),

reason: Type.Optional(Type.String()),

continuationKind: optionalStringEnum(["systemEvent", "agentTurn"] as const),

continuationMessage: Type.Optional(Type.String()),

// config.get, config.schema.lookup, config.apply, update.run

gatewayUrl: Type.Optional(Type.String()),

name: "gateway",

ownerOnly: isOpenClawOwnerOnlyCoreToolName("gateway"),

description:

"Restart, inspect a specific config schema path, apply config, or update the gateway in-place (SIGUSR1). Use config.schema.lookup with a targeted dot path before config edits. Use config.patch for safe partial config updates (merges with existing). Use config.apply only when replacing entire config. Config writes hot-reload when possible and restart when required. Always pass a human-readable completion message via the `note` parameter so the system can deliver it to the user after restart. If restarting during a user task and you still owe the user a reply, pass a specific one-shot `continuationMessage` for what to verify or report after boot; do not write restart sentinel files directly. Use `continuationKind` only when it should be a system event instead of a normal agent turn.",

"Restart, inspect a specific config schema path, apply config, or update the gateway in-place (SIGUSR1). Use config.schema.lookup with a targeted dot path before config edits. Use config.patch for safe partial config updates (merges with existing). Use config.apply only when replacing entire config. Config writes hot-reload when possible and restart when required. Always pass a human-readable completion message via the `note` parameter so the system can deliver it to the user after restart. If restarting during a user task and you still owe the user a reply, pass a specific one-shot `continuationMessage` for what to verify or report after boot; do not write restart sentinel files directly.",

parameters: GatewayToolSchema,

execute: async (_toolCallId, args) => {

const params = args as Record<string, unknown>;

const reason = normalizeOptionalString(params.reason)?.slice(0, 200);

const note = normalizeOptionalString(params.note);

const continuationMessage = normalizeOptionalString(params.continuationMessage);

const continuationKind = normalizeOptionalString(params.continuationKind);

// Extract channel + threadId for routing after restart.

// Uses generic :thread: parsing plus plugin-owned session grammars.

const { deliveryContext, threadId } = extractDeliveryInfo(sessionKey);

message: note ?? reason ?? null,

continuation: buildRestartSuccessContinuation({

sessionKey,

continuationKind,

continuationMessage,

}),

doctorHint: formatDoctorNonInteractiveHint(),