Release v0.1.36 · TraX22/HydraOps

Highlights

🛡️ The outside-content guard now follows it everywhere. Saving to an agent's permanent memory after reading a page is always held for your OK — even for agents you marked as trusted. When recall brings back an old answer written after reading outside content, that task is marked too; and a task an agent delegates from a marked task starts marked, so the other agent's actions are held as well.
📱 Approve or reject from your phone. Each held action reaches Telegram with ✅ Approve / ❌ Reject buttons (only for your paired chats). System → Security shows the log: which tasks read outside content and what happened to every held action.
🔑 Opening HydraOps to your network got easier. Set HYDRA_HOST and HydraOps generates its own access token, saves it, and shows it (with a copy button) only on the server itself in Config → Network access. The manual explains how to reach it from outside home with Tailscale, without opening router ports.
⏱️ Research agents get time to finish. A task can now keep the model working for 10 minutes with cloud models (15 with the local one) instead of 2 (5), so long market or news analyses no longer get cut — and if one still runs out of time, the chat says so in your language.
📊 Tables and 3D prompts, readable. Tables in agent replies have lines, a header row and full width; in the 3D plugin every iteration's prompt can be read whole and reused with one click.

3d: an iteration's prompt can be read whole and reused by @TraX22 in #83
chat: Markdown tables in replies get lines, a header row and room by @TraX22 in #82
workers: research tasks get 10 minutes (15 local) instead of 2 (5), and a cut task says why by @TraX22 in #81
server: opening the API to the network generates its token; Tailscale in the manual by @TraX22 in #80
security: the taint follows outside content into memory, recall and delegation; held actions on Telegram; a security log view by @TraX22 in #79

Full Changelog: v0.1.35...v0.1.36