You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop AbstractGateway's compatibility-only extras (http/server/etc) so the supported install surface is just base, apple, and gpu. Update docs + install-profile tests and regenerate llms-full.
Copy file name to clipboardExpand all lines: README.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,9 +200,6 @@ pip install abstractgateway
200
200
201
201
-`abstractgateway[apple]`: full native macOS Python profile with Apple-local engines and all non-NVIDIA framework capabilities
202
202
-`abstractgateway[gpu]`: full local GPU profile with vLLM/HuggingFace, local Diffusers image generation, local voice engines, music, and KG memory; this is also the NVIDIA Docker install profile
203
-
-`abstractgateway[server]`, `[http]`, `[multimodal]`, `[memory]`, `[voice]`, `[vision]`, and `[all]`: compatibility aliases; the base package already includes the remote-light server stack
204
-
-`abstractgateway[server-nvidia]`: compatibility alias for the GPU profile used by older NVIDIA Docker commands
205
-
-`abstractgateway[telegram]` and `[visualflow]`: compatibility aliases; Telegram bridge and VisualFlow publishing use base install dependencies
Copy file name to clipboardExpand all lines: docs/configuration.md
+8-12Lines changed: 8 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,6 @@ compatibility (runs bundles produced by AbstractFlow; does not require the `abst
12
12
Optional extras (see `pyproject.toml`):
13
13
-`abstractgateway[apple]`: full native macOS Python profile with Apple-local engines and all non-NVIDIA framework capabilities; this is for native macOS, not Docker
14
14
-`abstractgateway[gpu]`: full native/container GPU profile with local GPU engines and all relevant framework capabilities; the NVIDIA Docker image uses this profile
15
-
-`abstractgateway[http]`, `[server]`, `[multimodal]`, `[memory]`, `[voice]`, `[vision]`, `[all]`: compatibility aliases because the base install now includes the remote-light server stack
16
-
-`abstractgateway[server-nvidia]`: compatibility alias for the GPU profile used by older NVIDIA Docker commands
17
-
-`abstractgateway[visualflow]`: deprecated compatibility alias (VisualFlow directory mode was removed; does nothing)
18
-
-`abstractgateway[telegram]`: compatibility alias; Telegram bridge support uses base install dependencies
19
15
-`abstractgateway[docs]`: MkDocs site tooling
20
16
-`abstractgateway[dev]`: local dev/test deps
21
17
@@ -200,14 +196,14 @@ and hybrid runtimes report `prompt_cache_local_only`.
200
196
201
197
### Multimodal provider/plugin controls
202
198
203
-
The `server`, `multimodal`, and `all` extras install the lightweight AbstractCore
204
-
plugin surface for generated images, generated videos, generated voice, STT, and music
205
-
capabilities. Voice generation, transcription, generated images, and generated
206
-
music have direct Gateway endpoints; generated images are also exposed through
207
-
Runtime/Core workflows and through `POST /api/gateway/runs/{run_id}/images/generate`
208
-
and `POST /api/gateway/runs/{run_id}/images/edit` when a Runtime/Core image
209
-
backend is configured or provider/model are supplied on the request. Local
210
-
heavy engines remain explicit opt-ins in the provider packages.
199
+
The base install already includes the Gateway HTTP/SSE server and the Runtime
200
+
multimodal integration layer. Direct Gateway routes for voice/audio, image/video,
201
+
and music become available when the corresponding lower-layer capability
202
+
packages are installed on the gateway host (or when Gateway is configured to
203
+
proxy to a remote AbstractCore server).
204
+
205
+
Local heavy engines remain explicit opt-ins in the provider packages; Gateway
206
+
does not implicitly install them.
211
207
212
208
-`output.text` capability route: default text model for bundle LLM nodes
213
209
-`OPENAI_COMPATIBLE_BASE_URL` / `OPENAI_COMPATIBLE_API_KEY`: OpenAI-compatible text endpoint for AbstractCore providers
Copy file name to clipboardExpand all lines: llms-full.txt
+8-19Lines changed: 8 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -210,9 +210,6 @@ pip install abstractgateway
210
210
211
211
- `abstractgateway[apple]`: full native macOS Python profile with Apple-local engines and all non-NVIDIA framework capabilities
212
212
- `abstractgateway[gpu]`: full local GPU profile with vLLM/HuggingFace, local Diffusers image generation, local voice engines, music, and KG memory; this is also the NVIDIA Docker install profile
213
-
- `abstractgateway[server]`, `[http]`, `[multimodal]`, `[memory]`, `[voice]`, `[vision]`, and `[all]`: compatibility aliases; the base package already includes the remote-light server stack
214
-
- `abstractgateway[server-nvidia]`: compatibility alias for the GPU profile used by older NVIDIA Docker commands
215
-
- `abstractgateway[telegram]` and `[visualflow]`: compatibility aliases; Telegram bridge and VisualFlow publishing use base install dependencies
Compatibility extras such as `abstractgateway[http]`, `[server]`, `[memory]`,
361
-
`[multimodal]`, `[voice]`, `[vision]`, and `[all]` remain accepted, but the
362
-
base install already contains the remote-light server stack.
363
-
364
357
With the base install and a configured provider stack, Gateway can surface
365
358
run-scoped direct TTS, STT, image generation, image edit, and music generation
366
359
for higher apps through one shared capability contract.
@@ -1736,10 +1729,6 @@ compatibility (runs bundles produced by AbstractFlow; does not require the `abst
1736
1729
Optional extras (see `pyproject.toml`):
1737
1730
- `abstractgateway[apple]`: full native macOS Python profile with Apple-local engines and all non-NVIDIA framework capabilities; this is for native macOS, not Docker
1738
1731
- `abstractgateway[gpu]`: full native/container GPU profile with local GPU engines and all relevant framework capabilities; the NVIDIA Docker image uses this profile
1739
-
- `abstractgateway[http]`, `[server]`, `[multimodal]`, `[memory]`, `[voice]`, `[vision]`, `[all]`: compatibility aliases because the base install now includes the remote-light server stack
1740
-
- `abstractgateway[server-nvidia]`: compatibility alias for the GPU profile used by older NVIDIA Docker commands
1741
-
- `abstractgateway[visualflow]`: deprecated compatibility alias (VisualFlow directory mode was removed; does nothing)
1742
-
- `abstractgateway[telegram]`: compatibility alias; Telegram bridge support uses base install dependencies
1743
1732
- `abstractgateway[docs]`: MkDocs site tooling
1744
1733
- `abstractgateway[dev]`: local dev/test deps
1745
1734
@@ -1924,14 +1913,14 @@ and hybrid runtimes report `prompt_cache_local_only`.
1924
1913
1925
1914
### Multimodal provider/plugin controls
1926
1915
1927
-
The `server`, `multimodal`, and `all` extras install the lightweight AbstractCore
1928
-
plugin surface for generated images, generated videos, generated voice, STT, and music
1929
-
capabilities. Voice generation, transcription, generated images, and generated
1930
-
music have direct Gateway endpoints; generated images are also exposed through
1931
-
Runtime/Core workflows and through `POST /api/gateway/runs/{run_id}/images/generate`
1932
-
and `POST /api/gateway/runs/{run_id}/images/edit` when a Runtime/Core image
1933
-
backend is configured or provider/model are supplied on the request. Local
1934
-
heavy engines remain explicit opt-ins in the provider packages.
1916
+
The base install already includes the Gateway HTTP/SSE server and the Runtime
1917
+
multimodal integration layer. Direct Gateway routes for voice/audio, image/video,
1918
+
and music become available when the corresponding lower-layer capability
1919
+
packages are installed on the gateway host (or when Gateway is configured to
1920
+
proxy to a remote AbstractCore server).
1921
+
1922
+
Local heavy engines remain explicit opt-ins in the provider packages; Gateway
1923
+
does not implicitly install them.
1935
1924
1936
1925
- `output.text` capability route: default text model for bundle LLM nodes
1937
1926
- `OPENAI_COMPATIBLE_BASE_URL` / `OPENAI_COMPATIBLE_API_KEY`: OpenAI-compatible text endpoint for AbstractCore providers
0 commit comments