WobeSync / Documentation
A guide to your workspace.
Everything you need to organize work, write together, and keep your team moving.
Updated 18 October 2026 · Features depend on your access and service configuration.
What lives in your workspace
Keep context, ownership, and progress together. People and connected clients work with the same records.
Wobe assistant
Ask questions, find workspace records, and request actions in text or voice. Review action cards and follow progress in chat.
Reminders and tasks
Use reminders for follow-through, deadlines, recurrence, attachments, and ownership.
Notes
Write and format shared notes, collaborate live, dictate at the cursor, and ask Wobe to refine or edit a passage by voice.
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
Create your account and confirm your email address.
Open or create a workspace. Personal work can stay in your personal space; team work belongs in shared workspaces.
Add your first reminder, note, or whiteboard so the workspace starts with visible context.
Invite collaborators when the work should be shared with a team.
Open Wobe to ask about your workspace, or open a note and choose Edit note to write together and use voice tools.
Connect MCP from Settings if you want Cursor, Claude, or another client to use the same records.
Write and collaborate in live notes
Open Notes, choose a note, and select Edit note. Your title, content, and folder changes save automatically; check the save status before leaving.
Write, organize, and save
Use the toolbar for highlight, bold, italic, strikethrough, inline code, headings, quotes, bullet lists, numbered lists, and images from a URL. Undo and Redo are beside the formatting tools.
Pin frequently used notes from the note list or reader. Use the folder picker above a note to move it or create a folder.
Wait for All changes saved. If the title cannot save, use Retry autosave. If another person renamed it, choose Use shared title or Keep my title.
Find a collaborator’s place
The Live together strip shows people in the note, with colored cursors and selections in the content.
Select a person’s name to jump to their cursor when it is available. Choose Back to my cursor to return to your editing position.
To ask someone about a passage, select up to 500 characters and choose Mention. Pick a workspace collaborator and add a message if needed. The passage is highlighted, the mention stays below the note, and the collaborator receives an email.
Continue editing the shared note. If your connection drops, check the save status and let it reconnect before leaving; do not assume pending edits have saved.
Browse earlier versions
Choose History in an open note. Select a point in the timeline, or use Earlier and Later. Removed and added text is highlighted inside the note, with the recorded editor beside each change.
Choose Back to current to resume editing. You can save a named version once all changes are saved.
Choose Restore this version and confirm to make an earlier version current. The version you replaced stays in the timeline.
Refine a passage with a preview
Select up to 12,000 characters and choose Refine. Ask for a change or use Make it clearer, Shorten it, Fix grammar, or Make it professional.
Choose Refine selection, review or edit Your refined version, then choose Replace selection. Generating a preview does not replace your text.
If the selected passage changes while the preview is open, close the panel and select it again. Use the editor’s Undo control to reverse an applied refinement.
Write and format notes by voice
In Edit note, the floating voice controls offer two modes: Dictate adds your spoken words, while Talk to this note discusses and edits the open note when you ask.
Dictate at the cursor
Place your cursor where the text should go, choose the microphone button, then Start dictating. Allow microphone access when prompted.
Completed phrases are added directly to the note at the cursor. Use the note’s Undo control to correct an insertion.
Choose End and allow the final phrase to finish transcribing. Check the note and its save status before leaving.
Talk to this note
Choose the waveform button, then Start live conversation. Ask about the note, request a summary, or give an explicit editing instruction.
Identify text naturally: ‘Shorten the pricing section’, ‘Replace Friday with Monday in the deadline’, or ‘Make that bold’. You do not need to select text or count paragraphs first.
If the target is ambiguous, clarify the passage or occurrence. Voice edits appear directly in the editor; watch the save status to confirm persistence.
Use the formatting tools hands-free
Say ‘Highlight the deadline’, ‘Italicize the introduction’, ‘Strike through that phrase’, or ‘Format this phrase as inline code’. You can also request underline or remove text formatting.
Say ‘Make the introduction a heading’, ‘Use a level-three heading’, ‘Turn the next steps into bullets’, ‘Make that a numbered list’, or ‘Format the passage as a quote’. Code blocks and plain paragraphs are also supported.
To insert an image, provide its HTTP or HTTPS URL and say where it belongs. Wobe does not find or invent image URLs. Tables and checkboxes are not currently supported by these note voice tools.
Interrupt, correct, and undo
Speak while Wobe is responding to interrupt and give your new instruction. An edit already applied stays in the note unless you ask to change or undo it.
Say ‘Scratch that’, ‘I meant Friday’, ‘Undo the last two changes’, or ‘Redo that’. Voice history supports multiple recent voice edits.
If typing or another person’s edits make a voice undo unsafe, use the editor’s Undo control instead. Check the result before continuing.
Control the session
Mute or unmute the microphone, expand Transcript to review the conversation, or choose End. Closing the voice panel ends its session too.
Drag the grip to move the floating controls. Their position is remembered in this browser; the grip also supports arrow keys.
Audio is sent to OpenAI. Only one microphone session runs at a time, and sessions end after ten minutes. Start again to continue. Note conversation tools act only on the open note; use Wobe chat for workspace-wide requests.
Ask Wobe to help with workspace work
Open the Wobe button from your workspace. Its current space, view, and selected record provide context for your request. Be explicit about which records you want to change.
Find, discuss, and act
Workspace search is Automatic by default for both text and workspace voice. Ask about the current workspace, name another workspace, or say ‘across all my workspaces’. Use the scope selector to override this with Current workspace or All my workspaces. Only workspaces you can access are searched; Talk to this note stays limited to the open note.
Ask questions or request work in the composer, for example ‘Find my overdue tasks’ or ‘Summarize this note’. Wobe uses the records your account can access.
Use the thread list and search to return to earlier conversations. Expand References when a response includes links to source records.
For spoken workspace requests, choose Start voice chat in Wobe’s voice controls. For chat dictation, choose Start transcribing, review the text, then Add to composer before sending. Note dictation inserts directly into the note.
Review actions and follow progress
When Wobe presents an action card, review the proposed changes and use the approval control on that card. For deletion, inspect the confirmation and affected records carefully.
Spoken approval does not approve a protected action. Return to the pending card in chat to confirm or cancel it.
While a request is running, follow its progress in chat. You can refresh or leave the page and return to the thread. Use Stop to request cancellation; the current step may need to finish, and Stop does not undo completed work.
Troubleshoot voice and saving
Use the message in the app to distinguish microphone access, connectivity, and service availability. Repeatedly starting a session will not fix missing permissions or exhausted API credit.
Microphone access is denied or times out
Allow Microphone in your browser’s site settings for the WobeSync address you are using, then reload the page.
On macOS, open System Settings → Privacy & Security → Microphone and enable the browser, or WobeSync when using the desktop app. Restart it if prompted.
Voice requires a supported browser on HTTPS or localhost and a working microphone. Requesting microphone means access is still pending; Connecting voice means the app is establishing the voice connection.
No audio or a disconnected session
If Play voice audio appears, select it to allow playback. Check your output device, volume, and microphone mute state.
After a connection failure, check your network and start a new session. Review completed transcript text and any edits already applied before repeating a command.
If voice reports unavailable API credit or quota, ask the service administrator to check the configured OpenAI API account’s billing. Changing microphone permissions will not resolve that error.
A change has not saved
Check the live note save status. A spoken acknowledgment means an edit was applied in the editor; All changes saved confirms synchronization.
Resolve title conflicts using the choices shown in the note. If a folder was moved by someone else, check its current location and select your destination again.
For stale voice targets or changed refinement selections, identify the passage again. Avoid repeating broad changes until you have checked the current content.
Common workflows
Follow up on something discussed in AI chat
Open the right workspace.
Create a reminder or task with the owner and due date.
Add supporting context in the notes field or create a related note.
Use reminders so the work does not disappear after the conversation ends.
Capture a product or ops issue
Create a change request with a clear title and expected outcome.
Set priority, impact, and risk so the team can triage it correctly.
Assign owners and move it through the defined statuses.
Link the change request back to any whiteboard, note, or task that led to it.
Turn early thinking into structured work
Start with a whiteboard to map the idea or workflow visually.
Create a task or change request directly from the whiteboard.
Keep the board as the reference artifact while the structured item carries ownership and status.
Update the linked records instead of creating duplicate copies of the same work.
Roles and access
- Workspace editor
- Can work with shared records in spaces where they have editor membership. Access to other spaces is not granted by that membership.
- 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.
Connect an MCP client
Use your workspace from Codex, Claude, or another MCP-capable client.
Go to Settings → AI connections and copy the OAuth MCP configuration.
Add it to your MCP client, then sign in to WobeSync and approve the connection when prompted. You can also create a manual API key in Settings.
Refresh or restart the AI client after setup so the agent loads the new tools.
Keep the API key private. Tools enforce your account permissions and the key’s required scope; expired or revoked keys cannot connect.
Once connected, agents can work against the same reminders, notes, whiteboards, skills, and change requests visible in the app.
Create a separate API key for each client. Store keys securely and revoke them when a client is retired or a credential may have been exposed.
Security and good practice
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 questions
- Do I need MCP to use Wobe inside the app?
- No external MCP client setup is required to open Wobe in the app. MCP connection settings are for connecting external AI clients. AI and voice features still depend on the service’s configuration and availability.
- Does discussing a note change it?
- Talk to this note is instructed to edit only when you explicitly ask. Dictate is different: it inserts completed spoken phrases directly into the note. Use the appropriate mode and review changes as you go.
- Can I use the desktop app?
- The desktop app supports email and password sign-in. If you normally sign in with Google, use Forgot password to set a password for desktop sign-in. Allow microphone access for WobeSync separately from your browser.
- 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.