Skip to main content

omnichar-frontend

Prebuilt Inline Studio web UI (SPA), packaged so Inline Core can serve it on a single port - mirroring ComfyUI's comfyui-frontend-package. End users pip install omnichar-core (which depends on this), then run python main.py; no Node build on their machine.

What's in the wheel

The payload is the built SPA under omnichar_frontend/static/ (index.html + hashed assets/). Core resolves this dir via inline_core.server.frontend.resolve_frontend_root and mounts it.

Publishing (release only)

# in the Inline Studio repo
npm run build:spa                       # -> dist-web/
cp -r dist-web/* packages/frontend/omnichar_frontend/static/
cd packages/frontend
python -m build && twine upload dist/*  # publish to PyPI

Local development - don't republish

Point Core at a local build instead:

npm run build:spa
python main.py --front-end-root ../Inline-Studio/dist-web   # in the Inline Core repo
# or, for HMR:
npm run dev:web        # Vite dev server on :5173, proxying the backend to Core

Release files for omnichar-frontend 1.3.26

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for omnichar-frontend 1.3.26
File Size Uploaded
omnichar_frontend-1.3.26.tar.gz 568.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for omnichar-frontend 1.3.26
File Interpreter ABI Platform
omnichar_frontend-1.3.26-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / omnichar_frontend-1.3.26.tar.gz

Download URL omnichar_frontend-1.3.26.tar.gz
Size 568.5 kB
Tags Source
SHA-256 checksum
How to use checksums
0401fe7a3c62f2906d813a9a098540986639e258b81e83d892fe1c3b6762f46e
BLAKE2b-256 checksum
How to use checksums
94cd990ab8b2d5d62db0dbbf0405e7f410e2aa0010fefe024ce28aef635dfd93
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 25, 2026.

Transparency log

Release files / omnichar_frontend-1.3.26-py3-none-any.whl

Download URL omnichar_frontend-1.3.26-py3-none-any.whl
Size 567.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
50a85794f05124a5f7123903c2074fa793df51333bf5941dc80c7e70042bfdfa
BLAKE2b-256 checksum
How to use checksums
df6b95c7c13c5f3bfbef8afc57649dfdc486fbbaadd8aec5f4e42336e22ef5d7
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 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.3.26 This release

2 release files

1.3.25

2 release files

1.3.24

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page