Notes hold the idea. Then mind maps lay it out.

Notes catch the idea while it is still rough. Mind maps branch the questions, and AI works with the notes that are selected. The decisions become the first brief for the app.

Get started
Concept mockup of a monitor, a Raspberry Pi and a mini PC on a desk
Concept mockup: the note, live on a dedicated agent computer.

A note comes first.

A note holds the idea while it is still fresh. A few lines and a checklist are enough.

  • Type / for headings, to-dos, tables, code and equations.
  • Type @ to link another note. Click the link to open it.
  • Download any note as a Markdown file.
  • Share one note by email, to read or to edit, with an optional expiry.

A mind map sends the agent one branch.

A linear chat keeps one thread, so a side question stays in the context of every answer after it. In a mind map, a question starts from a note, and the agent receives that note and its parents. Other branches stay out of the prompt. In the example below, a question branches off to agent computers, then planning continues from the root. Select any note to see the context its next question uses.

Concept mockup of a monitor and a mini PC on a dark desk, with a keyboard, a notebook, a pen and loose paper

Oyren mind map

Branch from any node. Select one to see the context behind its next question.

Oyren

Build a workspace where people can plan work and run AI agents on Codespaces.

Planning workspace

Keep notes, mind maps and tasks together so an agent has a clear brief.

Agent computers

Give each agent a Codespace with a terminal, editor and browser.

Fleet inbox

Bring agent questions, requests and work ready for review into one inbox.

Start an agent

Give the agent one task from the plan and review what it builds.

Write the brief

Name the goal, attach the notes and say what a finished task looks like.

Concept mockup: the mind map on a dedicated agent computer.

One idea. Three places to ask the next question.

Linear chat

Every follow-up goes at the end.

  1. You

    What should the first version include?

  2. AI
    Planning, agent computers and a fleet inbox.
  3. You

    How should users start an agent?

  4. AI
    Give it a task from the plan.
  5. You

    Back to planning. What belongs in the brief?

Asked from Planning workspace

What should go in the task brief?

AI answer

Name the goal, attach the notes and say what a finished task looks like.

Interactive example. Answers are written for this walkthrough; no AI request is sent.

  • Drag nodes, draw arrows, and label each arrow with the question that led there.
  • Ask from any node. The answer lands as a new node beside it.
  • Follow one thread. A question uses the current note and its parent notes as context.
  • Suggest offers follow-up questions. Click one to answer it.
  • Tag a note to a node. Verify checks a claim against it and quotes the passage.

Chat talks the details through with the notes open.

The AI reads the note before it answers. A question about pickup starts from the times written in the note.

  • Ask AI inside a note. It answers from that note's text.
  • In chat, type @ to bring in any note. The answer comes from what the note says.
  • Paste an image or tick web search when the notes are not enough.
Concept mockup of a laptop and a mini PC on a dark desk, with an open notebook, a pen and a stack of paper
Concept mockup: chat with the note as context, on a laptop beside the notebook.

Idea, plan, product.

The note is the first file in a workspace. The board and the code go in the same one, so nothing gets copied between apps.

Idea

Notes and mind maps

Notes capture it, mind maps lay it out, chat talks it through. This is the current step.

Plan

A project board

The checklist in a note becomes tasks on a board that move across columns.

Product

A codespace

The build happens in the same workspace, next to the notes that explain why.

See Codespaces

Every product starts as a note.

Notes and mind maps are free within the plan's storage limit. AI answers use credits.

Get started