A debugging and testing cog for discord.py rewrite bots.





GitHub Stars



Last Commit

4d ago










Python versions License Status Circle CI AppVeyor CI Issues Commit activity


a debugging and utility extension for discord.py bots
Read the documentation online.

⚠️ Warning

As of the 27th of August 2021, discord.py has ceased development.

Jishaku will continue to be maintained targeting both the PyPI version and the latest git revision as of the archive, until at least the date of the slash command mandate (currently speculated to be around April 2022).

As all trusted contributors have rejected continuing the library, I do not have enough trust in any forks to target those instead. The existing forks are handled by inexperienced developers, and I figure this will continue to be the case in the future, as all of the developers experienced enough to carry the torch do not want to maintain the library for similar reasons to Danny himself.

However, if you personally decide that you wish to use a fork, I will allow Jishaku to honor your decision by removing the discord.py package requirement. This means, from now on, installing jishaku will not automatically handle installing discord.py, you must choose a version to use yourself. Any fork that you use must be compatible with the original (in that it supplies the discord module and its namespaces).

When April 2022 comes, I will make a decision at the time as to whether I want to continue maintaining Jishaku. I still enjoy making and maintaining bots, but implementing Jishaku under the philosophies I have defined so far will likely be impossible under the new slash commands, and I don't really want to compromise my work for the sake of appeasing a company that doesn't care for its developers.

I hope you've found Jishaku useful, and hopefully it will get to live on in one way or another.

jishaku is an extension for bot developers that enables rapid prototyping, experimentation, and debugging of features for bots.

One of jishaku's core philosophies is to be dynamic and easy-to-use. Here's the two step install:

  1. Download jishaku on the command line using pip:
pip install -U jishaku
  1. Load the extension in your bot code before it runs:

That's it!

You can also import the module to use the command development utilities.


Command reference

> jishaku [py|python] <argument>

> jishaku [pyi|python_inspect] <argument>

The Python commands execute or evaluate Python code passed into them. It supports simple expressions:

> jsk py 3+4

Beep Bot


It also supports async expressions:

> jsk py await _ctx.pins()

Beep Bot

[<Message id=123456789012345678 ...>, ...]

You can pass in codeblocks for longer blocks of code to execute, and you can use yield to return intermediate results within your processing.

The inspect variant of the command will return a codeblock with detailed inspection information on all objects returned.

The variables available by default in all execution contexts are:

_ctx The Context that invoked the command.
_bot The running Bot instance.
Shortcuts for attributes on _ctx.
Shortcuts for discord.utils functions.

The underscore prefix on the provided variables is intended to help prevent shadowing when writing large blocks of code within the command.
If you decide that you don't want the prefix, you can disable it by setting the JISHAKU_NO_UNDERSCORE environment variable to true.

Each Python command is individually scoped. That means variables you create won't be retained in later invocations.
You can use jishaku retain on to change this behavior and retain variables, and jishaku retain off if you change your mind later.

> jishaku [dis|disassemble] <argument>

This command compiles Python code in an asynchronous context, and then disassembles the resulting function into Python bytecode in the style of dis.dis.

This allows you to quickly and easily determine the bytecode that results from a given expression or piece of code. The code itself is not actually executed.

> jishaku [sh|shell] <argument>

The shell command executes commands within your system shell.

If you're on Linux and are using a custom shell, jishaku will obey the SHELL environment variable, otherwise, it will use /bin/bash.
On Windows, jishaku will use PowerShell if it's detected, otherwise, it will use Command Prompt.

The results from the commands you pass in are returned through a paginator interface live as the command runs. If you need to stop a command, you can press the stop button reaction, or use jsk cancel.

The execution will terminate automatically if no output is produced for 120 seconds.

> jishaku git <argument>

> jishaku pip <argument>

These commands act as shortcuts to the shell command, so you can save typing a word if you use these frequently.

> jishaku [load|reload] [extensions...]

> jishaku unload [extensions...]

These commands load, reload, or unload extensions on your bot.

You can reload jishaku itself with jsk reload jishaku.
jsk reload ~ will reload all extensions on your bot.

You can load, reload, or unload multiple extensions at once: jsk reload cogs.one cogs.two

> jishaku shutdown

This command gracefully shuts down your bot.

> jishaku rtt

This command calculates Round-Trip Time for your bot to the API. It does this by calculating response time samples, so you can tell if your bot is being slow or not.

> jishaku cat <file>

This command reads a file from your file system, automatically detecting encoding and (if applicable) highlighting.

You can use this to read things like bot logs or source files in your project.

> jishaku curl <url>

This command reads text from a URL and attempts to detect encoding and language, similar to jsk cat.

You can use this to display contents of files online, for instance, the message.txt files created when a message is too long, or raw files from paste sites.

> jishaku exec [member and/or channel...] <command string>

> jishaku debug <command string>

> jishaku repeat <times> <command string>

These commands serve as command control for other commands.

jishaku exec allows you to execute a command as another user, in another channel, or both. Using aliases with a postfix exclamation mark (such as jsk exec! ...) executes the command bypassing checks and cooldowns.

jishaku debug executes a command with an exception wrapper and a timer. This allows you to quickly get feedback on reproducable command errors and slowdowns.

jishaku repeat repeats a command a number of times.

> jishaku permtrace <channel> [targets...]

This command allows you to investigate the source of expressed permissions in a given channel. Targets can be either a member, or a list of roles (to simulate a member with those roles).

It will read all of the guild permissions and channel overwrites for the given member or roles in the channel, and provide a breakdown containing whether the permission is granted, and the most fundamental reason why.

Installing development versions

If you'd like to test the latest versions of jishaku, you can do so by downloading from the git hosts instead of from PyPI.

From GitHub:

pip install -U "jishaku @ git+https://github.com/Gorialis/jishaku@master"

From GitLab:

pip install -U "jishaku @ git+https://gitlab.com/Gorialis/jishaku@master"

Please note that the new 2020 dependency resolver now no longer discounts git package sources from reinstall prevention, which means that if you are installing the jishaku development version multiple times within the same version target you may run into pip just discarding the update.

If you run into such a problem, you can force jishaku to be reinstalled like this:

From GitHub:

pip install -U --force-reinstall "jishaku @ git+https://github.com/Gorialis/jishaku@master"

From GitLab:

pip install -U --force-reinstall "jishaku @ git+https://gitlab.com/Gorialis/jishaku@master"

You must have installed jishaku with one of the commands above before doing this else you will probably end up with a broken installation.


The documentation and this README uses icons from the Material Design Icon library, which is licensed under the Apache License Version 2.0.

Rate & Review

Great Documentation0
Easy to Use0
Highly Customizable0
Bleeding Edge0
Responsive Maintainers0
Poor Documentation0
Hard to Use0
Unwelcoming Community0