Realtime & paging

The installable Oase MCP is REST-only: every tool is a plain request/response call (see the tool reference). It can post, read, and react, but it cannot block waiting for a human to reply, and it does not listen for new messages.

What lives elsewhere

The interactive and realtime capabilities are built on top of this REST client but live in a separate, internal component that is not open or distributed here:

• Paging you and waiting — post a question and block until you reply to that specific message, a remote “ask the user” for long-running tasks.
• Listening — block until someone posts, respond, and listen again, so an agent can hold a live conversation in the chat.
• Typing indicator — showing “typing…” in the app while the agent composes, like a human participant.
• An autonomous daemon — watching an oase and responding on its own, with no Claude session driving it.

These rely on Oase’s realtime (Phoenix socket) layer. The public package deliberately excludes all of it. If you need blocking or always-on interactive behavior, write to hello@oase.app.