Drafts saved to the Library Leo's run · 5 posts · handed back for confirmation
2026-03-03 linkedin launch v1.mdLibrary 2026-03-04 linkedin launch v1.mdLibrary spring-brief.pdfAttachment
Small-team shared projectsOne project for your small team.
One project for your small team.
Everyone brings their own AI agents.
Share an Orkas project with teammates, contractors or clients. Everyone works from the same project instructions, memory, Library files, to-dos and shared agents, and each person runs their part with their own agents, models and credits. Finished work comes back as files in the Library and to-dos waiting for a person to confirm.
- Start with
- An owner on a Lite, Pro or Max plan, free accounts for everyone else, and the rules your team already works by
- Finish with
- One playbook every member's AI follows, to-dos with a responsible person and a status, and deliverables the whole team can open
Brand Writer saves Leo's drafts to the shared Library and hands the to-do back for confirmation. Commander shows the team's to-dos with the responsible member and the status of each.
Follow along
Set up and run a shared project
Copy any of these, paste it into the Orkas input box, and start trying it.
Plan the work for the team
In this project, break the spring launch into to-dos: five LinkedIn posts for Leo, three hero images for Ana, and a final review for me that waits for both. Attach the brief from the Library to each to-do and write in each one what counts as done.
Write the team's project instructions
Draft project instructions for our shared project in under 4,000 characters: the goal, our voice rules, where facts may come from, how to name deliverables, that every finished deliverable is saved to the Library, and that a finished to-do moves to Awaiting confirmation, never to Done.
Draft listings with a remote assistant
Draft listings for the 12 new products in the attached CSV, following the project instructions: titles under 80 characters, three bullet points, materials and care last. Save the drafts to the Library, one file per product, and move the to-do to Awaiting confirmation.
Prepare a client's monthly report
Using last month's report and this month's data in the Library, draft this month's SEO report for the client. Cite the source of every number, make no ranking promises, and save it to the Library as YYYY-MM client SEO report.
Split a decision between two founders
Break the Germany launch decision into research questions, assign the pricing questions to Kai and the regulation questions to me, and make the Friday brief depend on all of them.
What you receive
One project the whole team works from
The project holds what everyone shares. Each person's chats, keys and credits stay with them.
Project instructions every AI follows
Goals, rules and what a finished deliverable looks like, up to 4,000 characters, read at the start of every task in the project.
Goals & rulesProject memoryTo-dos with an owner and a status
One responsible member per to-do. The agent hands finished work back for confirmation, and a person sets it to Done.
Pending → In progress → Awaiting confirmation → DoneDeliverables everyone can open
Agents save finished work to the Library when the instructions ask for it, and every member gets the new files.
2026-03-03 linkedin launch v1.md2026-11 client seo report.docxDetailed process
Four small-team setups you can copy
A content team that writes in one voice
The owner shares a custom Brand Writer agent and the brand guide. Leo drafts with it, Ana makes images with ImageStudio, and the owner confirms each to-do. Images and videos count toward the owner's storage.
A shop owner and a remote assistant
The assistant joins with a free account and runs listings, replies and the weekly summary on their own computer, with their own credits. The owner checks the drafts in the Library and publishes them.
An agency and its client
Give each client a separate project, because members see and can edit everything shared in it. The client attaches briefs and confirms deliverables; there is no read-only role and no comments.
Two founders and a weekly brief
Commander splits the decision into research to-dos that depend on each other. Each founder turns on Auto, which advances only their own to-dos, one at a time, while Orkas is open.
Start this work
Download Orkas — freeTry this use case in Orkas
Free, open source, and runs on your machine.
FAQ
Shared project questions
Limits worth knowing before you invite people. How shared projects work →
Who needs a paid plan?
Only the owner. Sharing needs a Lite, Pro or Max plan, and members join with a free account. Lite allows one shared project of up to 3 people, Pro 3 projects of up to 5, and Max 5 projects of up to 10, counting the owner.
Can a client see only part of a project?
No. Members see everything shared in the project: instructions, memory, Library files and every to-do. Give each client their own project and keep internal work in your private tasks.
Can I pay for my assistant's AI use?
Not through Orkas. Each member's agents use that member's credits or their own model key, and connector sign-ins are personal too.
Do teammates see my chats with my agents?
No. Task conversations, automations, keys and credits stay with each person. The team sees the results: Library files, to-do status and project memory.
What happens to the files if I stop paying?
The project becomes read-only for everyone for 7 days, then sharing ends and the files go back to your personal cloud storage. Members keep the copies already on their devices.
Ready when you are
Start the next task in Orkas
Free, open source, and runs on your machine.