Can't deploy to Google's Agent Engine using "Runner"?

[Axibord]

Apparently, Agent Engine only supports deploying simple agents right?

We can't attach: ArtifactService, MemoryService...and all other services because we need to pass them to a Runner.

Since complex workflows also need to be using the Runner to be able to use ArtifactService, MemoryService...etc we can't use them with "Agent Engine" right now?

What I mean is that this code can't be deployed to "Agent Engine" and at the same time it's the only way to pass the services.

runner = Runner(
    agent=my_agent,
    app_name="my_prod_app",
    session_service=cloud_session_service,
    memory_service=memory_service,
    artifact_service=artifact_service
)

Maybe I don't understand something, but i read all the doc

[Jacksunwei]

Agent Engine is meant to be pre-wired services. Right now, it only has hosted session service, the other two will come later.

---

If you're looking for a customized solution with 3 services from different providers, then cloud run is better fit.

[Axibord]

I'm not sure if I fully understand. So you're saying that for now we can't use the GcsArtifactServiceand VertexAiRagMemoryService if we deploy with Agent Engine, correct? (I guess so, because we can only pass them to a Runner)

[Axibord]

After digging deeper in the CLI, I found that MemoryService and ArtifactService are initialized using the InMemory... when deployed to Agent Engine. It's very confusing since the documentation doesn't specify that these services are being used under the hood by Agent Engine and how they are used.