One photo, one remark, one saved result.
This travel journal example follows one photo and a supplied remark all the way to saved timeline content. Codex directed real MCP calls to a local Vifo service. The photo and remark are demonstration inputs; they do not document a real restaurant or journey.
1 · The input
six seats, and the owner sings while he cooks.
An invented demonstration remark, submitted as written. It tests verbatim storage; it is not a factual claim about a restaurant.
2 · The instructions
“Create a trip called Photo-to-journal demonstration, dated 13 October 2026, timezone UTC. This is a software demonstration, not a real journey.”
“Give me an upload link.” Open it in the browser, upload the photo and save the remark above.
“View the saved photo, describe only what is visible, and save timeline content alongside my original words. Keep the remark exactly as supplied.” The test used 12:00 UTC as an assigned demonstration ordering time, not as the photo’s capture time.
These are reproduction instructions, not a transcript of a Claude or ChatGPT conversation. Ordinary chat attachments do not automatically become Vifo uploads.
3 · What was actually saved
13 October 2026 · Demonstration day
Lunch · demonstration
A bowl of noodles with egg and shrimp. This illustrated entry is a software demonstration, not a record of a real restaurant visit.
six seats, and the owner sings while he cooks.
The remark was retrieved from storage and matched exactly. It is separate from the assistant’s photo description.
The first saved description was “A bowl of noodles with egg.” A later save added “and shrimp”, matching the visible photo. The original remark stayed unchanged. Review descriptions and quotations before you share your own journal.
This page is a saved snapshot of that test output, not a live private account page. The service stored one photo, one remark and three timeline blocks: a day divider, a photo entry and the original remark. Saving those blocks is a meaningful outcome, not proof that every organising step is complete.
What this test establishes
Observed on 13 October 2026: Codex-directed MCP HTTP calls against a disposable local Vifo account; browser photo and note submission; retrieving the uploaded image; saving and refining a description; storing and reading back timeline content. Claude web, ChatGPT setup, their OAuth login flows and full journal completion were not tested here.
Read the sanitized saved-output receipt. Private identifiers and upload/share addresses are omitted; image references use the public demonstration file.
Use the assistant you already have, with a place to save the journey. Assistant plan requirements and Vifo’s own plan are separate.
Connect your agent