← All guides

How okWOW Works

Places, spaces and roles, private and shared mode, tasks and what agents can see

On this page

This page explains how okWOW organizes knowledge and who can see what. It is written for people and for the agents that connect to okWOW through the okWOW MCP.

Places

Everything in okWOW lives in one place:

  • Organization: your company. Its memories reach every member. It holds memories, memory groups and skills.

  • Space: a team area inside the organization. It holds memories, memory groups, tasks and items in the Vault.

  • Only you (me for agents): items for you alone, available in every space. It holds memories and skills.

Spaces and roles

A space's audience decides who may be in it:

  • Private: only the owner.

  • Chosen people: the members the owner or an admin adds.

  • Whole organization: anyone in the organization may join. Joining makes you an editor. Until you join, you see none of its content.

Only members can read a space. Each member is a viewer, editor, admin or owner; only the owner can change who the space is for.

When you leave a space, or are removed from it, what you saved there stays with the space. You lose access to it.

Private and shared mode for agents

Each agent connection is in one mode at a time. A new connection starts in private mode. The mode stays until it is switched, across sessions, and other connections keep their own.

PrivateShared
What the agent readsYour own items and the team'sOnly the team's (your own skills still load)
A save in a spaceYours alone, filed in that spaceReaches the space's members
A save in the organizationNot allowedReaches every member
A save for only youAllowedNot allowed
Creating a taskNot allowedAllowed

Switching changes where new saves land. Items saved earlier keep their audience. To share something saved privately, save it again in shared mode.

What you save

  • Memory: one fact, up to 1,000 characters. A memory saved without a group goes to the place's Inbox.

  • Items in the Vault: artifacts (documents and code), files, skills, meeting transcripts and plans.

  • Skill: one SKILL.md. Only that text is shared; files next to it on your computer are not. Saving a skill in a space needs the editor role.

  • Task: a to-do in a space, with an owner and an optional due date.

Deleting an item removes it for every member of its place, and you cannot restore it yourself.

Tasks

The person who asks for a task is its watcher. An agent working on a task claims it, so no other agent takes it. A claim lapses after an hour without an update from that agent.

When an agent needs something only a person can give, such as a decision, access or a fact, it blocks the task with a note. Agents stop working on a blocked task until a person unblocks it. A blocked task appears in its watcher's Needs you.

Knowledge graph

okWOW links people and named subjects, such as projects, companies and customers, to spaces, channels, memories, tasks and items in the Vault. Agents read it to find who owns or knows a subject and how two things connect. You see only what your access allows.

Session capture

With session capture on, each coding session is saved as one of your okWOW chats when it ends or after 30 idle minutes. Your rules decide which space it is filed in, or whether it is saved at all.

  • A captured chat is yours. Other members of the space cannot open it.

  • okWOW titles and summarizes it and learns memories from it. Those memories start as yours.

  • Common secrets are removed before upload. Do not paste secrets into a session anyway.

Plugins

Plugins you add in okWOW, such as email, chat, calendar or meetings, can also be used by an agent you give access to them (see Choose which plugins an agent can use). A plugin's tools act as you. An agent should confirm with you before sending, posting, scheduling, changing or deleting anything. Some actions wait for your approval in okWOW and do nothing until you approve.

Access levels

When you connect an agent you choose Read, Read and write or Manage account. Read allows no saves. Inviting people needs Manage account and the organization owner or admin role.