jusi-gigacode

jusi-gigacode is the exact GigaCode provider for the shared Jusi ACP family. It launches GigaCode over Agent Client Protocol while jusi-acp supplies the %%acp magic, interactive VisiData application, permission choices, durable follow-ups, cancellation, session controls, completion, editor actions, and attention notifications.

Installation

Install this package, jusi-acp, and Jusi in the Python environment used by the target Jupyter kernel. The gigacode executable must be available on that target's PATH. Attention support requires jusi-acp>=0.1.3 and Jusi >=1.0.5, installed automatically through the package dependencies.

pip install jusi-gigacode

For development from sibling checkouts:

python3.12 -m venv .venv
.venv/bin/pip install -e ../jusi-acp -e '.[dev]'
.venv/bin/pytest

Configuration

Add an ACP alias to ~/.jusi/jusi.toml on the kernel target:

[acp.work]
provider = "gigacode"
path = "/path/to/project"
additional_directories = ["../shared"]
model = "provider-owned-model-name"

Then run:

%%acp work
Inspect the project and implement the requested change.

The provider launches gigacode --acp. A live GigaCode handshake has confirmed ACP protocol version 1, the browser-backed gigacode authentication method, session load/resume support, and HTTP/SSE MCP support.

Provider-specific alias options are:

• executable: executable name or path; defaults to gigacode.
• model: passed as --model VALUE.
• approval_mode: passed as --approval-mode VALUE. Leaving it unset allows ACP permission requests to reach the interactive Jusi client.
• arguments: an array of additional command-line arguments.
• environment: environment-variable overrides for the GigaCode process.
• auth_method: ACP authentication method ID. It defaults to gigacode, as advertised by GigaCode, or may be set to an empty string to skip the proactive authentication call.

The executable inherits the target environment, including desktop/session variables used by browser launchers. With the default authentication method, jusi-acp calls ACP authenticate before creating the session. GigaCode owns opening its authorization URL and waiting for the callback; after it completes, the original cell body is submitted automatically.

Session controls and family commands include:

%%acp work --load SESSION_ID
Replay and continue a stored session.

%%acp work --resume SESSION_ID
Continue a stored session without replay.

Follow-up cells can use /mode ID, /config ID VALUE, /auth METHOD_ID, and /cancel. Slash commands advertised by GigaCode are also completed and sent as ordinary ACP prompts.

Verified ACP handshake

GigaCode identifies its agent implementation as qwen-code with the title GigaCode. It advertises authentication method ID gigacode; authentication is handled by the GigaCode backend through its browser flow. The initialize call waits for that flow to finish, after which jusi-acp completes ACP authentication, establishes the session, and submits the original cell body without requiring the user to repeat it.