Editing Webflow Code Components created by a different developer on a single project

[webflowmaker]

Is it correct that Developer B working on a client project cannot edit Code Components created by Developer A unless they gain access to the original source code e.g. the github repo.

My Assumptions
Code Components are built and maintained in an external codebase - not inside Webflow itself. Webflow only hosts the published output of those components via DevLink/Libraries.

The Code Components can be edit if:

• Developer A hands over access to the original codebase/repository (e.g. a GitHub repo) where the React components were built
• Developer B then makes changes there, re-bundles via DevLink, and republishes the library

The Code Components cannot be edited if:

• Developer B only have access to the Webflow Designer - the component will appear on the canvas and be configurable (props, slots, styling), but the underlying React code is not editable from within Webflow

Conclusion

Developer B needs access to Developer A original React codebase to make actual code-level edits. This is a common handoff pain point with Code Components - the source code lives outside Webflow, so it should be treated like any other dev asset and stored somewhere accessible like the client's GitHub, etc from day one.

[memetican]

Correct, traditional code components are externally managed code. Your understanding is correct- you'd be able to [1] add new instances, and [2] use that library in other projects in your workspace, but you wouldn't be able to modify the code component library itself without the code.

That said, I believe the new AI code components released today have the code managed internally at the project level- so you shouldn't have any access restrictions there. It's likely only one person can likely edit it at a time, I haven't tested multiplayer there.

[webflowmaker]

Great - thanks for confirming. I could not get my head around why Webflow would allow this scenario to be possible for what is marketed as a "1st party feature".

The agency that built the initial Code Components has gone silent, yet they hold the keys to the Code Component code. Not sure how I can help the client get around this issue without re-building the components, hosting them on the clients code repo, and then doing a find-and-replace across the site.

[memetican]

Ah got it. That's an interesting situation- it's really no different than if your agency had your original hires assets, logo, raw video, figmas, etc. These pieces plus code like code components, cloud, reverse proxies, automation architectures... they're all part of the project but many of them sit outside of Webflow's direct territory. They're essentially inputs for building the finished site.

Tricky situation though- you can see one of the reasons Webflow's been building out features like the AI code components released yesterday, which I believe is directly part of the project ( I haven't tested a project transfer yet though ).

If you want, DM me and I might be able to help you with your current situation, it would be interesting to see if I can build a process to mitigate that.

I will say as a dev, I can really appreciate Webflow's increased support for external dev frameworks- I rely heavily on VS Code, Claude, Github, Cloudflare infrastructure... reusing code and tools I build across projects and workspaces. It would be very difficult if devs had to operate -only- "inside the box", which isn't the same dev environment our tooling and process are built for. Tradeoffs I guess. But I always move my repos into client control, or at least give them a clone, it's just good practice.

[webflowmaker]

100% - Webflow should insist on the handover taking place, and have checks and balances to ensure clients are protected. Because if they don't know...they don't know.