My Studio
My Studio is where your work is coordinated. It keeps the context of what you're working on — the conversations, the tickets, the documents, the decisions — in one place, so you stop reassembling it every morning.
It lives at my.work.studio.
What it's for
Most work is spread across systems that don't know about each other. The tickets are in Jira, the spec is in a doc, the decision was made in a chat thread, and the only thing joining them is you.
My Studio's job is to hold that join. You work in projects; each project accumulates the conversations you have about it and the things those conversations reference, so a week later "what was the state of this?" has an answer that isn't your memory.
It is not another place to keep your work. Your tickets stay in your tracker; your documents stay in your Drive or SharePoint. My Studio keeps pointers and context, not copies — so nothing here can drift out of sync with the system that owns it.
The pieces
The unit of work. A project has its own conversation, its own memory, and its own view of everything referenced in it.
An assistant that can see the project — its code, its knowledge bases, its connected tools — and act through them.
Your own accounts: Jira, GitHub, Google Drive, SharePoint, Slack, Outlook. Connected once, used everywhere.
How it relates to Flow
Flow is the workflow automation platform — you build a pipeline once and it runs on a schedule, a webhook, or an event.
My Studio is the other half: the conversational, day-to-day surface. Where Flow answers "run this process every time X happens", My Studio answers "help me with the thing I'm working on right now."
They share the same connections and the same account, so a tool you connect in one is available in the other.
Next
Start here Understand projects