---
title: "Continue a Mac-synced chat in the cloud"
method: POST
path: "/threads/{id}/continue-mirrored"
---

# Continue a Mac-synced chat in the cloud

`POST /threads/{id}/continue-mirrored`

## Request

- Base URL: `https://api.agentsky.dev/v1`
- URL: `https://api.agentsky.dev/v1/threads/{id}/continue-mirrored`
- Auth: HTTP bearer

Continue a chat synced from a Mac (the agent `columnId` names, the first when omitted) in the cloud, from the transcript the platform already holds, with `text` (and optional `files`) as the new session's first message, as a send on the web does. It stays the same chat: the new session's history starts with the synced conversation and `playgroundId` is this thread. The chat's owner and any workspace member who may use it can continue it; the new session is the caller's. Works with the Mac offline. 409 `continue_pending` means ask again with the same `requestId`; 422 `not_mirrored` when the chat did not come from a Mac.

## Path parameters

- `id` string, required

## Request body

- object
  - `requestId` string, required
  - `text` string
  - `files` object[]
  - `columnId` string
  - `timezone` string

## Response `201`

OK

- object
  - `playgroundId` string
  - `sessionId` string

## Other responses

- `400`: Error — { error: { code, message } }
- `401`: Error — { error: { code, message } }
- `403`: Error — { error: { code, message } }
- `404`: Error — { error: { code, message } }
- `409`: Error — { error: { code, message } }
- `422`: Error — { error: { code, message } }
- `default`: Error — { error: { code, message, request_id } }

## Changes

- **2026-11-02** `e5e8f0229a99`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/agentsky/apis/agentsky-developer-api/changes/threads/:id/continue-mirrored/post.md)

---

[API](https://skmtc.dev/agentsky/apis/agentsky-developer-api.md) - [All operations](https://skmtc.dev/agentsky/apis/agentsky-developer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/agentsky/apis/agentsky-developer-api/revisions/8280a065ef6a?raw)