Give each subscription a clear job
Think of Rayito as the part that connects a question to your screen and presents the answer in a usable way. The provider supplies the model behind that answer. Paying for one does not automatically activate the other. This distinction matters when comparing a screen companion with an app that bundles a fixed allowance of model requests.
Your provider can still apply its own plan requirements, usage limits, service availability, and terms. Rayito does not turn a limited plan into unlimited access. If the provider stops accepting requests, a working microphone and drawing overlay cannot produce a new model answer by themselves. Check the connection separately from the companion’s account status.
Check the connection that is actually available
The public Rayito site describes connecting an installed Claude Code client that you have signed into through its own supported account flow. Keep that sign-in under the provider’s control. You should not treat a request to paste subscription credentials into a random webpage as part of the normal screen companion workflow.
ChatGPT subscription support is pending commercial availability. A local development build or a planned Codex connection is not the same as a generally available, commercially approved sign-in option. Before choosing a plan for this purpose, read the current Rayito availability notice and the provider’s supported-plan information. This guide does not promise that a connection shown in development is ready for every customer.
Separate access problems from screen problems
If Rayito can hear a question but cannot obtain an answer, begin with the provider connection: is the selected assistant installed, signed in, and available? If answers work but the visible source is missing, look at screen access and the current window instead. If an explanation works but an action cannot run, that is another layer involving app control and its permissions.
This separation avoids changing several settings at once. Test one simple question with ordinary visible content, then inspect whether the answer refers to the correct screen. Only after that should you try a selected-app action. A short, staged check is easier to interpret than a large request that depends on voice, screen access, model access, and action permissions simultaneously.
A question to try“Explain the relationship between these two visible values.”
Compare the total arrangement before subscribing
Consider both the companion price and whatever supported AI plan you intend to use. Also consider the workflow: which connection is available, whether your Mac can run the needed local voice components, and whether you want actions as well as explanations. The public website remains a preview. Use its demonstrations to understand the product, and confirm current availability before planning work that depends on it.