<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipelinepilot on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/pipelinepilot/</link><description>Recent content in Pipelinepilot on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 09 Apr 2026 20:56:12 -0500</lastBuildDate><atom:link href="https://startaitools.com/tags/pipelinepilot/index.xml" rel="self" type="application/rss+xml"/><item><title>Vertex AI Agent Engine Forced a Same-Day Architecture Pivot</title><link>https://startaitools.com/posts/pipelinepilot-vertex-ai-migration-architecture-pivot/</link><pubDate>Sat, 01 Nov 2025 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/pipelinepilot-vertex-ai-migration-architecture-pivot/</guid><description>&lt;h2 id="the-plan-that-died-on-deployment"&gt;The Plan That Died on Deployment&lt;/h2&gt;
&lt;p&gt;PipelinePilot had a clean four-agent architecture. Orchestrator routes to Research, Enrichment, and Outreach. Each agent owns its tools. Each agent has a single responsibility. The Python ADK migration from YAML was already done. CI passed. Local tests passed.&lt;/p&gt;
&lt;p&gt;Then I deployed to Vertex AI Agent Engine and the entire multi-agent topology fell apart.&lt;/p&gt;
&lt;p&gt;Agent Engine cannot have multiple non-search tools on a single agent.&lt;/p&gt;</description></item></channel></rss>