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

Aberta
  • Algo errado?
#4,897 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Pouca atividade
Stack de tecnologia
typescript
Domínio
ai

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
29.8k
Forks
3.9k
Merge médio
1h 44min
PRs com merge (30d)
841

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de simstudioai/sim

Todas as issues de simstudioai/sim

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.