override_timestamp
For importing work that was created or finished somewhere else: set when a project or task was really created (name "created_at"), or when a task that is done was really completed (name "completed_at"). The service normally records these itself, as the moment of the call; use this only to carry over dates from the tool the work comes from, never to adjust the dates of work done here. The value is a date and time with its zone, such as 2026-03-14T09:30:00Z. It is refused when it is not a real date or is before 1970, when it is in the future, when a completion would come before the creation or before an earlier completion of the same task, when the creation would come after the moment the item was recorded here or after a later status change, and when the task is not done. When both dates are to be set, set created_at first. Setting completed_at earlier also moves the status changes between creation and completion that would otherwise come after it. The change is recorded in the item's history with the old and the new value and who made it.
- It
- Changes the plan, as one step that is stored whole or not at all.
- Who may call it
- Every user.
- Version
- Takes the
versionthe caller last read, and is refused withversion_conflictwhen the item has changed since. A change moves the version one on. A call that asks for what is already so changes nothing, and leaves the version as it is. - Answers with
- The task in short. Its fields. Not in it:
description,why,links,timeline,created_at,created_by,updated_atandunchanged_since.gethas those. - MCP tool
override_timestamp- HTTP
POST /api/override-timestamp- Command
vigile override-timestamp
Input
| Field | Takes | What it is | |
|---|---|---|---|
kind | "project" | "task" | optional | "project" or "task". Needed only when the ID alone is ambiguous. |
id | string | required | The ID of the task or project. |
version | integer 1 or more | required | The version of the item you last read. The call fails with a conflict if the item changed since. |
name | "created_at" | "completed_at" | required | Which timestamp to set: "created_at", or "completed_at" for a task that is done. |
value | string | required | The date and time it really happened, with its zone, for example 2026-03-14T09:30:00Z. |
A field that is not listed here is refused, as invalid_input. On the command line each field is an option, with hyphens for underscores: --kind.
Example
The same call three ways, as agent1. It was made on the demo plan the pictures of this site show. Over HTTP and MCP, a call without a key acts as agent1 on a new instance.
Command line
vigile override-timestamp \
--id WEB-002 \
--version 3 \
--name created_at \
--value 2026-02-20T09:00:00Z \
--as agent1HTTP
curl -s http://127.0.0.1:8700/api/override-timestamp \
-H 'content-type: application/json' \
-d '{"id":"WEB-002","version":3,"name":"created_at","value":"2026-02-20T09:00:00Z"}'MCP tool call
{
"name": "override_timestamp",
"arguments": { "id": "WEB-002", "version": 3, "name": "created_at", "value": "2026-02-20T09:00:00Z" }
}The answer
{
"kind": "task",
"id": "WEB-002",
"title": "Cart page lists the items and the total",
"type": "task",
"status": "done",
"priority": 0,
"value": null,
"size": null,
"version": 4,
"contained_in": ["WEB", "WEB-001"],
"depends_on": [],
"assigned_to": ["agent1"],
"is_assigned": true,
"is_next": false,
"is_waiting": false,
"waiting_for": [],
"has_problems": false,
"completed_at": "2026-03-02T10:55:00.000Z"
}
This is what a service answered when this page was built. Over HTTP it is the body of the response, over MCP the text of the tool result, and the command line prints it in words unless given --json.
A call that is refused
vigile override-timestamp \
--id WEB-002 \
--version 3 \
--name completed_at \
--value 2026-02-20T09:00:00Z \
--as agent1
{
"error": {
"code": "rule_violation",
"message": "Task WEB-002 cannot have been completed on 2026-02-20T09:00:00.000Z: it was created on 2026-03-02T08:49:00.000Z, after that.",
"rule": "completed_before_created",
"actions": [
"Give a completion date at or after 2026-03-02T08:49:00.000Z.",
"Or set when it was really created first: override_timestamp with name \"created_at\"."
]
}
}
What it answers
The item in short. For a task that is done, completed_at is in it. created_at and the timeline show in get.
When to use it
Only for work that was created or finished somewhere else and is being brought in. The service records creation and completion itself, as the moment of the call, and everyone relies on that record. For imported work, create and link the tasks, give each the status it has, and then set the dates: created_at first, then completed_at for a task that is done.
Rules
- The value is a date and a time with its zone:
2026-03-14T09:30:00Zor2026-03-14T10:30:00+01:00. - It cannot be in the future, nor before 1970.
- A creation cannot be put after the moment the item was recorded here, nor after a later change of its status.
- A completion can only be set on a task that is done. It cannot come before the creation, as in the refused call above, nor before an earlier completion of the same task.
- Setting the completion earlier also moves back the status changes between creation and completion that would otherwise come after it.
- A date that names the moment the item already has, in whatever zone it is written, changes nothing: no new version, and no line in the history.
- The history records who set which date, when, and what it was before.
Errors
invalid_input: the value is not a real date and time with a zone, or is before 1970.version_conflict: the item changed since it was read.rule_violation:timestamp_in_future,created_after_recorded,created_after_change,not_completed,completed_before_created,completed_before_earlier_completion, ordeleted.