API for managing tasks within a project. Tasks represent units of work to be performed by an agent.
Request
- Base URL: https://us.posthog.com
- URL: https://us.posthog.com/api/projects/{project_id}/tasks/{id}/
- Auth: one of:
- HTTP bearer
- HTTP bearer
Path parameters
Project ID of the project you're trying to access. To find the ID of the project, make a call to /api/projects/.
Request body
Short human-readable title. Auto-generated from description when omitted.
Whether the title was set by a human (vs auto-generated from the description).
Free-form description of the work to be done. Used as the prompt passed to the agent.
- onboarding - Onboarding
- error_tracking - Error Tracking
- eval_clusters - Eval Clusters
- user_created - User Created
- slack - Slack
- support_queue - Support Queue
- session_summaries - Session Summaries
- posthog_ai - PostHog AI
- experiments - Experiments
- signal_report - Signal Report
- autoresearch - Autoresearch
- signals_scout - Signals Scout
- scout_suggestions - Signals Scout Suggestions
- support_reply - Support Reply
- hogdesk - HogDesk
- review_hog - ReviewHog
- image_builder - Image Builder
- loop - Loop
- mcp_analytics - MCP Analytics
- signals_chat - Signals Chat
- task_analysis - Task Analysis
- workflow - Workflow
- space_setup - Space Setup
- business_knowledge - Business Knowledge
- metrics_import - Metrics Import
Target GitHub repository in organization/repo format (e.g. posthog/posthog-js).
GitHub repositories available to this task, each in organization/repo format.
GitHub integration for this task.
User-scoped GitHub integration to use for user-authored cloud runs.
Signal report this task implements, when created from a report.
How the created task relates to the signal report (e.g. 'implementation', 'discussion'). Recorded as a signals task_run work-log entry; 'implementation' also opens the auto-start spend gate. Any routing-safe identifier (lowercase letters, numbers, '_', '-') is accepted except labels reserved for server-created tasks ('research', 'repo_selection', 'scout'). Non-implementation labels count toward the report's discussion task limit.
If true, the task is hidden from default list responses.
Custom prompt for CI fixes. If blank, a default prompt will be used.
Base branch for the first run when start_run is true, or for matching a pre-warmed run. Omit to use the repository's default branch. Write-only and not persisted on the task.
LLM model for the first run when start_run is true, or for matching a pre-warmed run. Write-only.
First user message when start_run is true or creation reuses a pre-warmed run. This message can differ from description. Ignored if creation does not start a run. Write-only and not persisted on the task.
Run artifact ids (already uploaded to the pre-warmed Run) to attach to the forwarded first message when creation reuses that warm Run, e.g. skill bundles or file attachments. If any id is missing from the warm Run's manifest, warm reuse is skipped and the task is created cold. Ignored when no warm Run is matched. Not supported when start_run is true.
When true, the agent pushes its work and opens a draft pull request on completion without an explicit request. Applies when start_run is true or creation reuses a pre-warmed run. Resumed runs keep this setting. Ignored if creation does not start a run. Write-only and not persisted on the task.
Channel this task is owned by (the channel it was kicked off in).
Response
- acp - ACP
- pi - Pi
Stable key of the server-side flow that created this task, e.g. desktop_onboarding_session:<user_id>. Null for tasks people create themselves.
Changes
No recorded changes to this operation across all 1 revision of this API.