hm_timeline

hm_timeline_write records a decision, milestone or piece of context in the timeline that other tool calls don’t capture on their own — “deployed v2.3 to production”, “the user decided to use JWT”.

Parameters

Parameter	Type	Description
`summary`	string	Required. The entry, written so it makes sense on its own later. Up to 16 KiB.
`meta`	object	Optional structured details: versions, ticket ids, participants. Up to 64 KiB. Set `meta.node_key` to tie the entry to a node so `hm_timeline` with `node_key` finds it.

Response

Field	Description
`summary`	The entry as written, with its `id` and time.
`replayed`	`true` when the same request had already been written (safe retry).

Example

{
  "summary": "Deployed Release 2.4 to production; all checks green.",
  "meta": { "release": "2.4", "environment": "production" }
}

Timeline entries always go to your own timeline, even when you are an organization admin with organization write mode on.

Equivalents

curl -X POST https://api.hypermemory.io/api/v1/memory/timeline/write \
  -H "Authorization: Bearer $HYPERMEMORY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"summary":"Deployed Release 2.4 to production; all checks green."}'