Enhance call handling with state management and WebRTC integration by harshlocham · Pull Request #26 · harshlocham/agentmesh-ai

harshlocham · 2026-03-31T12:39:31Z

This pull request introduces the foundational backend and frontend logic for real-time call signaling and WebRTC integration, enabling audio/video call features in the chat application. The changes include new socket event handlers for call signaling on the server, a client-side Zustand call state store, custom React hooks for managing call state and signaling, and a WebRTC peer connection manager.

The most important changes are:

Backend: Call Signaling and State Management

Added comprehensive socket event handlers in call.handler.ts to support call initiation, offer/answer exchange, ICE candidate relay, call acceptance/rejection, ending, and reconnection, using user-specific rooms for targeted signaling. [1] [2]
Introduced new Redis key patterns and TTL constants in keys.ts for tracking call states and participants, laying groundwork for call lifecycle management and concurrency control.

Backend Integration

Registered the new callHandler in the socket server initialization to activate call signaling features. [1] [2]

Frontend: Call State Management

Implemented a Zustand-based call-store.ts to manage the local call state, including participants, call status, direction, media states, and error handling, with convenient selectors for UI logic.

Frontend: Call Signaling and WebRTC

Added useCallSignaling React hook for handling socket events and emitting signaling messages, integrating with the call store for state updates and error handling.
Added useCallState hook for easy access to call state and selectors from components.
Added PeerManager class and useWebRTC hook to encapsulate WebRTC peer connection logic, including ICE candidate handling, offer/answer flow, media stream management, and connection state changes. [1] [2]

…ser validation

…dation

…nts and state

…electors

…ction handling

…cipants

…ns and media streams

vercel · 2026-03-31T12:39:36Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chat-app	Ready	Preview, Comment	Apr 12, 2026 7:57am

Copilot

Pull request overview

Introduces foundational call signaling + WebRTC scaffolding to support audio/video calling in the chat app, including shared socket payload/types, a backend call signaling handler, and frontend state/hooks for signaling + peer connection management.

Changes:

Added shared socket event names and payload types for call lifecycle + signaling (offer/answer/ICE/accept/reject/end/state).
Registered a new socket callHandler and added Redis key/TTL primitives for call lifecycle tracking.
Implemented frontend call state (Zustand) plus hooks for call signaling and WebRTC peer connection management.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
packages/types/socket/payloads.ts	Adds call-related payload/type definitions shared across client/server.
packages/types/socket/events.ts	Adds call socket event constants + typed event maps.
packages/services/call.service.ts	Adds call state machine helpers (transitions/terminal states).
apps/web/store/call-store.ts	Introduces Zustand call store + selectors for UI state.
apps/web/lib/webrtc/peer-manager.ts	Adds a wrapper around RTCPeerConnection lifecycle and signaling helpers.
apps/web/hooks/useWebRTC.ts	Adds React hook integrating PeerManager + local/remote stream handling.
apps/web/hooks/useCallState.ts	Adds convenience hook to access call store state/selectors.
apps/web/hooks/useCallSignaling.ts	Adds hook to listen/emit call signaling socket events and update store.
apps/socket/server/socket/keys.ts	Adds Redis key patterns + TTL constants for call state primitives.
apps/socket/server/socket/index.ts	Registers `callHandler` on socket connection.
apps/socket/server/socket/handlers/call/call.handler.ts	Implements server-side call signaling relays using user-specific rooms.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-31T12:48:14Z

    socket.on(SocketEvents.CALL_OFFER, ({ to, offer }: CallOfferPayload) => {
-        io.to(to).emit(SocketEvents.CALL_OFFER, {
-            from: socket.data.userId,
+        const from = socket.data.userId;
+        if (!to) return;
+
+        io.to(userRoom(to)).emit(SocketEvents.CALL_OFFER, {
+            from,
            to,
            offer,
        });
    });


CALL_OFFER handler forwards only {from,to,offer} and drops call-scoping metadata already defined in CallOfferPayload (e.g., callId, conversationId, sdpRevision, deviceId). Without forwarding those fields, clients can’t reliably correlate offers when multiple calls/signaling sessions exist.

Copilot · 2026-03-31T12:48:15Z

    socket.on(SocketEvents.CALL_ANSWER, ({ to, answer }: CallAnswerPayload) => {
-        io.to(to).emit(SocketEvents.CALL_ANSWER, {
-            from: socket.data.userId,
+        const from = socket.data.userId;
+        if (!to) return;
+
+        io.to(userRoom(to)).emit(SocketEvents.CALL_ANSWER, {
+            from,
            to,
            answer,
        });
    });


CALL_ANSWER handler forwards only {from,to,answer} and drops CallAnswerPayload fields like callId/sdpRevision/deviceId. This makes the answer ambiguous in concurrent/overlapping calls and loses versioning hints; forward the relevant fields from the inbound payload.

Copilot · 2026-03-31T12:48:15Z

+    socket.on(SocketEvents.CALL_ICE_CANDIDATE, ({ to, candidate, callId }: CallIceCandidatePayload) => {
+        const from = socket.data.userId;
+        if (!to) return;
+
+        io.to(userRoom(to)).emit(SocketEvents.CALL_ICE_CANDIDATE, {
+            callId,
+            from,
+            to,
+            candidate,
+        });
+    });
+


CALL_ICE_CANDIDATE relay drops sequencing/indexing fields from CallIceCandidatePayload (candidateSeq, mid, mLineIndex). If clients rely on ordering or specific m-line targeting, this data loss can break ICE replay/reconnect flows; forward these optional fields when present.

Suggested change

socket.on(SocketEvents.CALL_ICE_CANDIDATE, ({ to, candidate, callId }: CallIceCandidatePayload) => {

const from = socket.data.userId;

if (!to) return;

io.to(userRoom(to)).emit(SocketEvents.CALL_ICE_CANDIDATE, {

callId,

from,

to,

candidate,

});

});

socket.on(

SocketEvents.CALL_ICE_CANDIDATE,

({

to,

candidate,

callId,

candidateSeq,

mid,

mLineIndex,

}: CallIceCandidatePayload) => {

const from = socket.data.userId;

if (!to) return;

io.to(userRoom(to)).emit(SocketEvents.CALL_ICE_CANDIDATE, {

callId,

from,

to,

candidate,

candidateSeq,

mid,

mLineIndex,

});

}

);

Copilot · 2026-03-31T12:48:15Z

    socket.on(SocketEvents.CALL_END, ({ to }: CallEndPayload) => {
-        io.to(to).emit(SocketEvents.CALL_END, {
-            from: socket.data.userId,
+        const from = socket.data.userId;
+        if (!to) return;
+
+        io.to(userRoom(to)).emit(SocketEvents.CALL_END, {
+            from,
            to,
        });
    });


CALL_END relay ignores optional CallEndPayload fields (callId, reason, endedAt) and emits only {from,to}. This prevents the receiver from validating which call ended and why; include the callId and propagate reason/timestamp when provided.

Copilot · 2026-03-31T12:48:16Z

    socket.on(SocketEvents.CALL_BUSY, ({ to }: CallRingingPayload) => {
-        io.to(to).emit(SocketEvents.CALL_BUSY, {
-            from: socket.data.userId,
+        const from = socket.data.userId;
+        if (!to) return;
+
+        io.to(userRoom(to)).emit(SocketEvents.CALL_BUSY, {
+            from,
+            to,
+        });
+    });


CALL_BUSY relay emits only {from,to} even though callId/conversationId can be present on CallRingingPayload. For correctness with overlapping calls, include callId (and conversationId if available) so the callee can associate the busy signal with the right call.

Copilot · 2026-03-31T12:48:16Z

+    socket.on(SocketEvents.CALL_RECONNECT, ({ to, callId }) => {
+        const from = socket.data.userId;
+        if (!to) return;
+
+        io.to(userRoom(to)).emit(SocketEvents.CALL_RECONNECT, {
+            callId,
+            from,
            to,
        });
    });


CALL_RECONNECT relay drops CallReconnectPayload fields like lastSeenSeq and iceRestartRequired. Those are typically needed to decide whether to resend buffered candidates/SDP or trigger an ICE restart; forward them (and validate callId) to support reconnection semantics.

Copilot · 2026-03-31T12:48:16Z

+    socket.on(
+        SocketEvents.CALL_OFFER_INIT,
+        ({ callId, conversationId, to, callType }: CallOfferInitPayload) => {
+            const from = socket.data.userId;
+            if (!to) return;
+
+            io.to(userRoom(to)).emit(SocketEvents.CALL_RINGING, {
+                callId,
+                conversationId,
+                from,
+                to,
+            });
+
+            const statePayload: CallStatePayload = {
+                callId,
+                conversationId,
+                status: "ringing",
+                participants: [{ userId: from }, { userId: to }],
+                serverTs: new Date(),
+            };
+
+            io.to(userRoom(from)).emit(SocketEvents.CALL_STATE, statePayload);
+            io.to(userRoom(to)).emit(SocketEvents.CALL_STATE, statePayload);
+
+            io.to(userRoom(to)).emit(SocketEvents.CALL_OFFER_INIT, {
+                callId,
+                conversationId,
+                from,
+                to,
+                callType,
+            });
+        }


CALL_OFFER_INIT currently emits both CALL_RINGING and CALL_OFFER_INIT to the callee with overlapping data, plus CALL_STATE to both sides. This duplication increases the chance of double-notifications and diverging client behavior; consider consolidating to a single “incoming call” event (or clearly separating responsibilities/payloads).

Copilot · 2026-03-31T12:48:16Z

+    useEffect(() => {
+        const onRinging = (payload: CallOfferInitPayload) => {
+            setIncomingCall({
+                callId: payload.callId,
+                conversationId: payload.conversationId,
+                callType: payload.callType,
+                participants: [{ userId: payload.from }, { userId: payload.to }],
+            });
+        };


The incoming-call handler is named onRinging but is wired to SocketEvents.CALL_OFFER_INIT (not CALL_RINGING). Given both events exist, this is easy to misread/maintain; either subscribe to CALL_RINGING (and use CallRingingPayload) or rename the handler/event usage to match intent.

Copilot · 2026-03-31T12:48:17Z

+        const onCallAccepted = () => {
+            stopRingtone();
+            setStatus("accepted");
+        };
+
+        const onCallRejected = () => {
+            stopRingtone();
+            setStatus("rejected");
+        };
+
+        const onCallEnded = () => {
+            endCall();
+        };


CALL_ACCEPT / CALL_REJECT / CALL_END handlers update global call state without checking which call the event belongs to (payload includes callId). If a user can receive stale/overlapping events, this can incorrectly flip the UI state; gate the updates by comparing payload.callId to the current store callId.

Copilot · 2026-03-31T12:48:17Z

+export enum CallState {
+    INITIATED = "initiated",
+    RINGING = "ringing",
+    ACCEPTED = "accepted",
+    ACTIVE = "active",
+    RECONNECTING = "reconnecting",
+    ENDED = "ended",
+    REJECTED = "rejected",
+    MISSED = "missed",
+    FAILED = "failed",
+}


packages/types defines a CallState string union, while packages/services exports a CallState enum with the same exported name but similar values. This naming collision makes cross-package imports ambiguous and error-prone; consider renaming the enum (e.g., CallLifecycleState) or re-exporting/deriving it from the shared @chat/types CallState.

…and session management

…cation security

…code

…es; extend tsconfig from expo

…le function

…nativewind types

…ement

…d integrating API validation

…payload handling

…son and package-lock.json

…horization header methods

…ependencies

…services packages

…rtifact management

…ng across shared packages

- Added new `RELEASES.md` file to document the release architecture and CI/CD workflow responsibilities. - Updated `.changeset/config.json` to ignore specific packages during versioning. - Enhanced `deploy.yml` to support manual promotion of releases with new inputs for `release_tag` and `deploy_target`. - Modified `release.yml` to compute and output the short SHA of the release commit for better tracking.

- Updated `deploy.yml` to support manual promotion of releases with new inputs for `release_tag` and `deploy_target`. - Improved deployment logic to handle both automatic and manual triggers, ensuring proper metadata resolution. - Enhanced `RELEASES.md` to document the new manual promotion process and health check configurations. - Added rollback triggers and notification features for production deployments.

…dcasting

- Removed debug logging from the socket handshake authentication process. - Enhanced the `getClientSocketUrl` function to provide a default local socket URL and handle various local development scenarios. - Updated the chat store to use a consistent `idOf` function for conversation identification, improving code clarity and maintainability. - Added unit tests for the `getClientSocketUrl` function to ensure correct behavior in different environments.

…pts in package.json for direct execution

…d streamline image domain configuration

- Added Prettier and related plugins to improve code formatting. - Updated Next.js version in package.json and adjusted build commands in vercel.json for consistency. - Refactored scripts in web's package.json for direct execution of Next.js commands. - Cleaned up next.config.ts by removing unnecessary environment loading logic.

…age-lock.json

…age.json and package-lock.json

harshlocham added 8 commits March 31, 2026 17:29

feat(call): enhance call handling with additional event support and u…

297fcec

…ser validation

feat(call): implement call state management with transitions and vali…

705836d

…dation

feat(call): add useCallSignaling hook for managing call signaling eve…

8240340

…nts and state

feat(call): implement useCallState hook for managing call state and s…

cd3f796

…electors

feat(call): integrate call handling with new event types and payloads

c4e090b

feat(peer-manager): implement PeerManager class for WebRTC peer conne…

ed6a63b

…ction handling

feat(call-store): add Zustand store for managing call state and parti…

cbcfac6

…cipants

feat(webhook): implement useWebRTC hook for managing WebRTC connectio…

d256bef

…ns and media streams

Copilot AI review requested due to automatic review settings March 31, 2026 12:39

Copilot AI reviewed Mar 31, 2026

View reviewed changes

harshlocham added 19 commits April 12, 2026 13:25

Add MIT License to the project

77fa601

feat(auth): return tokens in login response for mobile support

6ea2f50

feat(auth): return JSON response with tokens on successful refresh

34485c9

Get started with Expo

1ea6b93

feat(auth): implement mobile authentication flow with login, logout, …

889a135

…and session management

chore: update code structure for better readability and maintainability

8935bb5

feat(auth): add expo-secure-store plugin for enhanced mobile authenti…

73578c0

…cation security

fix(package): add missing newline at end of file in package.json

c80f7e6

refactor(auth): remove obsolete authentication and socket management …

1364f78

…code

chore: update package.json to add mobile script and set react overrid…

0f0cbf0

…es; extend tsconfig from expo

refactor(env): consolidate environment variable retrieval into a sing…

aa549ed

…le function

fix(package): add missing newline at end of mobile package.json

dc3b259

fix: add react-native-gesture-handler import and update tsconfig for …

3a57382

…nativewind types

feat: implement mobile authentication flow with login and token manag…

4c577b2

…ement

feat: refactor authentication flow by simplifying state management an…

91eb577

…d integrating API validation

fix(auth): improve user retrieval logic in login function for better …

dbe04fc

…payload handling

fix(deps): downgrade axios version from 1.14.0 to 1.13.0 in package.j…

039f80a

…son and package-lock.json

feat(auth): enhance token retrieval by supporting both cookie and aut…

7927b97

…horization header methods

feat(deps): add @react-native-async-storage/async-storage to mobile d…

b6278a6

…ependencies

harshlocham and others added 28 commits April 12, 2026 13:25

feat(build): add build scripts and tsconfig files for db, redis, and …

f625ddc

…services packages

feat(turbo): enhance build outputs and add clean scripts for better a…

88c7c69

…rtifact management

feat(dependencies): add nodemailer for email handling in the web app

6381fd3

feat(auth): add TypeScript build configuration and update build script

8e1d7e4

feat(auth): enhance mobile authentication and standardize build tooli…

f26a317

…ng across shared packages

Version Packages

1981870

Add conversation created event and payload to socket events

a4c9537

Add conversation created endpoint and payload

8264ed8

Add upsertConversation method and enhance conversation sorting logic

dd1c5bd

Enhance conversation creation flow and add internal socket event broa…

61f6785

…dcasting

Update axios version and increment package versions in package-lock.json

e4d3785

Enhance POST response to include access and refresh tokens

9660a80

Fix realtime message delivery and improve authentication infrastructure

3a06560

Update Next.js to version 16.2.3 and add related dependencies

33c33bf

Update .npmrc to use hoisted install strategy and modify Next.js scri…

c7b6677

…pts in package.json for direct execution

Refactor next.config.ts to use process.cwd() for current directory an…

ff2a9ac

…d streamline image domain configuration

Fix type definition for Button component props to exclude ref

39ebcb5

Version Packages

9810d2f

fix: unblock vercel build and workflow validation

9d09948

fix(auth): include jsonwebtoken types in production install

cf96041

feat: add PostCSS configuration with Tailwind CSS plugin

3b726aa

fix: restore @tailwindcss/postcss dependency in package.json and pack…

0f21c0b

…age-lock.json

fix: restore tailwindcss and tailwindcss-animate dependencies in pack…

81208f5

…age.json and package-lock.json

ci: simplify release workflow with changesets metadata

676c5e6

vercel Bot deployed to Preview April 12, 2026 07:57 View deployment

harshlocham self-assigned this Apr 19, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Enhance call handling with state management and WebRTC integration#26

Enhance call handling with state management and WebRTC integration#26
harshlocham wants to merge 122 commits into
mainfrom
feat/WebRTC

harshlocham commented Mar 31, 2026

Uh oh!

vercel Bot commented Mar 31, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Copilot AI Mar 31, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

harshlocham commented Mar 31, 2026

Uh oh!

vercel Bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 31, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vercel Bot commented Mar 31, 2026 •

edited

Loading