import { MutagentCore } from "../core.js";
import { RequestOptions } from "../lib/sdks.js";
import { ConnectionError, InvalidRequestError, RequestAbortedError, RequestTimeoutError, UnexpectedClientError } from "../models/errors/http-client-errors.js";
import * as errors from "../models/errors/index.js";
import { MutagentError } from "../models/errors/mutagent-error.js";
import { ResponseValidationError } from "../models/errors/response-validation-error.js";
import { SDKValidationError } from "../models/errors/sdk-validation-error.js";
import * as operations from "../models/operations/index.js";
import { APIPromise } from "../types/async.js";
import { Result } from "../types/fp.js";
/**
 * Stop a running Helix session without destroying its sandbox
 *
 * @remarks
 * The remote equivalent of Ctrl-C on a local agent: the SESSION stops and the box — its filesystem, its other sessions, its event log — stays up. `DELETE /:id` remains the only thing that destroys a sandbox. Distinct from sending an `abort` command via `POST /:id/input`, which politely asks a cooperating agent to end its turn and only works while it is still reading stdin; a signal reaches a process that has stopped listening. 200 means the signal was delivered to a LIVE process, never merely that the request was well-formed. 409 if the session has already ended, 404 if the box has never heard of it.
 *
 * If set, this operation will use {@link Security.bearerAuth} from the global security.
 */
export declare function sandboxPostApiSandboxByIdSignal(client: MutagentCore, request: operations.PostApiSandboxByIdSignalRequest, options?: RequestOptions): APIPromise<Result<operations.PostApiSandboxByIdSignalResponse, errors.ErrorMessage | errors.ErrorMessageStatusCode | MutagentError | ResponseValidationError | ConnectionError | RequestAbortedError | RequestTimeoutError | InvalidRequestError | UnexpectedClientError | SDKValidationError>>;
//# sourceMappingURL=sandbox-post-api-sandbox-by-id-signal.d.ts.map