Feature Request: More Flexible Router Block (Multi-Route Selection & Custom System Prompt)

Ouverte
  • Quelque chose ne va pas ?
#4,897 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
30/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Calme
Stack technique
typescript
Domaine
ai

Piste de recherche

No files, tests, or code entry points are named. Start by locating the Router block implementation and its existing single-route behavior, then determine how the requested routing modes, custom prompt, no-match handling, and confidence outputs fit together. Done would require an agreed, backward-compatible scope for these changes.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

feature

Problem

The current Router block is useful for AI-powered routing, but it appears to be limited to selecting a single route and relies on a hidden internal system prompt. This makes the block less flexible for advanced workflows and prevents users from adapting the routing behavior to different use cases.

In many real-world scenarios, a single input may legitimately belong to multiple categories. For example:

  • A support ticket may involve both Billing and Technical issues.
  • User feedback may contain both a Bug Report and Product Feedback.
  • A lead may qualify for multiple downstream workflows.

Currently, the Router seems designed around single-route classification, which limits these use cases.

Proposed Improvements

1. Route Selection Mode

Add a configurable routing mode with options such as:

Single Route (Current Behavior)

  • Select exactly one best-matching route.
  • Backward compatible with existing workflows.

Multiple Routes

  • Allow the model to select multiple matching routes.
  • Output an array of selected routes instead of a single value.
  • Trigger multiple output ports simultaneously.

Example:

Input:
"Billing charges are incorrect and the API is returning errors."

Selected Routes:

  • Billing
  • Technical
2. Custom System Prompt

Expose the Router's system prompt as an optional advanced setting.

Example use cases:

  • Adjust routing strictness.
  • Allow multi-label classification.
  • Prioritize specific business rules.
  • Customize fallback behavior.
  • Define confidence thresholds.
  • Improve domain-specific routing.

Example:

"You may select multiple routes if the input clearly belongs to more than one category."

or

"Prefer the most specific route instead of the most general route."

This would significantly increase flexibility without affecting users who prefer the default behavior.

3. Configurable No-Match Behavior

Allow users to choose between:

  • Route to Error Path
  • Force Best Match
  • Return Multiple Candidates
  • Use Custom Fallback Route
4. Confidence Score Output

Provide an optional confidence score for each routing decision.

Example outputs:

  • selectedRoute
  • selectedRoutes
  • confidence
  • reasoning

This would help with debugging and workflow monitoring.

Benefits

  • Supports both single-label and multi-label classification.
  • Works better for complex enterprise workflows.
  • Gives users more control over routing behavior.
  • Reduces the need for custom LLM blocks before the Router.
  • Makes the Router adaptable to a wider range of use cases.

Summary

The Router block would become significantly more powerful by supporting:

  1. Single-route and multi-route modes.
  2. User-configurable system prompts.
  3. Configurable no-match behavior.
  4. Confidence score outputs.

These changes would preserve backward compatibility while providing much greater flexibility for advanced workflow design.

Langage dominant
TypeScript
Étoiles
29.8k
Forks
3.9k
Merge moyen
1 h 44 min
PR mergées (30 j)
841

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de simstudioai/sim

Toutes les issues de simstudioai/sim

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.