28 行
1.3 KiB
Markdown
28 行
1.3 KiB
Markdown
# AstrBot chat extensibility probe
|
|
|
|
Date: 2026-07-20
|
|
|
|
## Scope
|
|
|
|
Non-destructive connectivity and response-shape verification for the two supplied AstrBot test containers. API keys and complete response bodies are intentionally omitted. No chat message was sent and no configuration was changed.
|
|
|
|
## Results
|
|
|
|
| Target | Sessions | Configs | File upload |
|
|
| --- | --- | --- | --- |
|
|
| Container 1 (:26285) | status=ok; existing webchat session returned | status=ok; one default config | POST /api/v1/file returned status=ok and an attachment_id |
|
|
| Container 2 (:26385) | status=ok; no sessions for the probe username | status=ok; config list returned | not uploaded during this probe |
|
|
|
|
## Upload response shape
|
|
|
|
The first container returned an envelope with these data keys:
|
|
|
|
- attachment_id
|
|
- filename
|
|
- type
|
|
|
|
The adapter already accepts attachment_id and preserves the client-side filename, MIME type, and byte size in normalized attachment metadata.
|
|
|
|
## Implementation consequence
|
|
|
|
The current capability and upload IPC contract matches the observed response shape. Model selection is represented by AstrBot config IDs; the first container exposes the default config and the second exposes a named workflow config. End-to-end image rendering and model behavior still require a real chat send with a user-approved test message.
|