Set up Ubimemo for WorkBuddy using https://ubimemo.com/guides/workbuddy. Download and verify the current package, then run the local helper quickstart --client workbuddy. Reuse my existing destination when present. Keep credentials private, preserve other connectors, and help me activate the connector and companion skill. Do not enroll or upload local files. Verify the synthetic save/read, then guide me through recall in a fresh conversation.
Existing or new account
Connect with an account
Sign in or register first, then connect a project from your account. Already connected? Keep using your existing setup.
Connect WorkBuddy to my Ubimemo account using https://ubimemo.com/guides/workbuddy#account-setup. Reuse any working connection. If I already have a guest project, help me register it and keep its memories instead of replacing it. Otherwise, help me sign in or register, choose or create a Lite project, and privately enter an account API key and project in WorkBuddy's connector settings. Download and verify the current package, preserve other connectors, and activate the companion skill. Never ask me to paste credentials into chat. Do not enroll or upload local files. Save and read back a synthetic setup memory, then guide me through recall in a fresh conversation.
Both options keep credentials out of chat. A working connection is reused. Guest setup is available when enabled by the service; account setup remains available independently.
One-time setup
Before you start
Ubimemo Connect
Version 0.3.0-beta.1 · ZIP · 356 KB For macOS and Windows · Node.js required
Node.js 22.13 or later and WorkBuddy on this computer. Check node --version in Terminal or PowerShell.
Guest onboarding creates My memories, a default Lite project, and a key restricted to that project. The private ownership credential is separate from the API key. Neither belongs in chat.
Guest setup is available when enabled by the service. If it is unavailable, keep the saved request and retry after rollout, or use the existing account setup described below.
For this setup, use the -standalone.tar.gz archive, ubimemo-memory.zip and SHA256SUMS from the download. Compare each file you use with its entry in SHA256SUMS. If a checksum differs, download a fresh copy before continuing.
01 / PROJECT
Choose your setup
Without an account: Quickstart reuses an existing valid setup, resumes an interrupted request, or creates a guest project. It stops on ambiguous destinations. Do not delete private state or create another profile to bypass an error.
For a new guest, no account, email, browser signup or manual key entry is needed. Connecting does not enroll local memory sources or upload conversations.
With an account: Follow the account setup steps to sign in or register first and select your project. If you already have a guest connection, use Register later to attach that same project; do not replace it with a new setup.
Choose an existing Lite project, or create a new Lite project for your memories.
In Account → API keys, create a key for this connection. Enter it only in WorkBuddy’s private connector settings. Account-wide keys can access your account’s projects; keep them private.
Already using a guest project? Register that project instead to keep its memories, keys and pending imports. Creating an account alone does not attach it.
02 / INSTALL
Install the connector
On the computer running WorkBuddy, start in the extracted download folder. Run one command at a time and stop on any error. Compare the archive’s hash before extracting or running it. The standalone archive includes JavaScript dependencies; Node is installed separately.
macOS · WorkBuddy installation Terminal
macOS WorkBuddy commands
shasum -a 256 ubimemo-connect-0.3.0-beta.1-standalone.tar.gz
# Compare with SHA256SUMS. Stop if the hash differs.
# Only after it matches:
tar -xzf ubimemo-connect-0.3.0-beta.1-standalone.tar.gz
cd ubimemo-connect-0.3.0-beta.1-standalone
node install.mjs
node install.mjs verify
Windows · WorkBuddy installation PowerShell
Windows WorkBuddy commands
Get-FileHash .\ubimemo-connect-0.3.0-beta.1-standalone.tar.gz -Algorithm SHA256
# Compare with SHA256SUMS. Stop if the hash differs.
# Only after it matches:
tar -xf .\ubimemo-connect-0.3.0-beta.1-standalone.tar.gz
Set-Location .\ubimemo-connect-0.3.0-beta.1-standalone
node .\install.mjs
node .\install.mjs verify
The installer prints the installed path and prepares connector/mcp.json with absolute Node and server paths. Default locations:
workbuddy_registration: required is expected. Installation does not add the connector to WorkBuddy; continue below. Keep the installed connector/mcp.json unchanged.
03 / CONNECT
Add the connector and its skill
WorkBuddy without an account
From the installed release directory, run node server.mjs quickstart --client workbuddy. Run the same command again after an interruption. The helper performs a synthetic save/read and prints the path to a secret-free mcp-local.json.
In WorkBuddy 5.8.3 on macOS, open Experts · Skills · Connectors → Connectors → Custom connectors → Add MCP. Labels may differ on Windows and other versions.
Merge the entry from the generated mcp-local.json into the existing mcpServers object. This editor replaces the whole file: keep a private backup and preserve every other entry. Its UBIMEMO_CREDENTIAL_MODE=local selects this computer’s private integration profile. Do not add UBIMEMO_API_KEY or UBIMEMO_PROJECT to this mode. Complete any host permission approvals.
Open Skills → Add Skill → Upload Skill and import ubimemo-memory.zip, or the installed connector/skills/ubimemo-memory folder. Enable the skill and preserve any customized instructions.
WorkBuddy with an account
After the account setup steps, use the installed connector/mcp.json. Preserve other entries when adding it to WorkBuddy’s Custom connectors. Privately enter your account API key and the exact unique Lite project name in the UBIMEMO_API_KEY and UBIMEMO_PROJECT fields. Keep this environment-key mode separate from the guest local-profile configuration.
Activate the connector and enable the companion skill using the same WorkBuddy menus above. If you already have a working connection, reuse it. A failed supplied key never falls back to guest credentials. Continue with the save/read and fresh-chat check.
Install the skill once. Then talk normally.
The MCP server provides the tools. The companion skill provides guidance to use them when earlier decisions or preferences matter. Adding the server alone does not install that guidance. You do not need to invoke the skill for every question.
04 / VERIFY
Check recall in a fresh conversation
Guest quickstart saves and reads a synthetic setup memory. For account setup, ask your assistant to save “Ubimemo setup check: the synthetic Cedar notebook is teal.” once, then read it back and check the exact text. Reuse the same operation ID and text if that save needs a retry. An accepted save, indexing readiness, installed tools and demonstrated recall are separate checks. Start a fresh WorkBuddy conversation and ask this question without supplying the answer:
What color is the synthetic Cedar notebook from our setup check?
Check that your tool:
Finds the right contextIt uses a relevant memory from your selected project without you pasting the answer.
Answers accuratelyIts answer matches the saved information, including any important constraints.
Shows its sourceIt cites the memory it used so you can check the original.
If the answer misses your saved context, follow the troubleshooting steps below.
Register later and keep your memories
Run node server.mjs register start. Open its short-lived link, register through email verification or sign into an existing account, then choose the destination account. Return to your tool and run node server.mjs register status. Check the verified email and project before explicitly confirming them. Only then run register confirm --account-id ID --confirmation-id ID with the exact status values.
Links expire after 30 minutes. An interrupted or expired claim leaves guest access intact; run register start again. Creating an account alone does not attach the project. Registration keeps project IDs, valid keys, memories and pending imports. Project-name collisions receive a visible suffix. Keys remain project-scoped.
Guests can retain 1,000 memories and 25 MiB, including retained versions and pending uploads. At capacity, reads continue and new intake pauses until registration. Guest data is not automatically deleted. Register before connecting another computer.
Optional recovery: run ownership export --file PATH in a private interactive terminal and enter a passphrase. Store the encrypted file safely. ownership import --file PATH validates the service and identity and restores ownership for registration only; it does not copy keys or enroll sources. Keep both the passphrase and ownership files out of chats and screenshots. Old backups lose ownership authority after registration.
After setup
Keep working. Let context follow.
Keep adding context to your Ubimemo project through saved notes, file imports or supported connected tools. New content needs to finish processing and indexing before it can be recalled. Synchronization follows each connected tool’s setup.
When earlier context matters, WorkBuddy searches your project, reads the relevant memories and cites what it used. WorkBuddy’s built-in memory stays separate; this connector does not automatically upload your WorkBuddy conversations.
To keep a new decision or useful detail, ask WorkBuddy to save it—for example, “Save this decision in Ubimemo.” You can review the saved memory in your project.
If something needs attention
Troubleshooting
Download or checksum mismatch
Stop and download a fresh copy. Verify checksums before execution.
Connector will not start
Check Node 22.13+, run install.mjs verify, and use the installed absolute paths. Native Windows activation and ACL checks remain release blockers until verified on Windows.
Key expired or revoked
Keys expire after 90 days. Before registration, explicitly run quickstart --client workbuddy --replace-expired to replace an expired key. Revoked keys are not silently recreated. Register to recover account control. After registration, use Account settings to replace that integration key and enter it privately with reconnect in its client profile.
Rate limit or storage limit
Honor Retry-After for temporary limits. At the guest allowance, register to continue intake. Reading existing memories remains available.
Destination conflict
Keep the existing configuration and journal. Select the intended setup explicitly; never reset state to force onboarding.
No recall or no_sources
Enable the companion skill, use a fresh conversation and check search readiness. No enrolled sources is expected after quickstart; explicit save and recall still work.
Timeout or conflict
Retry the same operation ID and exact content after a timeout. Preserve conflicting receipts and review the existing memory before changing it.
Notes for setup assistants
Follow the selected account or guest path; never silently switch paths after an error. Reuse working connections and register an existing guest project rather than replacing it. Download and verify the versioned package before running the helper. Never inspect private ownership or credentials files, print secrets, pass them as arguments, or put them in MCP results. Complete host activation steps while preserving existing configuration. Do not enroll sources without a separate explicit request. Registration confirmation requires the human to confirm the exact verified account and project after register status; never infer consent from the browser handoff. For recall, use search_memories, then read_memory with the returned document ID, revision ID and hash. Use the returned account ID and confirmation ID only after that confirmation, and repeat status if the destination changes. Report installed tools, accepted synthetic saves, indexing readiness and fresh-conversation recall separately. Do not claim a check was performed when it was unavailable.
Ubimemo