appendix

Glossary

The current words used across the Manifoldone product.

Agent — Claude Code, Codex, or Grok running through its provider CLI on a user-controlled machine.

Agent Settings — The product surface that reports provider availability and authentication state and offers the relevant recovery action.

Artifact — A file, Markdown document, or static preview opened from agent work inside the workspace.

Desktop owner — The desktop app and machine that own local execution, working files, and local session history.

Colleague — An authorized Manifoldone project member who can view shared activity and, when the owner explicitly permits it, respond or control a session.

Handoff — Leaving enough durable project, Git, session, and status context for another authorized person to understand and continue the work.

Provider — The vendor and CLI behind a session: Claude Code, Codex, or Grok.

Project — A top-level workspace connected to a local working directory and its Git structure.

Project room — The durable human-readable surface around a project: its Git work, persistent agent sessions, terminals, files, documents, previews, and members.

Relay — The connected service path used by authenticated clients to follow or control shared activity. It does not run provider agents.

Session — A persistent agent conversation and work object. It has a provider identity, status, history, and—when supported by the provider CLI—a native resume identifier.

Session wall — The visual work surface for docking several sessions, terminals, documents, and previews into one layout.

Shared session — An early-access session surface that another authorized person can follow or control. Permissions and active control must remain visible.

Teammate add — The current collaboration setup: a project owner searches for an existing registered Manifoldone account and adds it with a role. This is not yet an email or share-link invitation flow.

Workspace hierarchy — The sidebar structure from project to worktree or branch to persistent sessions.

Legacy terms

Older design documents may use Node, Thread, Director, Dock, Memory, or Pylon. They describe previous architecture drafts and are not canonical UI language.