Beta
Hedy Strawberry

Hand the Hedy session contexts to a companion

Hand a companion the outcome. It reads the Hedy session contexts, does the 19-operation version of the job, and stops for your click on anything that changes a record.

Open the session context. Check it against something else. Write the change. Move to the next one. That is the Hedy afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a session context until you approve it.

What it can do is exactly what Hedy exposes to an account you authorise and nothing beyond it: 19 operations, 13 reads and 6 writes. In practice that means it can update a topic, update a session context and delete a topic, and work across the session contexts, topics and highlights.

The Hedy API stops at Hedy. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.

Where do the session contexts come from?

13 of the 19 operations are reads.

Your account, not a guess at it: a companion can get a topic, get topic sessions and get a todos by session, and the full list below is the whole list, with nothing inferred from Hedy's documentation.

The session contexts are what most of this inventory is about, alongside the topics. A companion can hold all 19 of these operations and forty open tabs in the same pass, which is how an afternoon of Hedy admin becomes a queue you review.

  • Get Topic
  • Get Topic Sessions
  • Get Todos By Session
  • Get Todo
  • Get Session
  • Get Session Context
  • Get Many Topics
  • Get Many Todos
  • Get Many Sessions
  • Get Many Session Contexts
  • Get Many Highlights
  • Get Highlights By Session
  • Get Highlight

What happens before it can update topic?

All 6 write operations wait for you.

A companion can update a topic, update a session context and delete a topic, and each one is staged on an approval card first: you see the session context, the field and the new value before it lands in Hedy.

Nothing in Hedy is sent, changed or deleted on your behalf without that click, and a rejected card leaves the session context exactly as it was. The gate is the same one on every surface, described at security.

  • Update Topic
  • Update Session Context
  • Delete Topic
  • Delete Session Context
  • Create Topic
  • Create Session Context

What does the recurring session contexts pass look like?

Yes.

Saved as a routine, the Hedy session contexts pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.

The operations playbook catalogues the other recurring shapes of the busywork, the Hedy session contexts sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Hedy account and a companion works 19 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide