ruvnet/ruflo · error · QECoreError
Failed to list agents
Error message
Failed to list agents
What it means
QECoreBridge.listAgents caught a failure from the underlying agent-list call and rethrew as QECoreError. The agent service could not enumerate agents (service down, auth, or transport issue); the optional type/status filter is not the fault.
Source
Thrown at v3/plugins/agentic-qe/src/bridges/QECoreBridge.ts:365
/**
* List available agents by type
*/
async listAgents(filter?: { type?: string; status?: string }): Promise<AgentHandle[]> {
try {
this.logger.debug(`Listing agents with filter: ${JSON.stringify(filter)}`);
const agents = await this.agents.list({
type: filter?.type,
status: filter?.status,
});
// Filter to only QE agents
const qeAgents = agents.filter((a) => a.type.startsWith('qe-'));
return qeAgents.map((agent) => new AgentHandleImpl(agent, this.agents, this.logger));
} catch (error) {
this.logger.error('Failed to list agents', error);
throw new QECoreError('Failed to list agents', error as Error);
}
}
/**
* Get agent by ID
*/
async getAgent(agentId: string): Promise<AgentHandle | null> {
try {
// Check active handles first
const activeHandle = this.activeHandles.get(agentId);
if (activeHandle && 'type' in activeHandle) {
return activeHandle as AgentHandle;
}
const agent = await this.agents.get(agentId);
if (!agent) return null;
return new AgentHandleImpl(agent, this.agents, this.logger);View on GitHub (pinned to fa13ee4ad6)
Solutions
- Verify the core bridge connection before listing agents.
- Inspect the underlying error for the list operation.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at v3/plugins/agentic-qe/src/bridges/QECoreBridge.ts:365 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/835d50d2d5c07f5e.
Report an issue: GitHub.