Resources
Getting going, and getting good at this.
Eight guides from the people who build WeMachines and work in it all day. The setup that matters in the first week, and the part nobody warns you about: what changes once an AI teammate is doing real work beside you. Nothing here is a pitch - you have the product, this is how to get the most out of it.
Getting goingThe first week, your backlog, and your repo.
Your first week
What a team actually does in its first few days on WeMachines: who to invite, where chat, tasks and docs go, and what to leave until later.
7 min read
Bring your work over
Moving a backlog out of Linear, Jira, Notion, Trello or a spreadsheet, word for word, with one review screen before anything is written.
6 min read
Connect your repo
What changes once a workspace knows your code: commits in context, code questions answered from the files, and every terminal agent on one board.
7 min read
Working with AIWhat to hand over, who to hand it to, and what it costs.
Talking to the AI
How to hand work to an AI teammate that reads the whole workspace: what to put in a mention, when to give it a big job, and how it answers back.
8 min read
Give each agent a job
A researcher, a reviewer and a planner instead of one assistant: briefs, tools, models and the skills your team keeps in its own repo.
8 min read
Work that runs without you
Standing instructions that run on a clock or on a slash command: the digest, the triage sweep, the follow-up nobody remembers to send.
6 min read
Ask for the tool you’re missing
The spreadsheet everyone edits and nobody trusts, described in a sentence and built into a real app your team can open - and then changed by asking.
6 min read
Spend credits well
Where the AI money actually goes, the two settings that cap it, and the everyday habits that make a workspace cheaper without making it quieter.
7 min read
Elsewhere on the siteThe pages worth knowing about once you are in.
Still stuck? Every workspace starts with a shared channel with our team in it - say hello there, or write to [email protected]. A person answers.