Mulai Menggunakan Agent Studio Ulasan

326516 ulasan

NANDITA P. · Diulas sekitar 1 bulan lalu

Rohith N. · Diulas sekitar 1 bulan lalu

Gowtham S. · Diulas sekitar 1 bulan lalu

Good

Ali T. · Diulas sekitar 1 bulan lalu

worst

Suresh Kumar M. · Diulas sekitar 1 bulan lalu

247Y1A0520 T. · Diulas sekitar 1 bulan lalu

’m not satisfied. The instructions are unclear, and the process is time-consuming because it’s hard to find the information I need. Additionally, when I try to check my progress, I keep getting an error message even though I’ve completed the task.

Albert B. · Diulas sekitar 1 bulan lalu

very very badddddddddddddddd

Yazhini S. · Diulas sekitar 1 bulan lalu

Diego G. · Diulas sekitar 1 bulan lalu

Sammy G. · Diulas sekitar 1 bulan lalu

worst

Suresh Kumar M. · Diulas sekitar 1 bulan lalu

lab giving error on deployment

Abhinav S. · Diulas sekitar 1 bulan lalu

HARSHA SHARMA P. · Diulas sekitar 1 bulan lalu

Himanshu G. · Diulas sekitar 1 bulan lalu

HARSHA SHARMA P. · Diulas sekitar 1 bulan lalu

Gunapooshanam R. · Diulas sekitar 1 bulan lalu

Ignacio L. · Diulas sekitar 1 bulan lalu

Abyan Hisyam A. · Diulas sekitar 1 bulan lalu

Cheng Wai Kiang -. · Diulas sekitar 1 bulan lalu

Ok

Ali T. · Diulas sekitar 1 bulan lalu

Mithun M. · Diulas sekitar 1 bulan lalu

lab has various issues like i couldnt save the prompt or I couldnt find tab for system instructions as mentioned, and the settings tab for Global was also not visible for the model please fix on priority

JITHIN-A S. · Diulas sekitar 1 bulan lalu

Aquí está la reseña. Es firme pero concreta, porque las quejas con detalles técnicos son las que sí revisan: Rating: 1/5. Lab is broken in multiple places; the checks fail without a clear reason. I followed every step as written, and most of my time went into fighting the lab environment instead of learning. Task 1: the deployment can't succeed. The app that Agent Studio generates fails to build every time on npm install with Cannot read properties of null (reading 'edgesOut'). The generated template uses npm workspaces, "latest" for nearly every dependency, and node:20-slim. I reproduced the failure 3 times. Clicking "Update app", which the instructions recommend, rebuilds the same broken code. I fixed the Dockerfile myself and redeployed from Cloud Shell. The Cloud Run service built successfully, was Ready, and served the app. The checker still marked the task incomplete, because it apparently reads Agent Studio's internal status and not the actual service. Model and region errors. Prompts failed with a 404 because gemini-3.8-flash was not available in us-central1, even though saving prompts requires us-central1. The image task defaults to Nano Banana 2.1, which the lab's own organization policy blocks (constraints/vertexai.allowedModels). Nothing in the lab warns about either issue. Checks give no useful feedback. Several tasks I completed show 0/20, with no explanation of what is missing. The only message is a generic one that doesn't match what I did. Result: I ran out of time debugging Google's template, region settings and model policies instead of practicing prompt design. Please fix the generated app template, lock the correct model and region defaults, and make the checks report what they actually look for. I'd also appreciate a lab credit or reset, since the failures were not caused by user error.

Fernando G. · Diulas sekitar 1 bulan lalu

Gustavo M. · Diulas sekitar 1 bulan lalu

Franco C. · Diulas sekitar 1 bulan lalu

Kami tidak dapat memastikan bahwa ulasan yang dipublikasikan berasal dari konsumen yang telah membeli atau menggunakan produk terkait. Ulasan tidak diverifikasi oleh Google.