More help with your AI assistant

Get the result you meant, and know what to do when a task needs attention.

If your connection needs attention

Check the account shown during sign-in. It must be the account that owns the Archive you want to use. Read the permissions before you agree.

If your assistant asks you to sign in again, stop the task and follow its sign-in prompt. Keep the original conversation if an edit or export was interrupted. Never paste passwords, access tokens, or browser-session details into a chat.

If the service is unavailable, wait before trying again. Repeated attempts will not fix an outage. Contact support with the assistant you use and the error message.

Account permission and task instructions

Sides requests its finite enabled read and write permission bundle together at hosted sign-in. It covers the enabled modification, confirmed deletion, export and artwork operations. Independent grants, ownership and current access still control every call. Old or partial grants remain limited; reconnect deliberately if you need to review the current bundle.

The client manages sign-in and tool discovery. The MCP server declares the operation inputs, effects, limits, state requirements and recovery behavior. Optional skills supply research and conversational procedures, not permission or extra server capabilities.

With intake guidance loaded, approve proposed metadata, artwork or both, or give explicit direct-intake authority for the selected component and scope. Exact supplied corrections can execute directly. Previews are optional, write nothing and reserve nothing.

Deletion still needs the exact target and consequences confirmed. Deleting a Title removes its Copies; deleting a Collection keeps the records. A root Copy cannot be deleted on its own. Replacing an existing cover needs specific replacement intent tied to the current artwork state.

If the tools look old, refresh discovery and try a fresh session. Recreate a stale connection only if ordinary refresh/reconnect does not work. Repeated scope-upgrade requests do not repair an unchanged grant. Contact support without sending credentials.

Get a precise search result

Keep conditions together
“Jazz LPs in VG+ condition” means the conditions must all match. When you choose more than one value for the same detail, such as LP or CD, either can match. Choosing a value and “not set” for the same detail also allows either to match. A missing-detail search only applies where that detail belongs to the Title’s Category.
Match one Copy
An LP in VG condition and a different CD in VG+ condition do not make a VG+ LP. Ask your assistant to show which Copy matches. The Title’s root Copy can be different from the matching Copy.
Use your Archive’s choices
Your assistant should use the Genres, formats, and other choices represented by saved records. An unused Genre you have created does not mean any Titles will match it.
Search missing details carefully
Ask for a supported missing field, such as original release year, or inspect a small set of records. One search cannot find every kind of incomplete information. Location search and missing-date search are not supported.
Give complete dates
Choose valid calendar dates for both the start and end, with the start no later than the end. Date ranges include whole UTC days, including the first and last day. A purchase-date condition must apply to the same Copy as its format or condition.
Understand artwork results
A search for Titles with or without artwork uses the root Copy’s artwork. It does not inspect every Copy’s cover as if they were the same Copy.
Continue without changing the question
Results arrive in pages. Ask for more while keeping the same search, Collection, conditions, and sort. Empty results mean no match; choose a particular refinement before trying a broader search.

Handle an interrupted change

If you don’t know whether an edit saved, keep the conversation and ask your assistant to check that original request. Ask it to reuse the exact original request, expected record state, and retry key to recover the outcome, then read the current record. Starting a new request can repeat a change that already succeeded.

After checking an earlier result, ask to see the record as it stands now. An old success message does not show changes made since then.

If the record changed while you were editing, read the latest values and decide whether your intended correction still applies. Don’t replace a newer value just because it differs from an earlier suggestion.

When changing several Copies, ask for the outcome for each one: some can succeed while others fail. A completed batch report keeps its original outcomes; repeating that request will not retry failed Copies. Review those Copies as they are now before asking for a new attempt. Groups of Title edits and Collection membership changes are saved together, so a failed group leaves the group unchanged.

Keep a task manageable

Start with a few records and ask for more when needed. Search pages contain up to 25 results; ordinary groups of Title or Copy edits can include up to 50 selected records. Collection membership changes can cover up to 100 selected Titles.

Be specific about which records to change. A search is useful for finding candidates, but your assistant should agree on the selection before editing it. Avoid “change everything” when a deliberate selection would do.

If a result is too large, ask for fewer records per page or a narrower question. If you rename your Archive, choose a nonempty name of at most 120 characters.

Date searches show current records. They do not provide a complete history of deleted records, every intervening update, or Collection membership changes.

Save artwork or an Archive export

Original artwork retrieval and full Archive export are included in the upfront enabled bundle but checked as independent permissions. Decide which data the task may release; a broad grant is not an instruction to download the whole Archive.

An Archive export includes your records and original uploaded artwork. Choose JSON, TSV, or CSV; CSV supports comma, semicolon, or pipe separators. The export is prepared in the background and reflects the records when preparation runs. Ask your assistant to check when it is ready rather than requesting another export.

A previously accepted export request does not mean its file is still available. If a file has been replaced or removed, request a fresh export deliberately.

For an interrupted download, keep the same export or artwork version when resuming. If that version changed, start a fresh download rather than joining parts of different files. Check the completed file’s size and checksum before opening it.

For local file reconstruction, follow the transfer references/helpers in the relevant optional task skill. Use only a transfer route your client actually supports. Keep the output and captured events private: they contain the Archive data you released. The helper saves a completed file only after its checks pass.

To attach a cover, the assistant may use an image you supply or acquire an original image file with its own supported tools. It must then use a supported upload, publication or byte-transfer route. A displayed preview, web page, Library identifier or raw local path is not by itself a server-facing file. Ask the assistant to identify where it got stuck. If the client cannot pass the selected file to Sides, leave the cover pending or add it directly to the intended Copy in Sides.

The server accepts one declared source: a file object with genuine download_url and file_id, or supported image MIME/base64 byte input. The client may mediate its own selector into that object. Follow the schema actually exposed by the client; never fabricate file identifiers, download destinations or image bytes. Sides retrieves files only through bounded public HTTPS; the MCP server cannot open the assistant’s local filesystem.

Preview, retrieval and upload are separate checks. A successful download can still produce a broken inline preview. A saved cover may be accessible to the authorized Sides tools even when the client’s image renderer cannot open it. Ask for the saved cover on the specific Copy. If it cannot display inline, open the Copy in Sides. For a proposed cover, wait until you can inspect the exact image before approving it.

Preserve the selected original image bytes. Supported images are JPEG, PNG or WebP, at least 64 × 64 pixels, at most 16 million pixels and within the configured upload limit, no more than 5 MiB. Do not substitute a screenshot, thumbnail, recreation or silent resize. Identify the target Copy and current artwork state before the separate artwork operation; replacing an existing cover needs specific confirmation.

A new Copy must exist before artwork can be attached. Metadata and artwork do not form one atomic save. Ask for separate saved, pending or failed outcomes. Optional validation is non-writing and does not prove a later commit succeeded.

Find the right help

Sides is in beta.

Start building your Archive now. Sign up before January 1, 2027 (Pacific time), and your 14-day trial clock won’t start until January 1.

You can use Sides through January 14, 2027 (Pacific time), with up to 50 Titles and 5 Maestro assists for the whole trial.

Use the extra time to explore Sides with your own recordings and let us know what could work better.

Start free trial