This week in Okou: give clearer visual feedback with image annotations, keep new artifacts private until you choose to share, and find a starting point with task chips and template shortcuts. We also have subscription controls, email updates, and a conversation about AI memory from Heritage Table during SF Tech Week.
Image annotations
Make visual feedback easier to follow. Once an image has finished uploading, open its preview and choose Annotate to point out exactly what needs attention.
Draw a box or arrow, add a freehand mark, or place text on the image. Choose Attach marks to bring the annotations back into your draft, then send the image with your instructions. You can keep editing the marks until you send.
Private artifacts
New uploads and generated artifacts are private to their owner by default. Keep a first draft to yourself, then use Share to choose who can access it: Only me, your organization, or anyone with the link.
Only the owner can change an artifact’s visibility. Existing public artifacts keep their current access settings; this update does not retroactively make older files private.
Task chips and template shortcuts
Start with the kind of work you want to do. The chat home now has Workflow, Presentation, Image, Website, and Visualization chips that open relevant suggestions and options.
Choose Image to explore visual styles, Website to browse site templates, or Presentation for deck recommendations. Select a template to attach it to your prompt, then describe what you want Okou to make. The selected task stays visible as a chip in the composer.
The + menu also brings attachments and templates together, so you can add a file or choose a starting point while writing your request.
Smaller updates
Subscription controls. Ask your agent to check usage on connected personal subscriptions or switch the default account for future unpinned runs. Active runs keep their original account. Eligible Codex accounts can use a Reset Card that you review and confirm yourself; generating the card does not reset usage. Claude subscriptions recover on their provider’s natural schedule.
Email notifications. Ask your agent to email an update to the address on your own account. This notification channel is limited to the account owner, and existing permissions and email preferences still apply. Enable Email updates under Settings → Preference → Email subscriptions.
Around the table at SF Tech Week
What’s your earliest memory of coconut?
That was the opening question at Heritage Table’s The Memory Table: What Should AI Remember? on October 9. Molly and Scarlett joined hosts Evangeline Medina and Pubali Sen at artist Peggy Gyulai’s loft in San Francisco. Okou helped support the evening.
Heritage Table helps families preserve recipes and the stories behind them. A food memory can carry a person, a place, and details that never made it into a written recipe. Around the dinner table, those stories led to a question we keep returning to at Okou: what should an agent remember, and who gets to decide?
The Memory Table, October 9. Photo shared by Evangeline.
People are already talking about “hiring” and “firing” agents. They give one a job, explain how they want it done, and see whether it delivers. The expectation sounds familiar: understand your responsibilities, take feedback, and make the next piece of work easier. A role like “marketing agent” still needs specifics—what does it own, and where does a person stay involved?
One idea stayed with us: the agent as a snapshot, the human as an amplifier. An agent carries a version of our context and working methods. People bring new experiences, relationships, and judgment. That helps explain another observation from these conversations: some founders who started out hoping to avoid hiring are now building teams.
Teaching an agent also raises personal questions. If I share a preference, who can see it? Can I share a useful process without sharing the private information behind it? At Okou, personal memory, team instructions, and context from connected tools are distinct. Making those boundaries understandable matters.
The dinner offered a thoughtful example. Conversations were not recorded by default, and guests could choose what to contribute to a shared Living Cookbook afterward. We liked that the choice stayed with the person sharing. It is a useful standard to bring back to our own work: understand what was learned, and choose what to carry forward.
Read the full event recap: What should AI remember? A dinner at SF Tech Week.
Try annotating your next screenshot, choose a template for your next project, or check the sharing settings on a new artifact.
