jusi-gigacode: GigaCode in Jupyter through Agent Client Protocol
jusi-gigacode
A Python package gives the GigaCode agent Jupyter cells through ACP: browser sign-in, session resume, permission prompts and task cancellation
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- The GigaCode agent changes project files and runs commands from a cell, so the approval mode should be chosen deliberately
- Sign-in goes through an authorization page in the browser and GigaCode keeps the token on the machine
Install
- Services
Manual install
pip install jusi-gigacodeInstall it into the Jupyter kernel environment along with `jusi-acp` and Jusi; `gigacode` must be in `PATH` and the alias is set in `~/.jusi/jusi.toml`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The GigaCode agent changes project files and runs commands from a cell, so the approval mode should be chosen deliberately
- Sign-in goes through an authorization page in the browser and GigaCode keeps the token on the machine
This is third-party code. Review the repository files before installing.
What it does
The `jusi-gigacode` package is the GigaCode provider for the Jusi ACP family: it launches `gigacode --acp` over the Agent Client Protocol, while `jusi-acp` supplies the `%%acp` magic, an interactive VisiData application, permission choices, cancellation, session control and notifications. An alias goes in `~/.jusi/jusi.toml` (`[acp.work]`, `provider = "gigacode"`, project path, model, extra directories), after which a `%%acp work` cell sends a request to the agent. Provider options: `executable`, `model`, `approval_mode`, `arguments`, `environment`, `auth_method`. A live handshake confirmed ACP protocol version 1, the browser sign-in method `gigacode`, session load and resume and MCP support over HTTP and SSE. The `/mode`, `/config`, `/auth` and `/cancel` commands work in follow-up cells.
Who it is for. Analysts and researchers working in Jupyter who want to hold a dialogue with a GigaCode agent over their project in notebook cells.
Good fit when
- A GigaCode agent should work on a project straight from a notebook cell
- A past session has to be loaded with replay or resumed without replay
- Agent permissions should be approved by a choice in the interface rather than automatically
- A long task has to be stopped with `/cancel` without killing the kernel
Not a fit when
- You need chat outside Jupyter: the package works only as a provider for `jusi-acp` and a Jupyter kernel
- The `gigacode` executable is missing from the target environment `PATH`: the provider does not install it
- You need sign-in without a browser: the default method opens an authorization page
Example request
%%acp work
Inspect the project and implement the requested changeLimitations
It works only together with `jusi-acp` and Jusi in the same Python environment as the Jupyter kernel, and the `gigacode` executable must be in the target machine `PATH`. Sign-in goes through the browser: GigaCode itself opens the authorization page and waits for the answer, after which the original cell is sent automatically. The `approval_mode` is unset by default, so permission requests reach the interactive client. Notifications need `jusi-acp` 0.1.3 and Jusi 1.0.5 or newer. The package is small: zero stars, last commit in October 2026, MIT license.
How to disable. Remove the `[acp.work]` alias from `~/.jusi/jusi.toml` and run `pip uninstall jusi-gigacode` in the Jupyter kernel environment.
FAQ
What do I need besides the package?
`jusi-acp` and Jusi in the same environment as the Jupyter kernel, and `gigacode` must be in `PATH`.
How do I configure the alias?
In `~/.jusi/jusi.toml` create an `[acp.work]` table with `provider = "gigacode"`, the project `path` and optionally `model` and `additional_directories`.
How do I continue an old session?
With a `%%acp work --load ID` cell with history replay or `--resume ID` without replay.
How does sign-in work?
Through the ACP method `gigacode`: GigaCode opens the authorization page in a browser and waits for the answer, then the cell is sent on its own.
Can the approval mode be set?
Yes, with the alias option `approval_mode`, which is passed as `--approval-mode`; if unset the interactive client asks for permissions.
Discussion
No questions or reviews yet.
Related
All GigaChat toolsGigaCode Bridge MCP
Gigacode-bridge-mcp
MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review
MCP server for the GigaChat API
GigaChat API
A small Python MCP server for Sber's GigaChat API: authorizes with a Basic key and calls the models directly from an agent, tested on OpenCode under Windows
Process Kit for GigaCode
process-kit
A GigaCode workspace where the assistant takes a task in words, finds a ready process made of steps and runs it with a plan and a report in outputs
An unofficial Chrome extension adds an MCP button to the giga.chat chat: servers by URL, OAuth 2.1, local programs and confirmation of every call
GigaCode Proxy for editors: Cline, Roo Code, Continue
GigacodeOpenaiProxy
A dependency-free proxy connects GigaCode to Cline, Roo Code, Continue and Open WebUI, repairs tool call cuts and signs in with SberID
QA Agent for the GigaCode CLI: 14 roles and 6 skills for testing
QaAgentGigacodeCli
Requirements-based testing in GigaCode: from analysis and autotest review to a conclusion, with duplicate search before a bug is filed in Jira
README in short
The README sets out package installation, alias setup in `jusi.toml`, provider options, session control commands (`--load`, `--resume`, `/mode`, `/config`, `/auth`, `/cancel`) and the results of a verified ACP handshake with GigaCode.