The coding agent resolves the app resource name and runs agents-cli publish gemini-enterprise. Now the analyst asks, in the same app they use for everything else:
What materially changed for my semiconductor watch-list this week, and which company announcements aren’t backed by an SEC filing?
The answer comes back grounded and cited, with the claim-only bucket flagging exactly the announcements no filing supports. Prompts produced a governed, published enterprise asset, not a demo.
What comes next
None of this required a new UI, a second mental model, or a handoff between tools. ADK is open source, the platform services are managed, and the Agents CLI is the connective tissue that lets one assistant drive both. You moved through build, deploy, govern, optimize, and publish in plain English, and stayed in your coding agent the whole time.
Industry Watch is one example. The same shape fits any task that needs live data, an auditable answer, and a defended tool boundary.
Get started with the Agents CLI and build your first agent from a single prompt. The ADK docs cover tools, sessions, and evaluation when you want to go deeper. Your coding agent isn’t just where you write agent code. It’s the control plane for the whole lifecycle.
