Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Docs: cover creating a BYO Harness in the UI for kagent 1.x

Abierto
  • ¿Algo no está bien?
#539 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Área
documentation, frontend

Línea de trabajo

Read agents/bring-your-own-agent.md end to end, then check agents/agent-harness.md for the workload.command guidance. Build the fixture with make build-byo-a2a and use its digest to verify the UI flow, disabled Create state, optional model warning, Harnesses runtime, and agent response. Update the documentation and screenshots when every checklist item is confirmed against a real BYO image.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

help wanted

[!IMPORTANT]
Adjusted for 1.0.0-alpha5 on 2026-09-29. All four runtimes survive and a byo Harness still requires workload.command, so the core of this issue stands. Two changes affect the steps below:

  • allowedAgentTemplates is removed from HarnessSpec entirely. The test step that creates a template "labelled for that harness" describes label pairing that no longer exists. alpha5 pairs a template to a harness through the explicit Agent kind instead.
  • The UI gained explicit Agent create, edit and delete in kagent#2953, on the same surface this issue covers. Decide whether that belongs here or in its own page before writing.

Part of #549.

kagent#2935 added bring-your-own harnesses to the UI. agents/bring-your-own-agent.md documents the CLI and YAML path alone, so a reader working in the UI has no route through the feature.

This is a section added to an existing page, plus screenshots.

What changed in the UI

  • Agents → New Harness offers byo as a runtime, with command and args inputs. Create stays disabled until a command is supplied, which mirrors the API rule that a byo Harness must override the entrypoint because kagent does not infer it.
  • The model is now optional on an AgentTemplate. The form warns when a matching non-BYO harness still needs one. This is the change most likely to confuse a reader who learned the old rule, so it wants stating plainly rather than as a UI aside.
  • The Harnesses tab reports the runtime as byo, where HarnessService previously returned it blank.

How this meets the existing page

bring-your-own-agent.md already carries the four requirements a byo image must meet and the rule that kagent enforces only spec.workload.command at apply time. The UI enforces that same rule at a different moment, by disabling Create. Write the UI path as another route to the same contract rather than as a separate feature, so the page does not grow two accounts of one thing.

Check whether agents/agent-harness.md needs a matching line, since its workload field table is where a reader meets workload.command first.

Screenshots

The pull request added a BYO harness to the mock fixtures, so the new-harness form and the Harnesses tab can be captured from mocks rather than from a live cluster. Confirm that against the harness before assuming it, because a live capture and a mock capture are configured differently.

What to check before starting

  1. Read agents/bring-your-own-agent.md end to end, so the UI section states the contract the same way the YAML section already does.
  2. Build the fixture image with make build-byo-a2a, and create a BYO harness through the form using that image's digest.
  3. Confirm Create stays disabled until a command is entered.
  4. Confirm the Harnesses tab shows the runtime as byo.
  5. Create an AgentTemplate with no model, labelled for that harness, and confirm it saves and appears under Runs on.
  6. Send the agent a message and confirm it replies.

Done when

  • The page covers creating a byo Harness through the UI, including command and args.
  • The disabled Create button is explained by the underlying rule rather than described as UI behavior.
  • The optional model on an AgentTemplate is documented, including when the form warns.
  • Screenshots follow the site's existing capture setup, and the page says which UI version they show.
  • agents/agent-harness.md is checked for a matching update.
  • Every step was run against a real BYO image.
Lenguaje dominante
TypeScript
Estrellas
21
Forks
69
Merge medio
14 h 16 min
PR fusionados (30 d)
96

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de kagent-dev/website

Todos los issues de kagent-dev/website

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.