Quick start
Ten minutes, and you'll have a project that knows what you're working on.
1. Sign in
Go to my.work.studio and sign in with your work account.
You'll land on Home. The left rail is the whole product: Chat, Automations, Tasks, Projects, Views, Library, Docs, Connections, Memory, Insights.
2. Connect one tool
Open Connections and connect the system you spend most of your day in — for most people that's a tracker (Jira, Linear, ServiceNow) or a code host (GitHub, GitLab).
You only need one to start. Connecting more later doesn't require redoing anything.
Why connect first
The assistant can only be specific about things it can see. Connected before you start a project, it can answer "what's still open on this?" from the tracker rather than from what you happened to tell it.
3. Create a project
Open Projects → New Project, give it a name and a one-line description.
A project is a working context, not a folder. Anything you discuss inside it is attributed to it, and everything that conversation touches — tickets, specs, documents, pull requests — is collected against it.
4. Ask it something real
Open the project's Chat tab and ask a question you actually have. Good first questions:
- "What Jira tickets are open for this project?"
- "Summarise what changed in this repo this week."
- "What did we decide about the alert routing?"
The assistant reads from your connected systems as it answers. If it needs something you haven't connected, it will say so and offer to connect it, without losing your place in the conversation.
5. Look at what it collected
Open the project's Content tab, or the Project 360 panel from the chat header.
Everything referenced in the conversation is there — tickets, docs, designs, pull requests — grouped by what it is. These are pointers: opening one takes you to the real thing in the system that owns it.
If something doesn't belong, dismiss it. Dismissal is permanent — the extractor may keep seeing it mentioned, but it won't come back.
What to do next
The pattern gets more useful the more of your work lives in it. One project per real initiative works better than one big one.
Connect Google Drive or SharePoint so the assistant can write specs and plans into the place your team already reads.
When you notice yourself asking the same question every Monday, that's a workflow.
Something not behaving as described? support@work.studio