karea_edit_task
Update an existing task's fields like title, status, priority, deadline, or add notes by specifying its ID or name. Only provided fields are modified.
Instructions
Update fields of an existing task (title, status, priority, deadline, category, assignee, description, tags, or add a note) located by visual ID, name or UUID. Only the fields you pass change; the rest are left untouched. Returns the updated task.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sla | No | New deadline | |
| name | No | New task title (rename the task) | |
| note | No | Add a human-readable note (the user reads these). Markdown is supported (lists, **bold**, `code`, links) - use it when it makes the note more readable; plain text is also fine. For private AI cross-session working memory use karea_set_context instead. | |
| tags | No | Tags to attach. STRICT: only pass tags that already exist in this project (check karea_view_task first). Do NOT invent new tags unless the user explicitly asked for one — the API upserts by name and typos create duplicates. When unsure, omit and ask. | |
| task | Yes | Task name, visual ID (C1, T2), or UUID | |
| status | No | New status: open, in_progress, blocked, review, done | |
| category | No | Move to category | |
| markdown | No | Long-form markdown content — use for investigation findings, technical/functional docs, solution design, root cause analysis. Overwrites existing markdown; read first with karea_get_markdown to append. | |
| priority | No | New priority | |
| toolType | No | Optional: your AI provider ("claude-code" / "opencode" / "codex" / "cursor" / "aider" / "other"). Required when aiSessionId is supplied. | |
| clearTags | No | Remove all existing tags before adding new ones | |
| projectId | No | Project name or ID | |
| aiSessionId | No | Optional: your current AI CLI session ID. When paired with toolType, atomically links this session to the affected task (equivalent to calling karea_link_session, but saves the round-trip). For Claude Code use the id from `claude --resume`. | |
| description | No | New description. Rendered as Markdown - use `**bold**`, lists, `code`, links, etc. Keep it short (a few sentences); use `markdown` for long-form docs. | |
| jiraIssueKey | No | JIRA issue key to link (e.g. PROJ-123). Set to "unlink" to remove. | |
| sessionLabel | No | Optional short label for the linked session (e.g. "Feature draft"). | |
| closingRequisites | No | Closing requisites to add. Keep each short and concrete - 1 short sentence, ideally under ~120 chars. Do NOT write paragraphs. | |
| clearClosingRequisites | No | Remove all existing closing requisites before adding new ones |