Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

A coworker created as Built in still cannot hand work on

Ouverte
  • Quelque chose ne va pas ?
#399 3 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.

  • #695 par @Harbor404 — fermée sans fusion

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
typescript
Domaine
backend-api-design

Piste de recherche

Lisez la conception différée dans #317 et le comportement décrit dans #331, puis examinez plugins/store.ts, en particulier les chemins agentRunsHere et managedConfiguration. Comparez l'option de stockage built_in sans endpoint avec la création d'un endpoint hop sur la surface de callback, et documentez le comportement choisi pour les déploiements avec un managed Bot existant et pour les collaborateurs déjà enregistrés en tant que remote_ag_ui.

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

Description

Tracking the design question #317 deferred on purpose, so it survives the PR that half-answers it.

From that PR's description:

A coworker created as "Built in" through the wizard is stored as remote_ag_ui pointed at the
managed endpoint. Its tool callbacks work (the deployment-token path), but the handoff tool is
minted only inside this deployment's own run loop, so such a coworker can be asked but cannot
itself hand work on. […] Fixing it properly means either storing endpoint-less creates as
built_in type, or adding a server-minted hop endpoint to the callback surface — worth its own PR
either way.

What #331 covers

#331 takes the first option, because the interview it adds cannot end by asking somebody for a URL.
store.create writes a built_in coworker running on its role description where there is neither
an endpoint nor a managed Bot — which on the one-container image the README recommends is every
coworker.

That buys back exactly what the note was about, in that case: agentRunsHere is
row.type === "built_in" (plugins/store.ts), and grantable on the handoff answer comes from it,
so a coworker created that way can be handed work on.

What is still open

Where the deployment does have a managed Bot, create still prefers managedConfiguration, the
row is still remote_ag_ui, and nothing changes: the coworker can be asked and cannot hand work on.
The wizard's "Built in" option is only offered on exactly those deployments, so the case #317
described is the case still outstanding.

Two ways out, both from the original note:

  1. Store endpoint-less creates as built_in even when a managed Bot exists. Smallest diff, and
    it makes "Built in" mean one thing everywhere rather than two things depending on configuration.
    The question is what happens to coworkers already stored the other way — they keep working, but
    the roster then holds both shapes with no way to tell them apart except the endpoint string.
  2. Mint a hop endpoint on the callback surface. Leaves storage alone and makes the handoff tool
    reachable from outside the run loop. Larger, and it puts a new server-minted address into a
    surface that currently only issues tokens.

Not proposing either — this is #317's question and the choice is its author's. Filing it so it does
not disappear when #331 merges and the no-managed-Bot half stops being visible.

Langage dominant
TypeScript
Étoiles
6.6k
Forks
914
Merge moyen
19 h 22 min
PR mergées (30 j)
140

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

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 CopilotKit/OpenBot

Toutes les issues de CopilotKit/OpenBot

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.