You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π Your agents can post on X, with your approval. Connect your own X developer app in Tools β X and, through it, as many X accounts as you manage (a project's, a brand's, a personal one). Each account lists the agents allowed to post on it, and a new account starts with nobody. An agent with the x_accounts and x_post tools publishes a post or a thread, with up to four images per part, and every post waits for you: the approval card shows the account, every part as it will go out with its character count, the images and the estimated cost, and so does the Telegram notice. The server publishes only the exact post you approved, once. X's API is pay-per-use (about 0.015 USD per post, 0.20 USD with a link), charged to your developer account.
π Your own callback page. X only sends the browser back to an https address, so you publish a small page HydraOps gives you (download it from the X card) on any hosting, free or paid. The manual walks through GitHub Pages step by step. On that page, Continue finishes the connection on this computer, and Copy gives you the address to paste in the card when HydraOps runs on another machine.
π§² Searching a project no longer pulls its files into the chat. The harvest that runs after every connection tool call now leaves alone the files that already existed before the task started, so a model a Unity search listed no longer shows up as a card.