Skip to content

Agent Manager

The Agent Manager is a dedicated control panel that runs and monitors VJSP Agents as interactive command-line processes. It supports the following features:

  • Local session execution

  • Recovery of existing sessions

  • Parallel Mode (compatible with Git worktrees) for secure, isolated code modifications

  • View and resume cloud-synced sessions that match the current code repository

The content on this page aligns fully with the plugin’s actual implementation logic.

Prerequisites

  1. Install/update to the latest version of the VJSP Command Line Interface (CLI) — see CLI Configuration for details.

  2. Open your project in VS Code (a workspace must already be created).

  3. Authentication: Complete login via the plugin settings, or use the CLI with VJSP as your service provider (see the Authentication Requirements section for details).

Open the Agent Manager

  • Command Palette: Enter VJSP: Open Agent Manager.

  • If a corresponding title/menu entry is available in the VJSP interface, click it to open the manager directly.

The panel opens as a web view and remains active when you switch window focus.

Message Sending, Action Approval, and Process Control

  • Continue Conversation: Send follow-up messages to a running Agent.

  • Action Approval: A prompt will appear if the Agent requests to call tools, execute commands, launch a browser, or connect to an MCP server.

    • You can approve or reject the request, and add short notes if needed.
  • Difference Between Cancel and Stop

    • Cancel: Sends a structured cancellation instruction to the running process (a collaborative, graceful stop).

    • Stop: Force-terminates the underlying command-line process, and the process status updates to Stopped automatically.

Recover Existing Sessions

Both local and remote sessions can be resumed for later use:

  • If the target session is not currently running, the Agent Manager will start a new command-line process and link it to the session’s unique identifier (ID).

  • Tag information from the original session will be retained as much as possible.

  • The first follow-up message you send will serve as the input for session recovery.

Parallel Mode

Parallel Mode runs the Agent in an isolated Git worktree branch to keep the main branch clean of redundant modifications.

  1. Toggle the Parallel Mode switch on before starting the Agent.

  2. The plugin prohibits using Parallel Mode within an existing worktree.

    • You must open the main code repository (the directory containing the .git folder) to use this feature.

Worktree Storage Path

Worktrees are created in the .vjsp/worktrees/ folder within your project directory. This folder is automatically added to Git’s local ignore rules (.git/info/exclude) and does not need to be committed to the code repository.

plain

your-project/
├── .git/
│   └── info/
│       └── exclude   # Git local ignore rules (includes .vjsp/worktrees/)
├── .vjsp/
│   └── worktrees/
│       └── feature-branch-1234567890/   # Isolated code working directory
└── ...

Running Status Display

The Agent Manager shows the following information in real time:

  • Name of the branch created/in use

  • Exact path of the worktree

  • After the Agent finishes running, it will display guidelines for merging/completing the branch.

Post-Execution Processing

  • Worktrees are automatically cleaned up, but their corresponding branches are retained.

  • You can view code modifications on the branch in the Version Control (VCS) interface.

  • Merge the branch or use cherry-pick to integrate code modifications as needed.

Parallel Mode Session Recovery

When resuming a Parallel Mode session later, the plugin follows this logic:

  1. Reuse the original worktree directly if it still exists.

  2. Recreate the worktree from the branch linked to the session if the original worktree has been cleaned up.

Authentication Requirements

You must complete valid authentication to unlock the Agent Manager’s full functionality, including session synchronization.

Supported Authentication Methods

  • Complete login via the plugin settings page.

  • Provides a seamless authentication experience for the Agent Manager.

Method 2: CLI with VJSP as the Service Provider

  • Use the CLI with vjsp configured as your default service provider.

  • Run the vjsp config command to complete authentication setup.

  • See CLI Configuration for detailed steps.

Troubleshooting

Prompt: "Please open a folder…"

The Agent Manager depends on a VS Code workspace folder. You must open your project directory first.

Prompt: "Cannot use parallel mode from within a git worktree"

You must open the main code repository (the directory containing the .git folder) — not a checked-out worktree directory.

Authentication Failure

  • Verify that you’ve logged in via the plugin settings or are using the CLI with VJSP as your service provider.