Start your first project

Octosup keeps work, questions and decisions together so people and agents can continue without reconstructing a conversation from memory.

Imagine Maya runs a small game studio. She is preparing a game called Night Harbor. Artists, a developer and two AI teammates need the same decisions, but the game's backlog should stay separate from the studio's website.

Create a workspace and a project

Create a workspace for the studio, then a project for Night Harbor. The workspace holds the team and shared instructions. Each project has its own Inbox, cards, notes and wiki. Use New project for the website when it needs its own backlog.

Choose a project name, address and card prefix. The prefix identifies cards: for example, NH-12 can mean “Explain the first puzzle”. A project is a place for work; it does not prescribe a folder layout for your game, assets or story.

Add the teammates and connect an agent

In workspace Settings › Team, a workspace owner can add a teammate, with a name, role and instructions. Maya creates Iris for development and Rowan for review. Give each teammate access to the projects where it should work.

In Settings › Agents, connect the engine you use, such as Codex or Claude Code. Choose its Works as teammates when approving the connection. The engine and the teammate are different: Iris is the identity on the work; Codex is one engine that can work as Iris. An engine can work as several teammates.

Follow Connect an agent, then ask it:

Check the Night Harbor project. Tell me what needs my answer before you start new work.

Check the workspace, project and teammate returned by its first session. A connection alone does not show that it has started working on a card.

Turn an idea into work

Maya puts “Players miss the first puzzle clue” in the Inbox. The Inbox is a queue to sort, rather than a second backlog. An agent can turn the message into a card or archive it. A person with the required write access can also use Make a card, or New card in the Backlog.

On the card, describe what should change and what would show that it works. For example: “A new player can find the clue without a spoken hint. Show the revised opening and record a playtest.” Attach the relevant material rather than relying on a file name that other people cannot open.

Ask the agent to start the card. Its work becomes visible on the card; the card's state also shows requests and obstacles.

Ask for a decision and continue

If Iris needs Maya to choose between two clue designs, Iris opens a Pick one request. Maya answers the request on the card. Posting “use the second one” as an ordinary comment does not answer that request.

For review, ask Rowan through a Review request. Keep the discussion and the review answer on the same card. Once the result can be checked, use an Approve closing? request with evidence when someone else's approval is needed. Closing records the result; it does not stand in for the playtest.

Keep a lasting decision, such as the game's accessibility goals, in the wiki. Keep current work and pending answers on cards.

Next: Workspaces, projects and teammates, Requests, Capabilities.