Orneos documentation

A shared workspace for people and AI agents — what it does today, who it is for, and what it is deliberately not yet.

Approve an agreement for one change, then give a reviewer or agent its context.

Keep your existing tracker

The nine ideas the rest of the documentation assumes — company, team, issue, project, Vault, Intent, context bundle, the local replica, and sync scope.

What you can use today

How the two boundaries work, what switching between them does, and why a team is a harder wall than it looks.

Inviting people, the two team roles, company administration, and exactly what happens when someone is removed.

The five settings tabs and what lives in each — profile, appearance, teams, members and company.

The eight themes, light and dark mode, where your choice is stored, and why the app looks like the website.

The unit of work — every field, how editing behaves, what happens to concurrent edits, and how undo works.

Three views over the same issues — what each is good at, how board columns define status, and the shortcuts that make them fast.

Narrowing a list, saving personal filters and display settings, and sharing a filtered URL.

Team-scoped tags for classifying work, what they are good for, and the one failure mode worth avoiding.

Grouping issues into a body of work with its own status and dates — including sub-projects and links between projects.

Breaking work down, and the four typed links between issues — blocks, blocked by, relates to, duplicate of.

Discussion on an issue, linking Vault pages from a comment, and why comments are part of what a reviewer receives. Mentions are planned, not built.

Spotlight and the Search page, each with an explicit Team or Organization scope, saved Search views, and online Vault full-text results.

A personal page across your teams with a chat-style search over one team you choose that answers with sources, saved conversation history you can reopen, rename and delete, the assigned work needing you with the reason for each item, and an inbox for your in-app notifications. Work in progress.

Team documentation that lives next to the work it describes — and becomes part of what a reviewer receives.

Organising Vault, and the three space roles that control who can read and write.

The Vault editor, how simultaneous editing merges, and version history.

The approved, versioned agreement about what a piece of work should accomplish — and the rules that stop it quietly changing.

One click puts the task, its agreement, the discussion and linked Vault references on your clipboard — with sources named and truncation marked.

Bring useful context to a change

Evidence connected to the work

Review against the agreement

The vocabulary Orneos uses about proof — what a source reference means, what it does not, and why unknowns are stated rather than omitted.

Use the existing context tools and bridge the remaining intake and evidence steps with a founder during early access.

The current AI paths, active context and review work, and the provider and funding boundary for each surface.

Bringing your own Anthropic key for AI-assisted drafting — where it is stored, what "remember on this browser" means, and how to remove it.

Asking questions about your board in plain language, and the overview cards — plus what an answer is and is not.

AI access and usage

Controlled action with human oversight

Responsive work and synchronization

What works without a connection, what does not, how to tell whether your changes have reached the server, and what a pending change depends on.

What Orneos keeps in your browser, how much space it uses, when it is destroyed, and why it is not a backup.

Security and access boundaries

What Orneos stores, where it goes, what happens with AI features, and what we will not claim about backups.

The gaps most likely to affect you, written down deliberately rather than discovered.

Programmatic access

Scoped programmatic access

Context for supported agents

Shared coordination around a task

Know where your attention is needed

Relevant context for the work

Start work with a clear agreement

Carry useful decisions forward

Scope and future options

Navigation and common context-specific shortcuts, including list filters, timeline controls and Vault page actions.

The problems people actually hit, what causes them, and what to do — including how to reset your local data safely.

Every term Orneos uses in a specific sense, defined in one line.

Where Orneos is heading

How to reach us, what makes a report useful, and what we actually want to hear about.

Where Orneos is going: what comes next, and what is further out.

The review problem these docs are ultimately about, written as a guide.

Set up one team and its agents with us, and tell us what was worth it.