gradeNot graded
lumos-list-tasksAnswer
Lists the tasks in the user's Lumos panel task board (title, priority, status, optional schedule). Read-only: it never changes anything. Task content is private: the user must explicitly approve sharing the board with agents in the panel's own dialog. Without that consent this returns ok:false with reason 'read_consent_required' and NO task data — that is a refusal, not an empty board, so never report the board as empty. Consent lasts for the browser session and the user can revoke it from the panel at any time.
View tool JSON
{
"name": "lumos-list-tasks",
"kind": "answer",
"impl": "imperative",
"description": "Lists the tasks in the user's Lumos panel task board (title, priority, status, optional schedule). Read-only: it never changes anything. Task content is private: the user must explicitly approve sharing the board with agents in the panel's own dialog. Without that consent this returns ok:false with reason 'read_consent_required' and NO task data — that is a refusal, not an empty board, so never report the board as empty. Consent lasts for the browser session and the user can revoke it from the panel at any time.",
"inputSchema": {
"type": "object",
"properties": {}
},
"page": "/panel"
}lumos-propose-taskAction
Proposes a new task for the user's Lumos panel task board. The task is NOT created until the user approves it in the panel's own confirmation dialog. If the user declines, nothing is written and the result reports approved:false. Never claim the task exists unless ok is true. The result echoes the stored task only when the user has separately approved sharing the board (see lumos-list-tasks); otherwise ok:true arrives with no 'task' field and that still means it was written.
View tool JSON
{
"name": "lumos-propose-task",
"kind": "act",
"impl": "imperative",
"description": "Proposes a new task for the user's Lumos panel task board. The task is NOT created until the user approves it in the panel's own confirmation dialog. If the user declines, nothing is written and the result reports approved:false. Never claim the task exists unless ok is true. The result echoes the stored task only when the user has separately approved sharing the board (see lumos-list-tasks); otherwise ok:true arrives with no 'task' field and that still means it was written.",
"inputSchema": {
"type": "object",
"properties": {
"title": {
"type": "string",
"description": "Short task title, as the user would read it on the board."
},
"priority": {
"type": "string",
"enum": [
"dusuk",
"orta",
"yuksek"
],
"description": "Priority: dusuk (low), orta (medium, default), yuksek (high)."
},
"when": {
"type": "string",
"description": "Optional human-readable schedule hint shown on the task row, e.g. 'Yarın 14:00'."
}
},
"required": [
"title"
]
},
"page": "/panel"
}lumos-complete-taskAction
Marks an existing Lumos panel task as completed. This tool needs the user's board-sharing consent BEFORE it does anything: without that consent every call — valid ref, unknown ref, missing ref, or an already completed task — returns the exact same ok:false refusal with reason 'read_consent_required', no task is looked up and no confirmation dialog is shown. That refusal is NOT evidence that the task is missing or that the board is empty; do not report it as such — ask the user to approve sharing the board (see lumos-list-tasks) and then retry. Once sharing is approved the task is still NOT completed until the user approves it in the panel's own confirmation dialog; if the user declines, nothing is written and the result reports approved:false. A task that was already done comes back with reason 'already_completed' and nothing is written. Approving a completion is NOT permission to read the board: the result carries a 'task' field only while the sharing consent is in force. Use lumos-list-tasks first to get a valid ref.
View tool JSON
{
"name": "lumos-complete-task",
"kind": "act",
"impl": "imperative",
"description": "Marks an existing Lumos panel task as completed. This tool needs the user's board-sharing consent BEFORE it does anything: without that consent every call — valid ref, unknown ref, missing ref, or an already completed task — returns the exact same ok:false refusal with reason 'read_consent_required', no task is looked up and no confirmation dialog is shown. That refusal is NOT evidence that the task is missing or that the board is empty; do not report it as such — ask the user to approve sharing the board (see lumos-list-tasks) and then retry. Once sharing is approved the task is still NOT completed until the user approves it in the panel's own confirmation dialog; if the user declines, nothing is written and the result reports approved:false. A task that was already done comes back with reason 'already_completed' and nothing is written. Approving a completion is NOT permission to read the board: the result carries a 'task' field only while the sharing consent is in force. Use lumos-list-tasks first to get a valid ref.",
"inputSchema": {
"type": "object",
"properties": {
"ref": {
"type": "string",
"description": "Task id from lumos-list-tasks, or the exact task title."
}
},
"required": [
"ref"
]
},
"page": "/panel"
}