MURAGE™
How it worksFeaturesSolutionsUse casesComparePricingLearn
DownloadDownload
MURAGE™

An AI Chief of Staff and a team that does the work. Open source, from Ferrox Labs.

Product

  • Features
  • How it works
  • Engines and apps
  • Privacy and security
  • Pricing
  • Murage Cloud
  • Download
  • Changelog
  • FAQ

Solutions

  • Solopreneurs
  • Founders and startups
  • Agencies
  • Ecommerce
  • Small business
  • Creators and educators
  • Developers
  • SaaS
  • Nonprofits
  • Consultants and freelancers
  • Customer success teams
  • Legal and professional services
  • Small teams
  • Sales teams
  • Operations managers
  • OpenClaw and Hermes
  • Industries
  • Use cases
  • Build your team

Compare

  • vs Claude Code
  • vs Codex (ChatGPT Work)
  • vs Claude (Cowork)
  • vs Paperclip
  • vs OpenClaw
  • vs Hermes Agent
  • vs Manus
  • vs Genspark
  • vs n8n
  • vs Zapier
  • vs Grok Bot
  • vs Meta Muse
  • vs Claude Duet
  • vs OpenAI Dots
  • vs Cue by Manus
  • vs Instinct
  • vs Viktor
  • vs Lindy
  • vs Tasklet

Resources

  • Learn
  • Docs
  • Team library
  • Team gallery
  • Skill library
  • AI Chief of Staff
  • How we test
  • Limits
  • Switching to Murage
  • Open source
  • Blog
  • Community on Discord
  • Release notes

Company

  • About
  • Why trust Murage
  • Press
  • Partners
  • Enterprise
  • Contact
  • Privacy
  • Terms
  • Cookies

© 2026 Ferrox Labs, LLC. Murage is open source under AGPL-3.0. Murage™ is a trademark of Ferrox Labs, LLC.

Getting started · Episode 11 of 17

Projects: one room for every big job

4:50

Chapters

Every big job scatters: a timeline in one folder, a shot list in another, the rest in your head. Give the job its own project, with the bots on it, its folder, what it learns and its to-do list, all in one place.

What you'll learn

  • Create a project and choose the bots on it
  • Point the project at the job's folder
  • Ask the project, and see which file each answer came from
  • Tell it what to remember about this client, kept in the project's memory
  • Track what's left on the Board
Read the transcript

Which email had the Shah timeline? Maya doesn't dig any more. She asks the job. On site, ceremony, golden hour, from the folder she gave it. Every big job gets a room like this. Every big job scatters. The timeline's in one folder, the shot list's in another, and the one thing the client said never to forget is in Maya's head. Today she gives the Shah wedding its own project: its people, its folder, what it learns, and its to-do list, all in one place. Let's set one up. Step one: give the job its own project. Click the plus. New Project. Maya writes what it's for, and that becomes its name. Shah wedding, twelfth of June. Then who's on it. Ember, and Draft Partner, who writes her replies. Create. And here's the job's own room. Chat, Board, Overview, Files, Memory, Activity. Everything about this wedding lives behind these six tabs. Ember leads it by default. One more thing: right-click it, Move to team. And it's filed under her team, Solo Business, with the rest of the studio's work. Step two: the paperwork. Files. Right now the project has no folder of its own. So Maya gives it one. Details, Folder, Choose a folder. She points the project at the wedding's folder: the timeline, the shot list, and the contacts are already in there. Set. Every bot in here now works from that folder. It lives with the job. Not in her downloads, not in a chat from three weeks ago. Step three: ask the job. Back in Chat, and the folder's right there at the top. When does she need to be on site, when's the ceremony, when are the golden-hour portraits? Only from this project's files, and say which file. Send. And there it is: on site, ceremony, golden hour, each with its time, straight from the timeline in the folder she just gave it. No card, no permission dance: the folder is the project's. And it says which file it read, every line. Don't take its word for it? Open the file. Step four: what it learns about this job. Maya tells the project two things. Family photos, twenty minutes, tops. And her mum's paying the balance, so copy her on money. Noted, in plain words: both points, added to the project's memory. And there they are under Memory. This project's memory, for this client, and only the bots in here can see it. When Draft Partner writes the balance email in May, that's already known, without Maya saying it twice. The Board is for the jobs between now and the day. To do, in progress, waiting, review, done. New card. Final timeline to Priya, by the first of June. One card, on the board, where the job is. Not on a sticky note. In the sidebar, the project sits under her team, Solo Business, next to the bots that work it. Next wedding, next project. Same six tabs. You set these up on your computer. And Details is the one-page view. Filed under Solo Business. Members: Ember and Draft Partner. Who's on it, what it works from, what it remembers. One place. That's projects. Give each big job its own room: the people on it, its folder, what it's learned, and its to-do list, under the team it belongs to. Next job, next project, same six tabs. Tonight, pick the one job that's scattered across your inbox, and give it a project. Whatever you run, every big job gets its own project: its people, its folder, and what it's learned, in one place. Set one up tonight, on the AI plan you already pay for. Download it free at murage.ai.

Previous, episode 10Pick the right brain: modelsNext, episode 12Teams that talk to each other
Download it at murage.ai