Do I need Plus or API credits?

Custom GPTs and Actions require a paid ChatGPT plan from OpenAI; TaskPeace itself is free (Pro is $10/month). The REST API path works with any OpenAI tier that can make HTTP calls or with the OpenAI API directly.

The task manager for ChatGPT

Q: How do I connect ChatGPT to a task queue?

Two ways. (1) Build a custom GPT and import TaskPeace's OpenAPI spec at /api/openapi.json as an Action with a Bearer token — ChatGPT can then call get_next_task and complete_task itself. (2) Call the REST API directly from any chat: GET /api/next with your token, do the task, POST /api/tasks/{id}/complete. ChatGPT does support custom remote MCP connectors natively (Settings → Connectors, developer mode, on paid plans), but TaskPeace's bundled MCP server is a local stdio server — not a remote endpoint — so on ChatGPT use the custom-GPT Action or the REST API.

Q: Can ChatGPT work my tasks automatically?

Yes. With a custom GPT Action wired to TaskPeace, ChatGPT pulls the top unblocked task, works it, posts a result, and loops — running the one global priority queue top to bottom until it returns no task.

Give ChatGPT a real task queue. TaskPeace exposes one global priority list over a clean REST API (and MCP), so ChatGPT — via a custom GPT or a direct API call — pulls the next task, works it, and reports back. You set the order; it runs the list.

Open the board — free →

ChatGPT does support custom remote MCP connectors natively (Settings → Connectors, developer mode, on paid plans) — but TaskPeace's bundled MCP server is a local stdio server, not a remote endpoint, so on ChatGPT you connect through the custom-GPT Action or REST paths below.

Option A — a custom GPT (no code)

Create a GPT in ChatGPT → Configure → Actions.
Import the schema from https://taskpeace.com/api/openapi.json.
Set authentication to Bearer and paste your TaskPeace API token (from the in-app account menu).
Tell the GPT: "Work my TaskPeace queue: call get_next_task, do it, complete_task, repeat."

ChatGPT now reads and completes tasks from the same queue you see on the web board.

Option B — the REST API directly

GET  /api/next                       # → highest-priority task (Bearer token)
# …do the work…
POST /api/tasks/{id}/complete        # { "result": "what got done" }
# repeat until { "task": null }

This is the same loop your agent runs over MCP — just over HTTP. Full details in the API reference and the machine-readable OpenAPI spec.

Why route ChatGPT through a queue

One source of truth — the same ranked list humans, Claude Code and Cursor use.
Deterministic "next" — ChatGPT never has to guess what to work on; get_next_task answers it.
Results logged — every completion records a short result, so unattended runs stay auditable.
You stay in control — capture in the Inbox, rank what matters; ChatGPT only works ranked tasks.

Frequently asked questions

How do I connect ChatGPT to a task queue?

Either import TaskPeace's OpenAPI spec as a custom-GPT Action with a Bearer token, or call GET /api/next + POST /api/tasks/{id}/complete directly. ChatGPT's native remote MCP connectors need a remote endpoint — the bundled server is local stdio, so stick to the Action or REST paths here.

Can ChatGPT work my tasks automatically?

Yes — with the Action wired up it loops get_next_task → work → complete_task over your one priority queue.

Do I need a paid plan?

Custom GPTs/Actions need a paid ChatGPT plan from OpenAI; TaskPeace is free (Pro $10/mo). The REST path works from any HTTP-capable setup.

Start free — no card → How the queue works →