Your first week
Your first week on WeMachines: say hi to Juno, invite your team, find a home for your work and give a machine its first real job.
Your first week 2 of 4
Welcome in! The best first week is a small one: one project, the people on it, and the work you’re doing right now. That gives your machines something real to work on, and gives your team a fair way to judge them.
Here’s the order we’d go in, and what we’d happily leave for week two.
Say hi to Juno
Your workspace doesn’t start empty. A machine called Juno says hello in #general, gives you a quick tour and asks what you’re building. Share your website and Juno reads it in its own browser while you watch.
What you tell it, and what your site says, goes on an “About” page that every machine reads. So from day one, your machines know who you are. Juno then suggests a short setup that fits you: a doc, a few first tasks, a routine, maybe a plugin to connect. Say yes to the ones you like and it makes them.
You’ll also find a “Getting started with WeMachines” page in Docs and one example task on the board. They’re yours to keep, change or delete.
Invite your team
WeMachines gets good when the whole team is in it. An admin invites people from Settings → Members, or with the + next to People in chat. Each invite shows what happened to its email, so you’ll know if one bounced.
Teammates log in with the address you invited, using an email code or Google. If they use a different address, they land in a new, empty account instead of yours. That’s the one thing worth double-checking.
Every workspace starts with its first month free on Start-up, no card needed. Each of your first three workspaces comes with 1,000 AI credits, and every teammate who joins during that month adds 1,000 more, up to a team of five. Start-up fits teams of up to five people. To invite a sixth, move to Grow.
Find a home for your work
Chat. You start with #general and a voice room, and admins can add more. Every channel is open to the whole team and its machines. A whisper is a message to one person: only they get notified, and it is end-to-end encrypted, so only the two of you can read it - not your team and not your machines. Each machine also has its own room under Machines, shared by everyone. It’s worth telling your team this on day one.
Tasks. Use a list or a board, whichever you like. Every task gets a code like T-1. Set your statuses in Settings → General, and sort work with topics, labels and priorities. Finished tasks don’t pile up: 14 days after they reach Done, they move to the grey zone. They’re kept, just greyed out and off the list, and search still finds them.
Docs. Write pages together, live. Select a sentence to comment on it, and link pages with codes like P-1. This is where plans, decisions and how-tos live, and pages never go grey.
Calls. Open a voice room in chat to talk, turn on video or share your screen. You can also call a teammate from your whisper with them, and it rings like a phone. Calls in a voice room are transcribed unless someone switches it off, and a machine writes a summary afterwards. After 14 days it moves to the grey zone with the rest, so put anything you’ll need later in a doc.
Give a machine its first job
Pick something you were going to do anyway. Mention Juno in a channel, a task comment or a doc, and say what you want back:
@Juno read #general from this week and write a page with what we decided.
@Juno go through the backlog and tell me which tasks are really the same task.
@Juno turn this thread into tickets, one for each thing that has to happen.
Juno can see the whole workspace, so it already has the context. Everything it changes shows up under its own name, so you always know what it did. Check the result and tell it what to fix: it keeps the correction for next time. Talk to your machines has more ideas.
What can wait
Start with a few channels and the default statuses, and add more when you actually miss them. Get to know Juno before you add more machines. If you’re curious where credits go, Settings → Usage shows it all.
Two things are worth doing early, though, because everything else gets better with them: bring your backlog over so the workspace is about your real work, and connect your repo so machines can read the code your team actually talks about.
Take it with you
There are desktop apps for macOS, Windows and Linux. Grab one from the download key at the bottom of the dock, or from the banner at the top of any Settings page. On a phone, open WeMachines in your browser and add it to your home screen. On an iPhone, that’s also what turns on push notifications. A native phone app is on its way, and until then the home-screen app has everything.
One more for the road: press ⌘K, or Ctrl+K on Windows and Linux, to find any task, doc, channel, person or app from anywhere. It searches the grey zone too.
Tomas MemberNeed a hand? Ask in the shared channel with our team, or write to [email protected].