Kawl Now for Python websites
Prepare the voice widget in an existing HTML, Flask/Jinja or Django shared template, run your website checks, then connect a short-lived setup API key. This is a native Python installer: it has no runtime dependencies and does not download or invoke Node, npm, a JavaScript runtime, or your application code. Python 3.10 or newer is required.
Ask your coding agent:
Install Kawl Now in this website using https://www.kawlnow.com/install. Finish the local integration and checks first, then ask me for my setup API key.
Run a pinned, isolated installer with uv:
uvx --from kawlnow==0.1.0 kawlnow init --channel support --write --json
For an explicit shared template:
uvx --from kawlnow==0.1.0 kawlnow init --channel support --target templates/base.html --write --json
Use --channel sales for Sales. Without --write, init only prints a local
plan; it never reads a key, makes a network request or changes a file.
Auto-detection accepts one unambiguous existing shared HTML shell. If several
candidate shells exist, select the intended file with --target.
It preserves the existing template, scripts, template expressions and line
endings. The inactive marker does not load the widget. Review template conditions
and inheritance with your coding agent; a source-file check cannot prove which
pages actually render that template.
For a reusable isolated tool, pipx install kawlnow==0.1.0 exposes the same
kawlnow command. In an existing virtual environment, use
python -m pip install kawlnow==0.1.0, then python -m kawlnow.
Use the npm installer for React and Next.js applications; this distribution
does not pretend to install React dependencies or wire JSX layouts.
Check the prepared integration without account access:
uvx --from kawlnow==0.1.0 kawlnow doctor --channel support --site-origin https://YOUR_VERIFIED_DOMAIN --json
doctor (also named status) checks the saved public plan, owned marker, file
hash and shared shell. The shared kawlnow-install protocol version 1 exposes
readiness.keyInputAllowed: it is true only for unchanged local preparation
and an explicitly supplied production origin. A missing origin reports
awaiting_site_origin; a missing plan reports not_prepared.
Its structured nextActions and resume.argv explain
the next step. Exit 0 means a local dry run, a ready local doctor check or a connected local integration;
exit 2 means input or a later acceptance step is still required; exit 1
means a conflict or error. None of those states establishes voice acceptance.
After local preparation, create a setup key in Kawl Now's Installation panel for the selected brand and Support/Sales agent. It expires after 24 hours. No workspace ID or browser OAuth session is needed to begin. Connect using the same pinned installer version that created the plan:
uvx --from kawlnow==0.1.0 kawlnow connect --channel support --site-origin https://YOUR_VERIFIED_DOMAIN --write
The interactive command reads a hidden terminal prompt. A coding agent or CI
runner can instead supply one secret line through --api-key-stdin or the
KAWLNOW_SETUP_KEY variable using its ephemeral secret facility. --json
never prompts. Never paste a key into a command argument, inline environment
assignment, source file, chat prompt, public plan or log. Keys are used in memory
and are not persisted. A full-management token is rejected.
The production origin is explicit: metadata inside your repository cannot
authorize a new origin or choose a credential destination. Connection verifies
the selected brand and channel, merges only the supplied origin and preserves
existing origins. --expect-workspace PUBLIC_BRAND_ID can bind public brand
context copied from the dashboard. The default key destination is
https://app.kawlnow.com; a custom public HTTPS endpoint must be explicitly
trusted with --app-origin on every connection. Redirects are refused.
The public kawlnow.python.install.support.json (or Sales equivalent) records
only public integration context. It is deliberately separate from npm plans.
The installer refuses changed files, symbolic links, unsupported paths and
existing integrations requiring review. Repeated preparation is idempotent.
The installer does not publish your website, approve knowledge, enable customer calls, change billing or destinations, start conversations or test a microphone. After an authorized website deployment, inspect the real widget and use the Installation panel's bounded verifier. The verifier is static; browser behavior, voice acceptance and owner call enablement remain separate checks.
Public guides: installation and starters, complete setup reference, browser-local widget checker.
Metadata
Release files for kawlnow 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kawlnow-0.1.0.tar.gz | 19.5 kB | With provenance | Details for kawlnow-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kawlnow-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for kawlnow-0.1.0-py3-none-any.whl |
Total release size: 37.3 kB
Release files / kawlnow-0.1.0.tar.gz
| Download URL | kawlnow-0.1.0.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87ef308c225e86352a8a3d04e783bb2d2d802cabfc4bb1e8098c86a5c07373e1
|
|
BLAKE2b-256 checksum How to use checksums |
ad3448e01f546d17394cd2815c520c9a331d80d505cdbcd2df48e55d9711c071
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 16, 2026.
Transparency logRelease files / kawlnow-0.1.0-py3-none-any.whl
| Download URL | kawlnow-0.1.0-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1535a0b4587e90f18134d41bbec8e8178701fe4b06800658863e20be7e8625e4
|
|
BLAKE2b-256 checksum How to use checksums |
29fd510549b899da2e0128fda68d01b6450bf757957a6efd829e72b20d3a5002
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 16, 2026.
Transparency logSecurity for kawlnow 0.1.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for kawlnow-0.1.0.tar.gz
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 Nov 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.