6 comments

  • tptacek 2 hours ago

    A reminder that, while this is pretty neat and also probably offers a lot of convenient tooling for GCloud resources already built, an "agent" is simply an LLM call in a loop, each call presenting some number of available tools. If you're building your first agent, I'd recommend coding to an LLM API (probably the OpenAI Responses API, which is sort of a lingua franca of LLMs now) directly.

    This is one of those cases where it's really helpful to code, at least once, at one layer of abstraction below the one that seems most natural to you.

    • czbond 2 hours ago

      Agree. I've first used the Responses endpoint, and besides context like questions - it made me realize I did not want to build or self host in a lot of the gaps AI agents really needed. Eg: context, security, controls, external data source connection management, interaction mapping, etc.

  • jand 2 hours ago

    I have not test-driven adk-go. But if you - like me - have not toyed around with agents until now, there is a readable, nice example in [1] which explains itself.

    [1] https://github.com/google/adk-go/tree/main/examples/web

    • czbond 2 hours ago

      I was surprised a native typescript style agent wasn't a core initial offering.

  • kami23 an hour ago

    Been looking forward to this. I'm not up to date on my python and reviewing Claude's implementation of the python library has taught me a lot.

    Gonna point Claude at our repo and see if I can do an easy conversion, makes the amount of reviews I have to do a bit more bearable.

  • czbond 2 hours ago

    Thanks for posting. I am in the midst of evaluating some combination of n8n, open ai swarms, and others. This is a great addition