Skip to main content
Decorative header graphic for the PyCharm and Jupyter setup guide

Jupyter in PyCharm + Kumo Coding Agent

Overview

This guide walks you through setting up the KumoSDK and Kumo Coding Agent for use with the KumoRFM Pre-Trained model in Jupyter notebooks inside JetBrains PyCharm and IntelliJ development environments. This guide assumes minimal prior experience with Jupyter, PyCharm or IntelliJ editors, and coding agents. Experienced users may skip directly to the relevant sections.

Prerequisites

Make sure you have:
  1. PyCharm installed (Download) (or any python compatible IntelliJ editor)
  2. Python installed at the system level
  3. A Kumo account and API key (Create)
  4. Required PyCharm plugins enabled These plugins are usually installed and enabled by default, so you may not need to do anything. If needed, you can review, enable, or install plugins from PyCharm -> Settings -> Plugins.
You may also need:
  1. An OpenAI or Anthropic subscription (recommended - required for use with the Kumo Coding Agent)
  2. Homebrew (macOS package manager) (Install)
  3. GitHub CLI installed and authenticated (required for cloning coding agent context from GitHub)
🖥 Terminal
brew install gh     # install via Homebrew
gh auth status      # check if authenticated
gh auth login       # authenticate

Part 1: Setup for Jupyter in PyCharm + KumoSDK

Step 1: Create or Open a PyCharm Project

To create a new notebook:
  1. Create a new project
    • Select or create a local python environment for the project
      • Project type: Pure Python or Jupyter
      • Environment type: Venv (recommended) or Conda (if the Anaconda distribution is installed)
      • Select a Python version between 3.10 and 3.13
image
  1. Create a notebook .ipynb file inside your project
  2. Run a Cell (e.g., print("Hello Kumo!") to Start the Jupyter Server and notebook kernel
  3. Install or upgrade ipywidgets
Pycharm will automatically install the required IPython but does not by default install related ipywidgets package, which may lead to downstream warnings 📓 Notebook cell
%pip install --upgrade jupyter ipywidgets
A project-specific interpreter keeps KumoSDK and notebook dependencies separate from your system Python and from unrelated projects.

Step 2: Install KumoSDK

Install the KumoSDK in the same notebook environment: 📓 Notebook cell
%pip install kumoai
Using %pip instead of !pip helps ensure the package installs into the active notebook interpreter.
Verify installation: 📓 Notebook cell
import kumoai.experimental.rfm as rfm

print("Kumo SDK loaded successfully")

Step 3: Authenticate KumoSDK

You will need an API key to make calls to KumoRFM. There are two common approaches:
  • Use the interactive code block below to set KUMO_API_KEY from the notebook
  • Use the KumoRFM website and set KUMO_API_KEY manually
** Interactive authentication: ** 📓 Notebook cell
import os
import kumoai.experimental.rfm as rfm

if not os.environ.get("KUMO_API_KEY"):
    rfm.authenticate()

rfm.init(api_key=os.environ.get("KUMO_API_KEY"))
image ** Manual authentication: ** 📓 Notebook cell
import os
import kumoai.experimental.rfm as rfm

os.environ["KUMO_API_KEY"] = "YOUR_API_KEY_HERE"  # from  https://kumorfm.ai/api-keys
rfm.init(api_key=os.environ.get("KUMO_API_KEY"))
image

Step 4: Optional Dependencies

Install Graphviz:

The KumoSDK allows you to define and visualize a Kumo Graph, which represents data tables and the relationships between them. To enable Kumo Graph visualization with KumoSDK, the Graphviz library must be installed correctly. Installation requires:
  1. dot — an executable that is part of the Graphviz library, installed at the system level
  2. The graphviz Python package installed in the notebook kernel
Check if dot is installed: 📓 Notebook cell
import shutil
print(shutil.which("dot"))
If this returns None, install Graphviz: 🖥 Terminal
brew install graphviz
Install the Python package: 📓 Notebook cell
%pip install graphviz
Test that a simple graph renders: 📓 Notebook cell
from graphviz import Digraph

g = Digraph()
g.edge("Hello", "Kumo")
g

Install Jinja2:

The KumoSDK requires Jinja2, a Python library used to style displayed outputs. 📓 Notebook cell
%pip show Jinja2   # check if Jinja2 is installed
%pip install jinja2  # install

Part 2: Add a Coding Agent (Optional)

Choose one of the following to add an AI coding agent to your workflow:
Step 1: Open JetBrains AI and Select CodexJetBrains documents that Codex is available directly in JetBrains AI chat starting from IDE version 2025.3. Make sure you are using a recent PyCharm version and the latest AI Assistant plugin (enabled by default).To get started:
  1. Open the JetBrains AI widget in the top-right corner of PyCharm
  2. Follow the setup and authentication flow if JetBrains AI subscription or OpenAI subscription has not been enabled yet
  3. Open the AI chat and choose Codex from the agent picker image
Step 2: Install Kumo Coding Agent ContextThe Kumo Coding Agent has two parts:
  • Context (knowledge base): Documentation, PQL rules, workflow guides, and data connector references that teach the agent how to use the Kumo platform. Installed by cloning the repository.
  • Skills (slash commands): Actions like /kumo-issue and /kumo-pr for reporting bugs and contributing fixes. Installed via the skill installer.
Install the context:🖥 Terminal
cd your-project
git clone https://github.com/kumo-ai/kumo-coding-agent.git kumo-coding-agent
This action adds a directory named kumo-coding-agent to your project. It contains the Kumo Coding Agent’s knowledge base. Confirm that this directory appears in your project.Codex reads AGENTS.md automatically. No extra configuration needed.Install the skills (optional).Inside a Codex session or chat interface, run the following command and approve the requested actions:🤖 Codex
$skill-installer install https://github.com/kumo-ai/kumo-coding-agent
To confirm the Kumo slash-command skills were installed correctly, list the available skills and look for:
  • /kumo-issue to report an issue to Kumo
  • /kumo-pr to contribute fixes
🤖 Codex
/skills
Step 5: Use the Kumo Coding AgentTry a real prediction:🤖 Codex
wrap-code
Use the active VS Code notebook with the kumo-coding-agent skill to load the RelBench F1 dataset and use KumoRFM to predict whether each driver will finish in the top 3 in their next race.
The agent will inspect the data, build a graph, and write PQL. You can then run the notebook end-to-end. If needed, authenticate the KumoSDK within the notebook before running the prediction.
Before asking Codex to modify the notebook, save your changes first. If the notebook is not saved, PyCharm may keep your unsaved version as the active notebook view and treat Codex’s edits as the previous file version. If you do not see Codex’s changes, try one of the following:
  • Use the “Revert File” option in PyCharm to refresh the notebook (Cmd + Shift + P -> Revert File)
  • Close the notebook tab and reopen it
You are now fully set up with KumoSDK and the Kumo Coding Agent. You can proceed to:
  • the Kumo Coding Agent Quick Start for coding agent examples
  • the Kumo SDK Quick Start to get familiar with core SDK functionality
Step 4 (Optional): UpgradeUpgrade the KumoSDK:📓 Notebook cell
%pip install --upgrade kumoai
Upgrade the Kumo Coding Agent:🖥 Terminal
cd kumo-coding-agent && git pull
To pin to a specific version:
cd kumo-coding-agent && git checkout v1.0.0

Troubleshooting

  • If the notebook opens but cells do not run, re-check the selected interpreter and whether the Jupyter server started successfully.
  • If %pip install kumoai succeeds but import kumoai.experimental.rfm fails, verify that the notebook is using the same interpreter where the package was installed.
  • If authentication fails, confirm KUMO_API_KEY is set or repeat rfm.authenticate().
  • If Codex is not available in PyCharm, verify your PyCharm version, the AI Assistant plugin version, and that Codex appears in the JetBrains AI agent picker.
  • If Claude Code helps with project files but not notebook behavior, keep notebook execution inside PyCharm and use Claude Code mainly for project-side code and explanations.

Next Steps