Edit sleep times with your AI

Your AI can now correct the start time, end time or type of a sleep in tataya, including a sleep that has already ended. It updates the original entry and recalculates the duration.

If you logged the wrong wake time, your agent can fix it directly. It no longer has to delete the sleep and add it again.

One correction, the same shared entry

• The original entry stays. Its ID and the caregiver who first logged it are preserved.
• The duration updates. A corrected start or end time recalculates the length of the sleep.
• Your family sees the correction. Other caregivers see the updated entry when their journal refreshes.
• Conflicting edits are caught. If another caregiver changed the sleep in the meantime, the agent must read it again before trying to save.

Caregivers in the same family with permission to log can make corrections. An AI connection set to Read only can view entries but cannot change them.

How to try it

1. Connect your AI to tataya and choose Read and log if you want it to make changes.
2. Tell your AI which sleep to correct and give the right start time, end time or type: Nap or Night.
3. Open the journal to check the corrected entry. A running sleep can also keep running while its start time or type is corrected.

Already connected? Your existing connection or agent key still works. Some AI clients need their tool list or tataya instructions refreshed once. Agents using the command-line tool need the latest CLI.

A journal for everyone sharing the care

tataya is a shared baby journal for sleep, milk, solids and diapers. Each caregiver has their own sign-in and uses the same family record. Family sharing, creating a journal and nap and bedtime suggestions are free, with no subscription.

Sleep suggestions use your baby’s age and recent logged sleep. They are a planning aid, not medical advice.

For agents and developers

Use the new MCP tool edit_sleep, the CLI command sleep edit --id UUID --stdin, or PATCH /api/v1/events/sleep/{id}. Send the changed fields and an expected snapshot of the sleep you just read: at, end_at, sleep_type and revision.

A stale snapshot returns 409 concurrent_update. Corrected times need an explicit UTC offset, cannot be in the future, and the end must be after the start. The original author stays attached; the latest editor and edit time are recorded. Read the correction examples or use the OpenAPI reference.