No description
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Thorsten Klein 516d7da058
All checks were successful
test / test (push) Successful in 1m37s
fix(install): use v0.9.11 and soften token hints (#4)
## Summary

basepeak-ai/gptscript is public now and v0.9.11 is released, so `install_gptscript` and `scripts/package` download it without a token.

- **Pin gptscript v0.9.11** in `gptscript/install.py` and `scripts/package`. The package version also moves to `0.9.11` (`pyproject.toml`), matching the convention that the SDK version tracks the gptscript version.
- **Token stays optional.** `GPTSCRIPT_RELEASE_TOKEN` is still sent as a Forgejo `Authorization` header when set (tox still passes it through). The comments no longer say the repo is private.
- **Better failure hint.** Before, any non-2xx answer without a token added "set GPTSCRIPT_RELEASE_TOKEN for the private gptscript repo". Now the token is suggested only on HTTP 401/403/404. Other statuses report just the status.
- **README**: says downloads are public and the token is optional.
- **CI**: the workflow no longer sets `GPTSCRIPT_RELEASE_TOKEN`, so both install runs (the direct run and the one in tox) test the anonymous path.

## Verification

In a fresh Python 3.12 venv with no token in the environment and `PIP_CONFIG_FILE=/dev/null`:

```
pip install git+https://git.basepeak.dev/basepeak-ai/py-gptscript.git@fix/install-v0.9.11   # gptscript 0.9.11
install_gptscript    # symlink -> venv/bin/gptscript-v0.9.11
gptscript --version  # gptscript version v0.9.11+7299ab79
```
2026-10-18 12:01:45 +00:00
.github/workflows fix(install): use v0.9.11 and soften token hints (#4) 2026-10-18 12:01:45 +00:00
examples chore: prep for v0.8.4 release 2024-06-25 13:19:40 -04:00
gptscript fix(install): use v0.9.11 and soften token hints (#4) 2026-10-18 12:01:45 +00:00
scripts fix(install): use v0.9.11 and soften token hints (#4) 2026-10-18 12:01:45 +00:00
tests fix: set the description of tool_list fixture 2025-04-24 16:49:17 -04:00
.gitignore package binaries by default for linux, win, macOS 2024-03-08 10:25:24 -07:00
LICENSE initial commit 2024-03-05 17:00:35 -07:00
lock.txt fix(deps): raise dep floors past known vulns (#2) 2026-10-18 10:48:00 +00:00
NOTICE docs: add upstream attribution and NOTICE (#3) 2026-10-18 10:48:47 +00:00
pyproject.toml fix(install): use v0.9.11 and soften token hints (#4) 2026-10-18 12:01:45 +00:00
README.md fix(install): use v0.9.11 and soften token hints (#4) 2026-10-18 12:01:45 +00:00
requirements.txt fix(deps): raise dep floors past known vulns (#2) 2026-10-18 10:48:00 +00:00
tox.ini fix(install): fetch gptscript from our Forgejo release (#1) 2026-10-17 21:25:51 +00:00

GPTScript Python Module

Fork notice / Attribution

This repository is a fork of py-gptscript, originally developed by Acorn Labs, Inc. (now Obot Inc.) and the gptscript-ai contributors. The upstream project has been archived. This fork is maintained by BasePeak GmbH at https://git.basepeak.dev/basepeak-ai/py-gptscript.

BasePeak GmbH has modified files in this repository since the fork on 2026-06-13. The git history records every change. See NOTICE for details.

Introduction

The GPTScript Python module is a library that provides a simple interface to create and run gptscripts within Python applications, and Jupyter notebooks. It allows you to define tools, execute them, and process the responses.

Installation

This fork is not published to PyPI. The gptscript package on pypi.org is the archived upstream release, not this fork. Install the fork from git instead:

pip install git+https://git.basepeak.dev/basepeak-ai/py-gptscript.git

Installing the gptscript binary

Installing from git (like installing from the sdist or the py3-none-any wheel) does not include the gptscript binary. You must run the install_gptscript command to download it from the gptscript fork's releases. The release downloads are public, so no token is needed. GPTSCRIPT_RELEASE_TOKEN is optional: when set, it is sent as a Forgejo token with the download request.

install_gptscript

install_gptscript places the gptscript binary in the same directory as the Python executable, so it should be on your PATH.

Or you can install the gptscript cli from your code by running:

from gptscript.install import install

install()

Using an existing gptscript cli

If you already have the gptscript cli installed, you can use it by setting the envvar:

export GPTSCRIPT_BIN="/path/to/gptscript"

GPTScript

The GPTScript instance allows the caller to run gptscript files, tools, and other operations (see below). Note that the intention is that a single GPTScript instance is all you need for the life of your application, you should call close() on the instance when you are done.

Global Options

When creating a GTPScript instance, you can pass the following global options. These options are also available as run Options. Anything specified as a run option will take precedence over the global option.

  • APIKey: Specify an OpenAI API key for authenticating requests. Defaults to OPENAI_API_KEY environment variable
  • BaseURL: A base URL for an OpenAI compatible API (the default is https://api.openai.com/v1)
  • DefaultModel: The default model to use for chat completion requests
  • DefaultModelProvider: The default model provider to use for chat completion requests
  • Env: Supply the environment variables. Supplying anything here means that nothing from the environment is used. The default is os.environ(). Supplying Env at the run/evaluate level will be treated as "additional."

Run Options

These are optional options that can be passed to the run and evaluate functions. None of the options is required, and the defaults will reduce the number of calls made to the Model API. As noted above, the Global Options are also available to specify here. These options would take precedence.

  • disableCache: Enable or disable caching. Default (False).
  • subTool: Use tool of this name, not the first tool
  • input: Input arguments for the tool run
  • workspace: Directory to use for the workspace, if specified it will not be deleted on exit
  • chatState: The chat state to continue, or null to start a new chat and return the state
  • confirm: Prompt before running potentially dangerous commands
  • prompt: Allow prompting of the user

Tools

The Tool class represents a gptscript tool. The fields align with what you would be able to define in a normal gptscript .gpt file.

Fields

  • name: The name of the tool.
  • description: A description of the tool.
  • tools: Additional tools associated with the main tool.
  • maxTokens: The maximum number of tokens to generate.
  • model: The GPT model to use.
  • cache: Whether to use caching for responses.
  • temperature: The temperature parameter for response generation.
  • arguments: Additional arguments for the tool.
  • internalPrompt: Optional boolean defaults to None.
  • instructions: Instructions or additional information about the tool.
  • jsonResponse: Whether the response should be in JSON format.(If you set this to True, you must say 'json' in the instructions as well.)

Primary Functions

Aside from the list methods there are exec and exec_file methods that allow you to execute a tool and get the responses. Those functions also provide a streaming version of execution if you want to process the output streams in your code as the tool is running.

list_models()

This function lists the available GPT models.

from gptscript.gptscript import GPTScript


async def list_models():
    gptscript = GPTScript()
    models = await gptscript.list_models()
    print(models)
    gptscript.close()

parse()

Parse a file into a Tool data structure.

from gptscript.gptscript import GPTScript


async def parse_example():
    gptscript = GPTScript()
    tools = await gptscript.parse("/path/to/file")
    print(tools)
    gptscript.close()

parse_tool()

Parse the contents that represents a GPTScript file into a Tool data structure.

from gptscript.gptscript import GPTScript


async def parse_tool_example():
    gptscript = GPTScript()
    tools = await gptscript.parse_content("Instructions: Say hello!")
    print(tools)
    gptscript.close()

fmt()

Parse convert a tool data structure into a GPTScript file.

from gptscript.gptscript import GPTScript


async def fmt_example():
    gptscript = GPTScript()
    tools = await gptscript.parse_content("Instructions: Say hello!")
    print(tools)

    contents = gptscript.fmt(tools)
    print(contents)  # This would print "Instructions: Say hello!"
    gptscript.close()

evaluate()

Executes a tool with optional arguments.

from gptscript.gptscript import GPTScript
from gptscript.tool import ToolDef


async def evaluate_example():
    tool = ToolDef(instructions="Who was the president of the United States in 1928?")
    gptscript = GPTScript()

    run = gptscript.evaluate(tool)
    output = await run.text()

    print(output)

    gptscript.close()

run()

Executes a GPT script file with optional input and arguments. The script is relative to the callers source directory.

from gptscript.gptscript import GPTScript


async def evaluate_example():
    gptscript = GPTScript()

    run = gptscript.run("/path/to/file")
    output = await run.text()

    print(output)

    gptscript.close()

Streaming events

GPTScript provides events for the various steps it takes. You can get those events and process them with event_handlers. The evaluate method is used here, but the same functionality exists for the run method.

from gptscript.gptscript import GPTScript
from gptscript.frame import RunFrame, CallFrame, PromptFrame
from gptscript.run import Run


async def process_event(run: Run, event: RunFrame | CallFrame | PromptFrame):
    print(event.__dict__)


async def evaluate_example():
    gptscript = GPTScript()

    run = gptscript.run("/path/to/file", event_handlers=[process_event])
    output = await run.text()

    print(output)

    gptscript.close()

Confirm

Using the confirm: true option allows a user to inspect potentially dangerous commands before they are run. The caller has the ability to allow or disallow their running. In order to do this, a caller should look for the CallConfirm event.

from gptscript.gptscript import GPTScript
from gptscript.frame import RunFrame, CallFrame, PromptFrame
from gptscript.run import Run, RunEventType
from gptscript.confirm import AuthResponse

gptscript = GPTScript()


async def confirm(run: Run, event: RunFrame | CallFrame | PromptFrame):
    if event.type == RunEventType.callConfirm:
        # AuthResponse also has a "message" field to specify why the confirm was denied.
        await gptscript.confirm(AuthResponse(accept=True))


async def evaluate_example():
    run = gptscript.run("/path/to/file", event_handlers=[confirm])
    output = await run.text()

    print(output)

    gptscript.close()

Prompt

Using the prompt: true option allows a script to prompt a user for input. In order to do this, a caller should look for the Prompt event. Note that if a Prompt event occurs when it has not explicitly been allowed, then the run will error.

from gptscript.gptscript import GPTScript
from gptscript.frame import RunFrame, CallFrame, PromptFrame
from gptscript.run import Run
from gptscript.opts import Options
from gptscript.prompt import PromptResponse

gptscript = GPTScript()


async def prompt(run: Run, event: RunFrame | CallFrame | PromptFrame):
    if isinstance(event, PromptFrame):
        # The responses field here is a dictionary of prompt fields to values.
        await gptscript.prompt(PromptResponse(id=event.id, responses={event.fields[0]: "Some value"}))


async def evaluate_example():
    run = gptscript.run("/path/to/file", opts=Options(prompt=True), event_handlers=[prompt])
    output = await run.text()

    print(output)

    gptscript.close()

Example Usage

from gptscript.gptscript import GPTScript
from gptscript.tool import ToolDef

# Create the GPTScript object
gptscript = GPTScript()

# Define a tool
complex_tool = ToolDef(
    tools=["sys.write"],
    jsonResponse=True,
    cache=False,
    instructions="""
    Create three short graphic artist descriptions and their muses.
    These should be descriptive and explain their point of view.
    Also come up with a made-up name, they each should be from different
    backgrounds and approach art differently.
    the JSON response format should be:
    {
        artists: [{
            name: "name"
            description: "description"
        }]
    }
    """
)

# Execute the complex tool
run = gptscript.evaluate(complex_tool)
print(await run.text())

gptscript.close()

Example 2 multiple tools

In this example, multiple tool are provided to the exec function. The first tool is the only one that can exclude the name field. These will be joined and passed into the gptscript as a single gptscript.

from gptscript.gptscript import GPTScript
from gptscript.tool import ToolDef

gptscript = GPTScript()

tools = [
    ToolDef(tools=["echo"], instructions="echo hello times"),
    ToolDef(
        name="echo",
        tools=["sys.exec"],
        description="Echo's the input",
        args={"input": "the string input to echo"},
        instructions="""
        #!/bin/bash
        echo ${input}
        """,
    ),
]

run = gptscript.evaluate(tools)

print(await run.text())

gptscript.close()

License

Copyright (c) 2024-2025 Obot Inc. (formerly Acorn Labs, Inc.) (original work)

Modifications Copyright (c) 2026 BasePeak GmbH

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.