Documentation
WobeSync documentation
Everything users need to understand workspaces, records, MCP setup, permissions, and day-to-day operating flow.
Capture
Save a decision, follow-up, or issue from an AI or team conversation before it disappears.
Structure
Turn it into a note, reminder, whiteboard, skill, or change request with context and ownership.
Assign
Move work into a shared workspace where a real owner, due date, and collaborators are visible.
Follow through
Track status, review changes, and keep the same records available to both humans and MCP clients.
What gets tracked
The core records users work with every day.
Reminders and tasks
Action items with owners, dates, completion state, and reminders.
Change requests
Bugs, improvements, and product requests with status, priority, and assignees.
Whiteboards and notes
Visual thinking and written context that can become structured work.
Skills
Reusable instructions and playbooks shared between people and AI agents.
Admin visibility
Platform admins can review health, usage, and user activity across the workspace system.
At a glance
What the app is for.
Use WobeSync when the output of a conversation should become visible, assigned, reviewed, and reusable. It is designed for operational follow-through rather than temporary chat memory.
Reminders and tasks
Use reminders for follow-through, deadlines, recurrence, attachments, and ownership.
Notes
Store structured context, summaries, operating notes, and collaboration history inside a workspace.
Whiteboards
Sketch flows, capture early thinking, and turn a board into a task or change request when the idea becomes actionable.
Skills
Create reusable human or AI playbooks that can be shared across workspaces and used through MCP.
Change requests
Track bugs, enhancements, configuration changes, and new features from intake through review and resolution.
Dashboards
Review personal productivity, team progress, change request health, and platform activity where permitted.
Getting started
First-use checklist.
- 01
Create your account and confirm your email address.
- 02
Open or create a workspace. Personal work can stay in your personal space; team work belongs in shared workspaces.
- 03
Add your first reminder, note, or whiteboard so the workspace starts with visible context.
- 04
Invite collaborators when the work should be shared with a team.
- 05
Connect MCP from Settings if you want Cursor, Claude, or another client to use the same records.
Best practice
How teams usually structure work.
Use spaces as operating boundaries
Keep each workspace tied to a person, team, or operating area so records stay discoverable and permissions stay clear.
Keep context close to the work
If a task or change request needs background, attach it as a related note or whiteboard rather than burying it in chat.
Prefer one source of truth
Update the existing record instead of creating duplicates in multiple tools or multiple workspaces.
Treat agent output like draft work
Capture the result, assign a human owner where needed, and use the app to track review and follow-through.
Common workflows
The most common ways users operate in WobeSync.
Follow up on something discussed in AI chat
- 1
Open the right workspace.
- 2
Create a reminder or task with the owner and due date.
- 3
Add supporting context in the notes field or create a related note.
- 4
Use reminders so the work does not disappear after the conversation ends.
Capture a product or ops issue
- 1
Create a change request with a clear title and expected outcome.
- 2
Set priority, impact, and risk so the team can triage it correctly.
- 3
Assign owners and move it through the defined statuses.
- 4
Link the change request back to any whiteboard, note, or task that led to it.
Turn early thinking into structured work
- 1
Start with a whiteboard to map the idea or workflow visually.
- 2
Create a task or change request directly from the whiteboard.
- 3
Keep the board as the reference artifact while the structured item carries ownership and status.
- 4
Update the linked records instead of creating duplicate copies of the same work.
Roles and access
Who can do what.
Workspace member
Can work with the records shared in spaces they belong to, based on their membership and the features exposed in the app.
Workspace owner
Can manage invitations, remove members, and control the shared workspace setup.
Role-based visibility
What you can see in WobeSync depends on the workspaces you belong to and the level of access assigned to your account.
Shared workspace access
People in the same workspace can collaborate on the records shared there, while private or unrelated workspace content stays outside their view.
MCP connection
How AI clients fit into the system.
- 01
Go to Settings and create an MCP API key for the client you want to connect.
- 02
Copy the generated configuration and give it to Codex, Claude, or another MCP-capable client with a prompt to set up the MCP server.
- 03
Refresh or restart the AI client after setup so the agent loads the new tools.
- 04
Keep the API key private. It has the same access as your account.
- 05
Once connected, agents can work against the same reminders, notes, whiteboards, skills, and change requests visible in the app.
API keys should be created per client, stored securely, and revoked when the client is retired or the credential may have been exposed.
Security and operating notes
Guidance for safe and reliable use.
Keep secrets out of broad workspace records
Use normal security judgment. A shared workspace should not become a dumping ground for production secrets or credentials.
Use API keys intentionally
An MCP key acts with the same access as the issuing user, so create it only for clients you trust and revoke it when no longer needed.
Prefer clear ownership
A task or change request without an owner is easy to ignore. Assign work explicitly whenever follow-through matters.
Use the app as the reference layer
If an AI conversation produces a decision or instruction that matters later, capture it in WobeSync rather than assuming the chat history will remain the source of truth.
Frequently asked
Practical questions users usually ask first.
When should I use a note versus a task?
Use a note for context, reference material, or documentation. Use a task or reminder when something needs an owner, a date, or completion tracking.
When should I use a change request?
Use a change request when the work is a bug, enhancement, new feature, or configuration change that needs review, prioritization, and status transitions.
Do agents see a different dataset from humans?
No. The product is designed so MCP-connected agents work with the same core records your team sees in the app.
How should I treat API keys?
Treat them like passwords. Store them securely, revoke them when they are no longer needed, and create separate keys for different clients.