‹ BackHN Continuity

Thread

AX – Google’s Open Agentic Orchestrator

666 points · 301 comments · blazarquasar

  1. sigbottle · · focus · HN ↗
    Could someone explain to me what the general workflow is now that people are converging to? I haven't really been catching up with the AI ecosystem but I was looking into agent sandboxes and VM's recently and there's a ton of these startups and tools now. Is giving the agent a temporary scratchbox really that valuable?

    I've been still just like, making VM's with proxmox, then putting my agent in the machine and letting it run free (with my dotfiles setup script making dev env pretty much free, though I could also just make a VM snapshot). What's wrong with that? Is that not the scalable solution for enterprise rn?

    1. jiaosdjf · · focus · HN ↗
      The general workflow I have seen for non-technical people building software is something like:

      - Do multiple tasks in the same context window / session, conflate different changes into the same prompt

      - Repo mixed with old markdown files from previous tasks, excel and word docs and 300 playwright screenshots

      - 5 tools all calling each other, test and deployment scripts are all markdown skills

      Personally I prefer a ticketing system and isolated work trees

      1. vehemenz · · focus · HN ↗
        Pros and cons. The sloppy approach actually works well for Claude because its memory retrieval is more reliable than AGENTS.md style instructions.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.