任務 · MCP

Complete Task

complete_task is one of the 32 MCP tools in Weft, the AI task manager you run by talking to Claude, Cursor, Codex or ChatGPT through one MCP endpoint. The AI calls this when the work is actually finished — the card moves to Done with completion time recorded, and the optional outcome (what was done, where the result lives) is appended to the card as an "Outcome (AI, date)" note. No column id needed. Work marked as needing you does NOT move to Done: it goes to your queue with the receipt attached, and if the agent said what it would do next, accepting approves exactly that step and hands it back to the agent. If the task carries a verification plan, the server executes its checks right here — fetching the URL, looking for the quote, comparing the hash: an executable/state_delta plan whose blocking checks all pass closes verified by the server; a failed blocking check keeps the card out of Done and shows the agent what the server observed.

Weft 是為獨立創業者和小團隊打造的 AI 任務管理工具。

工具參考文件以英文維護:工具名稱、參數與範例在每種語言中都相同。

參數

名稱型別必填說明
iduuid是Task id to complete.
outcomestring否1-3 sentences: what was done and where the result lives.
artifacts{ kind, uri }[]否Evidence a person could check without trusting the account of it — a URL, a hash, a message id.
learnings(string | { trigger, content })[]否Up to 3 lessons worth remembering beyond this task — they become memory notes and surface in every future get_my_work, stamped with source and date.
nextStepstring否What the agent would do next if you accept (≤200 chars) — shown above the Accept button, so accepting approves exactly that.

回傳

The task, now in Done with completedAt set — or awaitingReview:true when it stopped at you instead.

註記

預設的寫入工具。這個工具會變更狀態;只要清楚使用者要什麼,MCP 客戶端可以自行呼叫。客戶端是否要求確認,由客戶端自行決定;Model Context Protocol 規格建議讓人參與其中,並保有拒絕工具呼叫的能力。

範例

使用者說的話:

"Mark the deploy task done — released in v1.2.0."

相關