---
title: "Resume Autopilot"
method: POST
path: "/api/chats/{chat_id}/autopilot-resume"
tags: ["chats"]
---

# Resume Autopilot

`POST /api/chats/{chat_id}/autopilot-resume`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/chats/{chat_id}/autopilot-resume`
- Auth: none declared

Reset the caller's Autonomous streak in this chat and re-arm the reply.

Setting ``autopilot_resumed_at`` is what makes one click reset BOTH bounds:
eligibility ignores every message at or before that instant, so the turn
count restarts at zero and the time budget restarts from the next reply.

Clearing the guard is not enough on its own. Nothing else would fire until
a brand-new inbound message arrived, so the user would click "keep going"
and watch the conversation stay exactly as stopped as it was - the same
dead end, one click later. The resume therefore re-enqueues the auto-reply
for the conversation's current tail.

## Path parameters

- `chat_id` string, uuid, required

## Headers

- `x-impersonate-identity-id` string, nullable

## Request body

- AutopilotResumeRequest: Optional widening applied along with the reset. Both default to null, which means "reset the streak, keep my settings" - the plain "keep going" click.
  - `auto_reply_limit` integer, nullable
  - `window_seconds` integer, nullable

## Response `200`

Successful Response

- AutopilotResumeResponse
  - `resumed_at` string, date-time, required
  - `auto_reply_limit` integer, required
  - `window_seconds` integer, nullable, required
  - `reply_enqueued` boolean, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/thinqos/apis/thinqos-api.md) · [All operations](https://skmtc.dev/thinqos/apis/thinqos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/thinqos/apis/thinqos-api/revisions/5387b4ded614?raw)