Skip to content
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
This repository was archived by the owner on Jun 22, 2026. It is now read-only.

[Feature Request]: Allow Agent Init/Import in the JVCLI Client #21

Description

@ChrisIsKing

Is your feature request related to a problem? Please describe.
Currently, in jvcli, there is no easy way for users to re-import an agent directly from the jvclient UI. If users make changes to an agent, they have to manually call the API to trigger an agent re-import using init or import agent, which is inconvenient and slows down development.

Describe the solution you'd like

  • Add a "Re-import Agent" button in jvclient that allows users to reload an agent with the latest changes on the fly.
  • Clicking the button should trigger a backend request to reload the agent without requiring users to interact with the API directly.
  • The process should:
    1. Identify the selected agent.
    2. Call the appropriate API endpoint to re-import and reinitialize the agent.
    3. Display feedback to the user indicating whether the re-import was successful.

Implementation Plan

  1. Modify jvclient UI

    • Add a "Re-import Agent" button next to the agent selection panel.
    • Ensure the button is only enabled when an agent is selected.
  2. Implement API Trigger

    • On button click, send a request to the appropriate endpoint in jvserve to reload the agent.
    • Ensure the request includes the correct agent ID.
  3. Provide User Feedback

    • Display a success message if the agent reloads successfully.
    • Show an error message if the reload fails, with debugging information.

Expected Benefits

  • Improves developer workflow – Allows users to apply changes instantly without needing to restart services or manually call the API.
  • Enhances usability – Provides a more intuitive way to update agents directly from the UI.
  • Reduces friction – Removes the need for extra steps, making agent management smoother and more efficient.

Describe alternatives you've considered

  • Keeping the manual API trigger workflow, but this adds unnecessary complexity for users.
  • Implementing an automatic reload on file change, but this could introduce unintended side effects.

Additional context

  • This feature aligns with existing agent management functionalities in jvclient and enhances the real-time usability of jvcli.
  • Future enhancements could include auto-reload on file save or batch updates for multiple agents.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status
Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions