Gemini CLI tips and tricks for agentic coding
1–10 of 152 posts
Re: Gemini CLI tips and tricks for agentic coding
#2Re: Gemini CLI tips and tricks for agentic coding
#3Integration with Google Docs/Spreadsheets/Drive seems interesting but it seems to be via MCP so nothing exclusive/native to Gemini CLI I presume?
Re: Gemini CLI tips and tricks for agentic coding
#4Re: Gemini CLI tips and tricks for agentic coding
#5Re: Gemini CLI tips and tricks for agentic coding
#6Re: Gemini CLI tips and tricks for agentic coding
#7A lot it seems to mirror syntax of Claude Code Integration with Google Docs/Spreadsheets/Drive seems interesting but it seems to be via MCP so nothing exclusive/native to Gemini CLI I presume?
Re: Gemini CLI tips and tricks for agentic coding
#8still i had high hopes for gemini 3.0 but was let down by the benchmarks i can barely use it in cli however in ai studio its been pretty valuable but not without quirks and bugs
lately it seems like all the agentic coders like claude, codex are starting to converge and differentiated only by latency and overall cli UX and usage.
i would like to use gemini cli more even grok if it was possible to use it like codex
Re: Gemini CLI tips and tricks for agentic coding
#9It Fucked up the entire repot. It hard coded tenant ids and used ids, it completely destroyed my UI. Broke my entire grpahql integration. Set me back 2 weeks of work.
I do admit the browse version of Gemini chat does much better job at providing architecture and design guidance time to time.
Re: Gemini CLI tips and tricks for agentic coding
#10Why is this AI generated slop so highly upvoted?
Of Addy Osmani fame.
I seriously doubt he went to Gemini and told it "Give me a list of 30 identifiable issues when agentic coding, and tips to solve them".