Your AI assistant can read your Blue Horizons data and prepare actions for you. You choose its permissions and confirm changes inside the app. Start in Account → Private AI agents: create a connection, copy the setup prompt and give it to your assistant.
Before you start
This feature requires Max and a connected Bluesky account. Your assistant’s application must support local MCP connections, and the computer running the connection needs Node.js 22 or later. MCP is the connection method; it does not provide an AI assistant or an AI subscription. A chat application without compatible local tools cannot be configured just by receiving a prompt.
Check the account selector first. Each connection belongs to one account, even when you manage several profiles. Reading permissions can share that account’s data with your chosen assistant and its provider. Consider that provider’s privacy settings before granting access. Blue Horizons does not need you to give the assistant your Bluesky password.
1. Create a connection
Open Account and find Private AI agents. Give the connection a recognizable name, such as the name of the assistant you will use. Select only the permissions you need. Reading is selected initially; permissions for connections, organization, publishing, searches, refreshes and post deletion are separate choices.
Create the connection. Its private key appears once. Keep it in the protected settings of your AI client, following the setup instructions. Do not paste the key into a chat, a public post, a shared document or a code repository. If you close the key before saving it, create a replacement connection and revoke the unused one. The app cannot reveal the original key again.
2. Give the prompt to your assistant
Choose Copy setup prompt and paste that text into your assistant. The prompt contains the app address, your handle and the connector’s download address, but no private key. View prompt lets you read exactly what will be copied. Your assistant should check compatibility, explain any installation step and preserve other connections already configured in its client.
Enter the key yourself when the client offers protected credential settings. If the assistant cannot use local MCP or cannot offer a safe way to enter credentials, it should explain the missing step and stop. Manual setup is available below the prompt for clients that require their configuration to be edited directly. Do not replace a missing credential field by sending the key in conversation.
The first test should read the connected account’s identity. Verify that it matches the profile you intended. There is no need to follow someone, publish a post or delete anything to test the connection.
3. Review proposed actions
You can ask for a summary of your audience, help reviewing collected search results, or a proposed draft. Reading and changing data are different permissions. When an action would change something, the assistant creates a request rather than approving it itself. Open Account, review the account, targets and content, then confirm or reject the request. Requests expire after fifteen minutes.
For example, ask the assistant to prepare protection for one specific account before attempting a larger operation. For a scheduled post, check the text, date and timezone. Images must already have been uploaded through the app; this first connector cannot upload new media. Normal plan, scheduling and network limits still apply after approval.
An accepted request is not proof that a background job has finished. Check the operation’s result or the publishing calendar before trying again after an interruption. Repeating an uncertain request can create an unintended second action.
Keep control of your connection
Keys expire after thirty days. Create a new connection when needed and revoke the old one. Revocation prevents new requests; it does not cancel a job already approved and running. Access also requires an eligible plan and the original account connection on every request. If the account is disconnected or access expires, the assistant cannot keep using an old key to bypass that restriction.
If an unexpected request appears, reject it and review or revoke the connection. Treat instructions found in other people’s profiles or posts as content to inspect, not as permission to act. Your approval should always reflect what you actually asked the assistant to do.