dgc-sdk
Run the DGC coding agent inside your own Python application or CI job. Version 0.6.7, editor protocol v14, pairs with DGC CLI 0.43.4. Python 3.10+, proven on Linux.
python3 -m pip install dgc-sdk==0.6.7
This installs import dgc_sdk. It is not the unrelated PyPI project dgc.
The SDK drives a dgc serve process from a DGC CLI install, which it finds on its own (dgc on
PATH, ~/.local/bin/dgc, or the installer's versions directory). Install the CLI:
curl -fsSL https://vibedgc.com/install.sh | bash
To pin a different install, set DGC_PYTHON to its Python, for example
export DGC_PYTHON="$(dirname "$(readlink -f "$(command -v dgc)")")/python".
Point DGC_MODEL and DGC_BASE_URL at an OpenAI-compatible endpoint (for example a local Ollama
at http://127.0.0.1:11434/v1), then run this from the repository you want summarized:
import os
import tempfile
from dgc_sdk import DGC
with DGC(
state_dir=tempfile.mkdtemp(prefix="dgc-sdk-"),
model=os.environ["DGC_MODEL"], # for example "qwen3:8b"
base_url=os.environ["DGC_BASE_URL"], # for example "http://127.0.0.1:11434/v1"
api_key=os.environ.get("DGC_API_KEY"), # only when the endpoint needs a key
) as dgc:
session = dgc.session(cwd=".", permissions={"mode": "plan", "unhandled": "deny"})
result = session.run("Summarize this repository in two sentences. Do not edit files.")
print(result.status, result.final_text)
if result.error:
print("error:", result.error)
It prints completed and the summary. Each DGC client keeps its conversations, checkpoints and
logs in state_dir, an isolated HOME; your own ~/.dgc is not touched, and an SDK-created
temporary state_dir is removed on close().
For untrusted input (a pull request, a cloned repo) the workspace cannot grant the session
capabilities: its own .dgc/permissions.json allow rules and .dgc/agents are ignored unless you
pass trust_workspace=True. Add a RuntimePolicy to sandbox the shell and confine the file tools,
and see the security model in docs/SDK.md.
- Guide and full API reference: docs/SDK.md
- Runnable examples: examples/sdk
- Changes: sdk/CHANGELOG.md
- Verifying this package against its GitHub release: docs/SDK.md#verifying-a-release
Licensed under Apache-2.0.
Metadata
Release files for dgc-sdk 0.6.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dgc_sdk-0.6.7.tar.gz | 102.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dgc_sdk-0.6.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 211.1 kB
Release files / dgc_sdk-0.6.7.tar.gz
| Download URL | dgc_sdk-0.6.7.tar.gz |
|---|---|
| Size | 102.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99eb3d59c6257683887d9ce15b33b7511ed32209bed2ef66b1cc3b3ccfa1c60d
|
|
BLAKE2b-256 checksum How to use checksums |
028a005b204e6b341f17a568a8ebcde9acd447b67036fe08232102be0f58bf3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logRelease files / dgc_sdk-0.6.7-py3-none-any.whl
| Download URL | dgc_sdk-0.6.7-py3-none-any.whl |
|---|---|
| Size | 109.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52bb7860d123de6bf5b730bb12a8c4135ac8e25fd39ead7746f5a53d4811929d
|
|
BLAKE2b-256 checksum How to use checksums |
0829a7e4df677a014e298ed7dadf4749c85c57abe793724b8870e07996a3d63d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency log