# Reported issues for flow-nexus

Pod holds 14 of 14 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [flow-nexus](/mcp/flow-nexus).

## Most discussed

### 🎨 CLI-MCP Feature Parity: Challenge System Works via MCP but CLI Interface Blocks User Access

# 🚨 **REGRESSION BUG REPORT**

## **Issue Summary**
Issue #4 was marked as resolved in v0.1.64, but the **exact same UUID validation error still exists** in current versions v0.1.111+. Additionally, discovered multiple related bugs and version distribution problems.

## **Environment**
- **Tested Version**: v0.1.111 (installed via `npm install -g flow-nexus`)
- **Platform**: macOS (Darwin 24.6.0)
- **Node Version**: Latest
- **Account**: Authenticated (michael@oboyle.co, 237 rUv credits)

## **🐛

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/45) · 2025-09-07 · open · external user · 4 comments

### Beta testing in Codespace after Repo forking

I am locally on a Mac. I am running a Github Codespace. I forked the repo and followed the instructions for a 60 seconds init sequence (but did not select a template or operation mode). I just went straight to authenticate. Yesterday I was able to init but, when I tried to authenticate I got this return from register: "[1] 6857
bash: ^ztNPm3: command not found." Today I tried again. This time it initialized again successfully, with indications that some dependencies were deprecated and suggested

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/36) · 2025-08-31 · open · external user · 1 comment

### No Rate Limiting on Resource Creation

## Description
No rate limiting implemented for resource-intensive operations like sandbox creation.

## Steps to Reproduce
1. Create multiple sandboxes in rapid succession
2. All are accepted without throttling
3. No rate limit errors or delays

## Expected Behavior
Rate limiting to prevent abuse and resource exhaustion

## Actual Behavior
Unlimited resource creation allowed

## Impact
- Potential DoS vulnerability
- Resource exhaustion possible
- No protection against automation abuse

## Envi

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/31) · 2025-08-30 · closed · external user · 1 comment

### Boundary Conditions Ignored in Swarm Creation

## Description
Setting boundary values like maxAgents: 0 doesn't produce expected behavior or errors.

## Steps to Reproduce
1. Call `swarm_init` with maxAgents: 0
2. Observe it creates default configuration instead

## Expected Behavior
Either:
- Minimum validation (reject 0)
- Create swarm with 0 agents if valid
- Clear error message

## Actual Behavior
Ignores input, uses defaults, charges unexpected credits

## Impact
Confusing behavior for users, unpredictable credit charges

## Environment

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/30) · 2025-08-30 · closed · external user · 1 comment

### Swarms Don't Persist After Creation

## Description
Successfully created swarms that charge credits don't appear in swarm_list and can't be queried.

## Steps to Reproduce
1. Call `swarm_init` (returns success with swarm_id)
2. Note credits are deducted
3. Call `swarm_list` with status: "active"
4. Returns empty array
5. Call `swarm_status` with the swarm_id
6. Returns "Swarm not found"

## Expected Behavior
Created swarms should persist and be retrievable via list/status endpoints

## Actual Behavior
Swarms vanish immediately afte

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/29) · 2025-08-30 · closed · external user · 1 comment

### No Input Validation Causes Excessive Credit Charges

## Description
Swarm creation accepts invalid parameters and charges incorrect credit amounts based on invalid input.

## Steps to Reproduce
1. Call `swarm_init` with maxAgents: 0
2. System creates 8-agent swarm, charges 19 credits
3. Call `swarm_init` with maxAgents: 1000
4. System accepts it, charges 2003 credits

## Expected Behavior
- Validate maxAgents range (1-100)
- Reject invalid topology/strategy values
- Return error for out-of-range inputs

## Actual Behavior
- Zero agents creates def

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/28) · 2025-08-30 · closed · external user · 1 comment

### Unlimited Credit Exploit via app_store_earn_ruv

## Description
The `app_store_earn_ruv` function allows any authenticated user to grant themselves unlimited rUv credits without authorization checks.

## Steps to Reproduce
1. Authenticate with any valid user account
2. Call `app_store_earn_ruv` with amount: 10000
3. Credits are immediately added to balance

## Expected Behavior
Function should require admin authorization or valid trigger (challenge completion, purchase, etc.)

## Actual Behavior
Any user can add any amount of credits to their 

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/26) · 2025-08-30 · closed · external user · 1 comment

### 🚨 Comprehensive Testing Report - Multiple Critical Issues Found

# 🚨 Flow Nexus Command Testing Report

## 📋 Test Summary
Comprehensive testing of flow-nexus commands revealed multiple critical issues affecting core functionality. This epic documents all unexpected outcomes discovered during systematic testing.

## 🔴 Critical Issues (Blockers)

### 1️⃣ Authentication System Broken - Email Confirmation Loop
**🐛 Unexpected Outcome**: Users cannot login even with valid credentials
**📝 Steps to Reproduce**:
1. Call `mcp__flow-nexus__user_login`
2. Provide valid e

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/5) · 2025-08-27 · closed · external user · 2 comments

## Most recent

### PostgreSQL Error: SQLSTATE 3D000/42P01 relation does not exist

### Summary

Queries against the Flow Nexus backend fail with a PostgreSQL error:

```
SQLSTATE 3D000/42P01 — relation does not exist
```

`SQLSTATE 42P01` (`undefined_table`) / catalog `3D000` (`invalid_catalog_name`) means the query referenced a relation (table/view) or schema that does not exist in the connected database.

### Core finding: system_health reports a false positive

The more important issue is that health monitoring does not catch this. Concurrently with the failing query, the `

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/54) · 2026-08-29 · open · external user · 0 comments

### MCP tool `user_reset_password` returns "not implemented" despite being listed with a schema

### Reproduce

1. Start the MCP server: `flow-nexus mcp start`
2. `tools/list` includes `user_reset_password` with a complete schema:
   `{"email": {"type": "string", "description": "User email"}}` , required: `[email]`
3. Call it:

```
Error executing user_reset_password: Tool 'user_reset_password' not implemented
```

### Impact

Combined with Issue 1, there is **no password-reset path in either the CLI or
the MCP surface** — recovery is web-UI only. Neither surface says so.

More generally: a

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/52) · 2026-07-28 · open · external user · 0 comments

### fix: Deprecated Anthropic model IDs cause Seraphina chat to fail (404)

## Bug Report

**Package version:** 0.1.128
**Affected feature:** `seraphina_chat` MCP tool

## Description

Seraphina chat is completely broken. The backend Supabase Edge Function calls Anthropic with deprecated model IDs that return 404.

## Error

```
404 {"type":"error","error":{"type":"not_found_error","message":"model: claude-3-5-sonnet-20241022"}}
```

The MCP tool `seraphina_chat` returns:
```json
{
  "error": "The Queen's court is in disarray. Please seek audience later.",
  "details": 

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/50) · 2026-03-28 · open · external user · 0 comments

### MCP Server stdout pollution prevents JSON-RPC communication

## Issue Description

The `flow-nexus` MCP server outputs logging messages on stdout, which prevents proper JSON-RPC communication with MCP clients.

## Problem

When running `npx flow-nexus mcp`, the server outputs various logs to stdout:

```
╔════════════════════════════════════════════════════════╗
║  >_ Flow Nexus - AI-Powered Swarm Intelligence         ║
║  Version: 0.1.128                                      ║
╚════════════════════════════════════════════════════════╝

[INFO] MCP server 

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/49) · 2025-10-17 · open · external user · 0 comments

### MCP server outputs non-JSON to stdout, breaking Claude Desktop integration

## GitHub Issue Content

**Title:** MCP server outputs non-JSON to stdout, breaking Claude Desktop integration

**Body:**

### Description
The Flow Nexus MCP server outputs non-JSON text to stdout after establishing the initial JSON-RPC connection, causing Claude Desktop to fail with a JSON parsing error. The server appears to output E2B initialization messages directly to stdout instead of stderr.

### Error
```
Unexpected token 'E', "E2B Templa"... is not valid JSON
```

### Expected Behavior

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/42) · 2025-09-03 · open · external user · 0 comments

### Beta Testing Session 2: No Fixes Deployed + Critical Security Vulnerabilities Found

# Beta Testing Session 2: No Fixes Deployed + Critical Security Vulnerabilities Found

## Context
**Date**: August 31, 2025  
**Session**: Beta Testing Session 2  
**Tester**: @proffesor-for-testing (Dragan Spiridonov, VP Quality Engineering - Forge-Quality)  
**Duration**: ~13 minutes active testing  
**Previous Issue**: [Session 1 findings - 23 bugs reported]

## Summary

Following up on yesterday's testing session, during which 23 bugs were identified and reportedly fixed within 24 hours, I c

[Read the thread](https://github.com/ruvnet/flow-nexus/issues/35) · 2025-08-31 · closed · external user · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/ruvnet/flow-nexus/issues).