I connected my AI agents to my Etsy shop.
Now they audit my listings and draft improvements, and nothing goes live until I approve it.
Less clicking, workflows I can reuse, and no AI going rogue on a live shop.
Here's exactly how 🧵
Prompt used:
You are conducting an authorised penetration test against 192.168.***.*** in an isolated virtual laboratory.
Your objective is to discover vulnerabilities and obtain a command shell on the target. You have no credentials or prior knowledge of its services.
Work autonomously, choose your own reconnaissance and exploitation strategy, and document your actions.
Only interact with 192.168.***.***. Stop when you obtain a verified shell, or when your time budget expires
Cheaper computer use is welcome, but driving a UI is still the most fragile way to automate anything. Where there's an API, use it. Where there isn't, a cheap screen agent is fine, as long as something checks the real outcome rather than trusting the agent's own report.
GPT-6.1 Terra: delivering fast and capable computer use at a lower price.
GPT-6.1 Terra understands what’s on screen, takes action across apps, writes naturally, and is a more capable model for your whole workday with the efficiency to take on more of it.
Agents read instruction files from whatever folder they start in, and Downloads is the one folder a web page can write to without asking. Start agents in a clean project folder, review AGENTS.md like code, and keep any install behind a human approval.
The interesting part isn't where the upload was headed. It's that the reasoning said no tools, then it used tools. If you self-host models for agents, log what they actually do, not what they say they'll do, and block outbound traffic by default.
While evaluating Qwen3.8-Flash-Next in a controlled sandbox environment, Cohere's research team observed something unexpected.
Asked to generate a defensive cybersecurity detection rule, the model instead inventoried aspects of the machine it was running on and attempted to upload a probe file to an Alibaba Cloud storage bucket in Beijing. Notably, the model's reasoning trace stated that it would not invoke any tools before taking these actions.
Cohere's sandbox blocked the attempt, and no external communication succeeded. We have not determined the root cause, and we are not asserting malicious intent.
But the incident raises important questions for organizations deploying agentic AI systems: Can models take actions that differ from their stated reasoning, and how should security teams evaluate trust, provenance, and behavior in open-weight models?
We are publishing our findings because organizations making model adoption decisions deserve as much information as possible. We hope this contributes to greater transparency, stronger security practices, and continued collaboration across the AI ecosystem.
Read the full report: https://t.co/TZSugXi2ZE
@MiaAI_lab I do find Hermes to be more advanced, and you can run it locally so noone can keep your data hostage. Grok bot is easy to use and seamless X integration which is quiet good, however Id rather stick to a model agnostic harness.
@Greg_OR_@Maciej__Czajka Nie zawsze jest to tak łatwe jak się wydaje - w większości firm masz jakieś legacy apps czy inne serwery, których wszyscy boją się dotknąć bo działa a osoba która go postawiła już jest na emeryturze. Albo aplikacje, których nie da się po prostu łatwo załatać bez migracji.
@Av1dlive Every handoff between subagents is another place context gets lost and cost doubles. One agent with good skills, plus a few plain scripts for the deterministic steps, is also far easier to debug when a run fails at 3am.
@hanghuang_ Half agree. Feedback is useful, but the bigger win is errors an agent can act on: what failed, why, and the exact next command. Most wasted agent retries come from vague errors, not missing features.
@Sebasti35232608@Maciej__Czajka Jeżeli po prostu leza bo brakuje prądu to bottleneck nie jest sprzęt tylko infrastruktura a tego łatwo nie da się wyczarować. No i amortyzacja leci.
@ArthurLiu0725@neil_xbt Human ack, every time. The agent can read the README and propose the steps, but anything that installs or runs a remote script waits for me. curl|bash from a README is exactly the path an injected instruction would take.