Zed, iroh and WorkOS: NYC Developer Happy Hour October 13

The Zed, iroh and WorkOS Happy Hour will bring developers together in New York on October 13, 2026, from 5:30 to 9:30pm EDT. The organizers welcome laptops and demonstrations, with food, drinks and tables for working through ideas. They explicitly describe an evening without talks.

That format gives the gathering a clear purpose: compare what is working in AI-assisted development, including how people and agents can collaborate on existing devices. Registration is subject to host approval, and the precise venue is disclosed through registration. Readers should use the official page for access rather than assuming the address or a confirmed place.

About the developer gathering

The event is presented by Zed, with iroh in the title and n0 named in the description alongside WorkOS. Its listed hosts include Esther Trapadoux, Rae, b5, ramfox, Emma Elliott and WorkOS. Those display names are preserved as supplied; an abbreviated name or handle is not expanded into an unverified identity.

The absence of a formal talk program makes a demonstration a natural starting point for conversation. A builder can show an example, explain a constraint and invite another person to examine the result. That is a different exchange from a presentation in which the audience mainly hears the conclusion.

A useful preparation would be a bounded workflow that can be understood quickly. Explain the desired behavior, identify the part that has been tested and make clear where the uncertainty remains. These are editorial suggestions for using the format, rather than additions to the organizers' agenda.

The official listing does not name speakers, announce a joint product or publish a current ticket price. It also withholds the exact New York location until registration. Coverage should preserve those limits, even when additional data might exist behind an event platform's page.

Three technical perspectives in one conversation

Zed describes its product as a code editor designed for speed and collaboration with humans and AI. Its current site discusses agentic editing and ways for developers to follow and review an agent's work. That supplies a concrete context for asking what collaboration looks like inside an actual development environment.

Iroh focuses on peer-to-peer connectivity for apps, agents and workflows. Its official site describes direct connections when possible and encrypted relay forwarding when a direct path is unavailable. Those are product characteristics, not a claim that every demonstration at the happy hour will use that architecture.

WorkOS supplies enterprise software building blocks, including authentication, single sign-on and access-related capabilities. Its involvement brings another relevant dimension to the discussion: a connected system needs a way to determine what a user or agent is permitted to do. The event itself does not announce a specific implementation combining the three products.

Taken together, these perspectives invite a discussion that moves between the development environment, connectivity and access. A team considering that combination still has to examine its own application, infrastructure and responsibilities. Sharing a room creates an opportunity to ask the questions, rather than a ready-made architecture.

What to look for in a demonstration

A demonstration becomes more useful when it makes the constraint visible. What happens when a connection is unavailable, when an agent makes a change that needs review, or when someone lacks permission to complete a step? Showing one of those conditions can produce a more informative conversation than a smooth path alone.

The organizers ask how agents and humans can work together on devices without sending everything to the cloud. That is an open technical question in the event description, not a blanket instruction to avoid cloud services. Different workloads will place different demands on connection, computation, data handling and operational support.

A builder can use the evening to compare those demands with another person's experience. The important distinction is between what a prototype demonstrates and what a team has established through broader testing. An example may reveal a useful direction while leaving deployment decisions unresolved.

That makes careful language part of the technical work. Saying what has been tested, what remains uncertain and what would need to change in a production environment gives another developer a basis for responding. The result may be a better experiment or a sharper requirement, without any need to turn a community exchange into a sales presentation.

Why the local format matters

An after-work gathering allows people to bring work that sits between a polished announcement and a private debugging session. The promised tables and welcome for laptops support that kind of exchange, while the lack of talks leaves space for participants to decide which examples deserve attention. No outcome or guest roster is guaranteed.

For engineering leaders, the useful lens is the decision a conversation might clarify. Where does the team need a better review process? Which connection assumptions are fragile? What access boundary needs to become explicit before an agent is trusted with another task?

DevCuration's Secure Software Factory Show and Tell coverage records another event on October 13 with a related but distinct security focus. It is a separate program, with its own hosts and registration conditions; readers should evaluate the formats individually.

The Zed, iroh and WorkOS gathering makes room for developers to discuss implementation while they can still point to the work. For someone approved to attend, the strongest contribution may be a modest example explained precisely enough that another person can help move it forward.