Compatibility and known limitations

What a compatible client needs

Oddlynew connects through a remote MCP server. A compatible client must support authenticated remote MCP connections, allow the Oddlynew connection for the user's plan or workspace, and make the resulting tool available to the conversation or agent that will use it.

Client support is not interchangeable. Availability can depend on the client product, plan, workspace administrator, local configuration, and whether tools are enabled for the current conversation. A working connection in one client does not prove that another client supports the same path.

Connect

The shared remote MCP endpoint is https://mcp.oddlynew.com/mcp.

Claude Code

Run: claude mcp add --transport http --scope user oddlynew https://mcp.oddlynew.com/mcp

Then open /mcp inside Claude Code and complete sign-in.

Codex

Run: codex mcp add oddlynew --url https://mcp.oddlynew.com/mcp

Then run: codex mcp login oddlynew

ChatGPT, Claude, and other hosted clients

Use the client's current remote MCP or custom-connector setup, enter the endpoint above, and complete Oddlynew sign-in when prompted. Eligible plans, administrator approval, and per-conversation enablement belong to the client and may change independently of Oddlynew. If the client offers no remote MCP connection flow, these instructions do not make it compatible.

Exact click-by-click steps per client (ChatGPT web and desktop app, Claude, Claude Code, Codex) are published at https://oddlynew.com/agent-connect.md. An agent guiding a user through connecting should read that page instead of guessing current client UI.

Connecting and configuring are separate steps. After the connection works, use Setting up your client to give the agent durable routing guidance.

Check the connection

Start a fresh session and ask:

Identify yourself through Oddlynew, list the organizations you can currently access, and tell me which organization guidance you read. Do not write anything.

A working connection should invoke Oddlynew, name an accessible organization, and cite guidance it actually opened. An answer that merely repeats the prompt or says what it would do is not evidence that the connection works.

What authorization means

By default an Oddlynew OAuth connection covers every organization the user belongs to, including ones joined later. Some apps ask you to choose organizations when you connect, and under Your agents > Allowed apps you can narrow any connection to the organizations you tick; organizations joined later are then not added. There is no per-document selector. Each operation still checks delegated OAuth scopes, current membership, roles, enabled features, and the target organization's live access rules.

Review this boundary before authorizing a client. Revoke a connected application in Oddlynew settings when it should no longer act with that user's grant.

Current product boundaries

Oddlynew does not currently include its own reasoning model. The chosen compatible agent supplies the intelligence and invokes Oddlynew when it needs the shared knowledge layer.
Nothing automatically leaves a chat. Work becomes durable only when an authorized person or agent writes it into an Oddlynew document.
In the browser you can read, comment, and create a new document from pasted text or files. Connected agents edit existing documents through the current MCP surface.
Search is bounded retrieval, not an exhaustive truth oracle. Ranked modes use an asynchronous projection and may lag the live document state. Verify recent writes with a direct document read, and use catalog or exact reads when freshness is decisive.
Documents can be archived out of the default retrieval set and restored later. A deleted document goes to the trash, from which documents.restoreDocument brings it back for 30 days; deletion is not a promise of immediate permanent erasure.
Members can list, read and compare a document's versions (documents.listVersions, documents.compareVersions); no operation restores a whole document to an earlier version.
Oddlynew does not currently offer a supported complete organization-export contract.
Document references can target any organization the author can read. Every reader of the citing document sees the reference with the target's version and drift state, while the target's content resolves only for readers who can read the target. Copying an eligible document across organizations creates an independent snapshot, not a synchronized shared document.
Circular version-pinned references are supported, but repeatedly advancing every pin in a cycle to the other document's latest version is not guaranteed to converge. Pins preserve reviewed evidence rather than creating an obligation to chase the head; see Circular references and convergence.
Exact methods, fields, limits, and errors come from live server validation inside run. Public examples and guide explain the model but do not override that contract.

When to stop

Do not proceed merely because a client can connect. Stop and review the setup when the user cannot accept the account-wide Oddlynew grant, when the task requires document-level permissions, when a legal or compliance requirement is not covered by an approved agreement, or when a required client capability is unavailable.