u/Fresh-Daikon-9408

The next focus is not “more magic”.

It’s making the whole thing sturdier.

What has been released:

• better GitOps foundations
• cleaner environment configs
• easier sharing across teams
• workflow promotion from one environment to another
• a much improved agent workbench
• checkpoints with Git-based rollback
• Git worktree support

The goal is simple:

Build in your IDE. Track everything in Git. Work across local / staging / production. Let the agent help, without losing control.

n8n-as-code is slowly becoming what I wanted it to be from the start:

a proper engineering layer for n8n.

Not a black box. Not a prompt-to-workflow toy. Just workflows, environments, Git, and an agent that actually understands the project.

https://github.com/EtienneLescot/n8n-as-code

Hi everyone,

Quick update on n8n-as-code V2.

The V2 release introduced a lot of changes around instance management, authentication, VS Code integration and workspace configuration.

Some of it was necessary for the long-term direction of the project, but the migration was clearly too disruptive for some existing users.

The main issue was this:

n8n-as-code should not only store workflows as files.

The project itself should behave like a codebase:

• clone the repo
• share the non-secret config
• keep secrets out of Git
• work against dev / staging / prod instances
• let other team members reproduce the setup

With the first V2 model, part of that experience moved too far into global configuration.

That was not aligned with the original “as-code” promise.

I pushed a fix in PR #409 and merged it into @next.

The new model is:

• global instances are mainly for managed instances
• workspace environments are back as first-class config
• environments can point to dev / staging / prod
• workspace config can live with the repository
• secrets stay outside Git
• CLI and VS Code should now follow the same model
• migration scripts are included to help existing users move forward

This was partly a fix, partly a migration improvement, and partly an architectural rollback.

The goal is to keep the new V2 features, but make the transition much closer to how people actually use n8n-as-code in real projects.

If you are using n8n-as-code with multiple n8n instances, team repos, or dev/prod workflows, I’d really appreciate feedback on the @next version before I push this further.

Especially interested in:

• does the new workspace environment model make sense?
• is the migration clear enough?
• does it work better for team setups?
• are there still cases where config should live in the repo but currently does not?

Thanks again to everyone who reported the migration issues clearly. That feedback was very useful.

I just released n8n-as-code V2.

Repo: https://github.com/EtienneLescot/n8n-as-code

Big changes:

• Integrated agent in VS Code
• Workflow-aware context Select a workflow or a node, then ask the agent to explain, edit, debug, or improve it.
• Create → explain → execute The agent is not limited to generating JSON. It can work from the actual workflow context.
• n8n-manager Manage local / staging / prod n8n instances from the editor.
• Workspace binding Attach a project to a specific n8n instance.
• Provider/model management Configure OpenRouter, OpenAI OAuth, Mistral, etc. from the extension.
• Open source / MIT

The goal is simple:

give coding agents n8n superpowers without replacing n8n.

Workflows stay inspectable, executable, and versionable.

Feedback very welcome from people building real n8n workflows.

Hi r/n8n,

I’m opening the n8n-as-code V2 pre-release for community testing.

This is not the official V2 launch announcement yet. I’m sharing it early because the new version changes a big part of the experience, and I’d like feedback from real n8n users before calling it stable.

The main new feature: you can now manage n8n instances directly through n8n-manager.

In practice, you can test:

• Creating a managed local n8n instance from the editor or agent
• Connecting an existing n8n Cloud or self-hosted instance
• Starting, stopping, and restarting local managed instances
• Managing public URLs for webhook, form, and chat trigger testing
• Selecting projects and pinning instances per workspace
• Keeping API keys and runtime config outside the project files
• Using the existing Git-style workflow: pull, edit locally, validate, push

The goal is to make n8n workflow development more local-first and developer-friendly, especially for people using VS Code, Cursor, Git, and AI coding agents.

I’m especially looking for feedback on:

• First-time setup
• Docker-managed local n8n instances
• Public URL/tunnel behavior
• Multi-instance workflows
• Project selection
• Anything confusing in the VS Code/Cursor UI

Links:

• VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=etienne-lescot.n8n-as-code
• GitHub: https://github.com/EtienneLescot/n8n-as-code

This is an independent community project and is not affiliated with, endorsed by, or sponsored by n8n.

If you try it, issues and feedback are very welcome. A separate official V2 release post will come later once the pre-release has had more testing.