ruvnet/ruflo · error · TeammateError

REMOTE_SYNC_FAILED

REMOTE_SYNC_FAILED

Error message

Team ${teamName} is not connected to remote

What it means

syncWithRemote() found team.remoteSessionId is unset, meaning pushToRemote() was never called (or the session was cleared) for this team. The team has no established remote session to synchronize with, so the sync operation is refused up front.

Source

Thrown at v3/plugins/teammate-plugin/src/teammate-bridge.ts:1667

      JSON.stringify(remoteSession, null, 2),
      { encoding: 'utf-8', mode: 0o600 }
    );

    this.emit('remote:pushed', { team: teamName, remoteUrl: remoteSession.remoteSessionUrl });

    return remoteSession;
  }

  /**
   * Sync with remote
   */
  async syncWithRemote(teamName: string): Promise<SyncResult> {
    this.ensureAvailable();

    const team = this.getTeamOrThrow(teamName);

    if (!team.remoteSessionId) {
      throw new TeammateError(
        `Team ${teamName} is not connected to remote`,
        TeammateErrorCode.REMOTE_SYNC_FAILED,
        teamName
      );
    }

    // Simulate sync result
    const result: SyncResult = {
      success: true,
      changesPushed: 0,
      changesPulled: 0,
      conflicts: 0,
      remoteUrl: team.remoteSessionUrl,
    };

    this.emit('remote:synced', { team: teamName, result });

    return result;

View on GitHub (pinned to fa13ee4ad6)

Solutions

1. Connect the team to the remote before performing remote operations.

When it happens

Trigger: Thrown at v3/plugins/teammate-plugin/src/teammate-bridge.ts:1667 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18). Data as JSON: /api/errors/69e1733387d25338. Report an issue: GitHub.