I integrated Google Apps Script with VS Code + Codex + Claude — and it changed how I build applications

[Kildere S Irineu]

I recently changed the way I develop applications with Google Apps Script, and the difference in productivity and structure has been remarkable.

For a long time, the common approach was to develop directly inside the browser editor provided by Google Apps Script. It is simple and convenient, but as projects grow, the limitations of that environment become clear. Code organization becomes harder, version control is limited, and scaling an application architecture becomes challenging.

So I started experimenting with a different development workflow.

Instead of building everything inside the Apps Script editor, I now connect the project to a local development environment using (Command Line Apps Script Projects) and develop the application inside Visual Studio Code, supported by AI copilots such as Codex or Claude.

This small change transforms the entire development experience.

When Google Apps Script is integrated with VS Code, the project immediately benefits from the same ecosystem used in modern software engineering. The code can be structured more clearly, versioned with Git, refactored with advanced editor tools, and supported by extensions designed for professional development environments. Instead of working inside a minimal browser editor, the developer gains access to a full development platform.

Adding AI assistants like Codex or Claude amplifies this effect even more. The AI becomes a development copilot that can generate code, suggest architectural improvements, help refactor functions, organize components, and accelerate debugging cycles. Development becomes a collaborative process between the engineer and an intelligent assistant, dramatically increasing iteration speed.

In practice, the development loop becomes very efficient. First, the architecture of the application is designed. Then technical prompts are written inside VS Code to guide the AI assistant. Code is generated or refined, the project structure is validated locally, and once everything is ready the application is synchronized with Google Apps Script using a simple command such as clasp push. From there, the application runs inside the Google environment and can be tested immediately.

What makes this paradigm especially powerful is something that is often overlooked about Google Apps Script itself. A large portion of the infrastructure that developers normally need to build or manage already exists inside the Google ecosystem.

When applications run within a Google Workspace environment, several complex layers are already solved by the platform.

User identity and authentication are handled natively by Google accounts, which means there is no need to implement login systems, password management, or identity infrastructure. Access control can rely on the same permission model used across the organization, integrating naturally with Workspace policies and user groups. Hosting and runtime infrastructure are fully managed by Google, eliminating the need to configure servers, containers, or deployment pipelines.

Data integration is also dramatically simplified. Applications can interact directly with services such as Google Drive, Sheets, Gmail, Calendar, and other Workspace APIs. Security, identity management, and execution monitoring are already integrated into the platform. Logs and execution traces are available without additional infrastructure work.

Because so many foundational concerns are handled by the ecosystem itself, developers can focus almost entirely on the most valuable part of the system: application logic and problem solving. Instead of managing infrastructure layers, the effort is directed toward automation workflows, data processing, and building solutions that directly support business processes.

This combination creates a development model that is both simple and powerful. On one side, the Google ecosystem provides identity, security, infrastructure, and integration. On the other side, modern tools such as VS Code and AI copilots provide the productivity, flexibility, and engineering capabilities expected from contemporary software development.

The result is a workflow that feels much closer to modern cloud-native engineering, while still benefiting from the simplicity and integration of the Google platform.

Google Apps Script is often seen as a lightweight scripting tool. But when combined with a modern development environment and AI-assisted coding, it reveals itself as a surprisingly capable platform for building automation systems, internal tools, and enterprise applications.

Sometimes the most powerful developer platforms are the ones hiding in plain sight.

Kildere Sobral Irineu
Systems Analyst | AI Agents Developer
MBA in Business Administration & Management

LinkedIn: https://www.linkedin.com/in/kilderesobralirineu/

[SMAARTE Group]

Our just use Google Antigravity and Gemini Ultra and that pretty much does the trick...

Regards,

Steve Horvath

SMAARTE Group

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/267bb0b4-08b9-4942-a4b5-dbaafde17bcbn%40googlegroups.com.

[Kildere S Irineu]

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/CAMnbTs3BEwrOA_ec7T0CjJOxmLwErUBfBe0WuyJV6Cg5Zy3DTA%40mail.gmail.com.

[webs...@danhinsley.com]

I’m about to embark on this on my Windows system.  Any chance you could provide a checklist for how to connect and existing Google Apps Script to my local VS Code?

--

[webs...@danhinsley.com]

I have everything installed, just need to know how to link my google script to vs code.

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/022401dcb585%24510cbf60%24f3263e20%24%40danhinsley.com.

[webs...@danhinsley.com]

OK, clone the script, but it doesn’t appear they are really linked, changes made in my local copy don’t propagate to the google server copy.  Plus it doesn’t appear like I debug from inside VS Code.

 

Am I missing something?

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/022b01dcb586%2466f59d50%2434e0d7f0%24%40danhinsley.com.

[Michael O'Shaughnessy]

@Kildere - Pretty cool that you got it working with an IDE you are comfortable with!!

Since my life is 100% online, I must rely on everything being internet based.  My main computer has been a Chromebook for the last 10 years!!  This is why I really like GAS's editor; however, even I, as an intermediate coder, am wanting some more "power."  I wish Google would "beef" up the editor a little more....

I tried the VSCode route both in a Linux terminal on my Chromebook and online. That did not go well.  I then tried GitPod and GitSpaces... still not what I wanted.  Then I stumbled upon IDX (now Firebase) and I like it. I took some time and created a starter template that uses Vite and CLASP.  It works, but I did all this during summer break (I am in education) and I had to put it on the back burner. 

At any rate here is a link to the repo: https://github.com/michaelos02/VITE-GAS-Starter

I did this with the assistance of Claude and the readme does a good job of explaining everything.  I have a "workaround" for logging into CLASP; however, I believe IDX (and most likely VSCode) have made some improvements.

Just sharing, maybe somebody can find it useful.

Thanks,

Michael

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/023601dcb587%247fc96630%247f5c3290%24%40danhinsley.com.

[Jhonny nelson]

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/CAJ-AUmgdU-Fvd%3Dyi_odiurJvE4BrJMf6Vx0tY4UFLfhfk0uWww%40mail.gmail.com.

[John Blades]

This was pretty awesome.  I'm a big youtube learner and seeing a video on setup and practical use would be pretty awesome!!!!

[webs...@danhinsley.com]

Has anyone made this work?  I’ve gone through the steps and still don’t see how to either sync changes I make on my PC or debug the script.

 

From: google-apps-sc...@googlegroups.com <google-apps-sc...@googlegroups.com> On Behalf Of Kildere S Irineu
Sent: Monday, March 16, 2026 12:21 PM
To: Google Apps Script Community <google-apps-sc...@googlegroups.com>
Subject: [Apps-Script] I integrated Google Apps Script with VS Code + Codex + Claude — and it changed how I build applications

 

I recently changed the way I develop applications with Google Apps Script, and the difference in productivity and structure has been remarkable.

--

[Bruce Mcpherson]

Or take it to next level and run native gas locally or on a range of platforms . https://youtu.be/oEjpIrkYpEM?si=L_s26mVW5jZbgMC8

On Wed, 18 Mar 2026, 16:22 Alex, <oshli...@gmail.com> wrote:

My stack is simple: Node + [Your Preferred] Code CLI.
I literally just prompt: "Make my life better."

And yes, that's actually enough to ship an app (screenshots below).

The catch: If you're wondering how that works, you need to understand the workflow first. Your prompt evolves: you start by asking "How?", and only then command "Better life".

In short, your stack should include:

• Skill with CLASP or Google Apps Script API.
• 3 roles (I run them as AI agents): Lead Dev, Apps Script Specialist, QA.
• MCP for UI validation.
• A bit of patience to wire it all up.

Development has changed. Now it's about iterating—repeating the loop until the output matches your expectation.

What I built in a couple of hours:

• Auth form
• Report generation & auto-filling
• Draft creation & approval workflow
• Aggregated data prepped for Looker analysis

Don't stop ask IT

--

You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/bb5593d9-daff-447a-bf47-2a7ddea29690n%40googlegroups.com.

[Joseph Vaughan]

are you remembering to issue "clasp push" after you've made changes?

Joseph

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/00b601dcb6ed%24a6b24e80%24f416eb80%24%40danhinsley.com.

[webs...@danhinsley.com]

Nope, didn’t know I need to do that, thanks.

 

My google scripts are all drive by google forms, is there a way to debug these in VS Code?

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/CAOjM3nS%3DOwaEiL%2BKjtyyJR8ZLxh4_yzFKjZ7CcQ4Rhbmbjxt3Q%40mail.gmail.com.

[Kildere S Irineu]

Boa tarde a todos,

Peço desculpas pela demora em responder.

Tenho dedicado um tempo para testar e refinar essa abordagem na prática.

Enquanto isso, para quem quiser explorar esse caminho, segue a documentação oficial do clasp, que é a base desse fluxo de trabalho:
https://developers.google.com/apps-script/guides/clasp?hl=pt-br

Agradeço novamente pela discussão e pelo interesse — em breve trago mais detalhes.

Atenciosamente,
Kildere Sobral Irineu

To view this discussion visit https://groups.google.com/d/msgid/google-apps-script-community/CAOjM3nS%3DOwaEiL%2BKjtyyJR8ZLxh4_yzFKjZ7CcQ4Rhbmbjxt3Q%40mail.gmail.com.

[Brett Grear]

You can also run clasp push -w then this will watch for changes and every save will push to cloud.