Repository navigation

Issues

New issue

omadia Facilitator — agent that moderates group chats to a defined outcome (+ Conductor JIT/ephemeral workflows & Core group primitives)
#330 · iret77 opened on Jun 18, 2026
4
Interactive product tour on omadia.ai (no install)
#337 · iret77 opened on Jun 18, 2026
5

Telegram bot and admin UI texts say "byte5 Harness" instead of omadia, and the unpaired-user refusal shows literal backslashes ("verbunden\.", "Pairing\-Link\.")
byte5ai/omadia#2005 · opened on Nov 11, 2026
Pressing START in the Telegram bot never shows the greeting: a bare /start is refused as unpaired (pairing policy) or sent to the model (open policy)
byte5ai/omadia#2004 · opened on Nov 11, 2026
Telegram answers repeat the AI disclosure line on almost every turn: earlier answers are replayed to the model with the line included, and the model starts writing it itself
byte5ai/omadia#2003 · opened on Nov 11, 2026
Telegram channel logs its admin token in clear text on first activation and tells operators to grep the log for it, while core's env bootstrap logs only a fingerprint of the same token
byte5ai/omadia#2002 · opened on Nov 11, 2026
Telegram chats never appear in /operator/channels and cannot be bound to an agent from the UI, although the page says Telegram reports its keys there
byte5ai/omadia#2001 · opened on Nov 11, 2026
Telegram bot shows raw internal error messages (provider and Telegram API errors) to users in its apology text
byte5ai/omadia#2000 · opened on Nov 11, 2026
Telegram: files the bot cannot read (PDF, Office, HEIC, images over 5 MB sent as a file, voice, stickers) are dropped without a reason, or answered with "I can only handle text and images" even when the file was an image
byte5ai/omadia#1999 · opened on Nov 11, 2026
Telegram DM policy fails open when the field holds an unknown value like Pairing or is cleared, so anyone can chat with the bot
byte5ai/omadia#1998 · opened on Nov 11, 2026
Telegram channel: in a group, @-mentions never reach the bot while BotFather privacy mode is on (the default), but the group activation message and the setup guide tell users to @-mention it
byte5ai/omadia#1997 · opened on Nov 11, 2026
Telegram bot replies "Ich kann derzeit nur Text-Nachrichten und Bilder verarbeiten" to service messages and stickers before any access check: in non-activated groups, to unpaired DM users and under dm_policy=disabled
byte5ai/omadia#1996 · opened on Nov 11, 2026
Telegram pairing says "connected as <name>" but links the chat to no omadia user: the identity ID is free text and every turn still runs as the Telegram user
byte5ai/omadia#1995 · opened on Nov 11, 2026
Telegram and Teams turns carry no channel kind: receipts get channel = NULL, telegram=/teams= disclosure overrides never apply, and /health reports them as effective
byte5ai/omadia#1994 · opened on Nov 11, 2026
Telegram: generated Excel/Word files never arrive and diagrams go missing with the default base URL, while the answer says "here is your file"
byte5ai/omadia#1993 · opened on Nov 11, 2026
Agent answers in German even when the user writes in English: the system prompt hard-codes German and there is no language setting
byte5ai/omadia#1992 · opened on Nov 11, 2026
Telegram: inline-keyboard button clicks skip the pairing and group-activation checks, so a revoked user or a deactivated group still gets answers
byte5ai/omadia#1991 · opened on Nov 11, 2026
Telegram webhook mode never receives messages: core answers every Telegram delivery to /api/telegram/webhook with 401 auth.missing
byte5ai/omadia#1990 · opened on Nov 11, 2026
Telegram answers longer than 4096 characters are never delivered: the user gets a "message is too long" error instead of the answer
byte5ai/omadia#1989 · opened on Nov 11, 2026
Docs and package metadata are out of date: docx provenance category, diagram/document URL paths, six smoke:* scripts, "Proprietary" manifest license, Web Search setup texts
byte5ai/omadia#1988 · opened on Nov 11, 2026
transcribe_recording says the full transcript is in the session log, but the session log keeps only the first 1,500 characters of each entry
byte5ai/omadia#1987 · opened on Nov 11, 2026
Generated Office files and diagrams are never deleted: chat, dataset and user deletion and the memory purge leave them in the bucket
byte5ai/omadia#1986 · opened on Nov 11, 2026
OpenAI transcription and embedding adapters declare a placeholder instead of a host in network.outbound and bypass ctx.http
byte5ai/omadia#1984 · opened on Nov 11, 2026
Under Privacy Shield, transcribe_recording hides the transcript from the model, so the agent cannot summarize or answer questions about the recording it just transcribed
byte5ai/omadia#1985 · opened on Nov 11, 2026
Transcripts from transcribe_recording re-enter later turns as the uploader's own messages, although the admin page says they are treated as untrusted input
byte5ai/omadia#1983 · opened on Nov 11, 2026
Transcription provider page shows an unconfigured adapter as "active provider" by raw id, and transcribe_recording then says no provider is installed
byte5ai/omadia#1981 · opened on Nov 11, 2026
create_docx ignores line breaks inside text, and create_xlsx fails on the sheet name "History"
byte5ai/omadia#1982 · opened on Nov 11, 2026

Navigation Menu

Repository navigation

Issues

Issues

Telegram bot and admin UI texts say "byte5 Harness" instead of omadia, and the unpaired-user refusal shows literal backslashes ("verbunden\.", "Pairing\-Link\.")

Pressing START in the Telegram bot never shows the greeting: a bare `/start` is refused as unpaired (pairing policy) or sent to the model (open policy)

Telegram answers repeat the AI disclosure line on almost every turn: earlier answers are replayed to the model with the line included, and the model starts writing it itself

Telegram channel logs its admin token in clear text on first activation and tells operators to grep the log for it, while core's env bootstrap logs only a fingerprint of the same token

Telegram chats never appear in `/operator/channels` and cannot be bound to an agent from the UI, although the page says Telegram reports its keys there

Telegram bot shows raw internal error messages (provider and Telegram API errors) to users in its apology text

Telegram: files the bot cannot read (PDF, Office, HEIC, images over 5 MB sent as a file, voice, stickers) are dropped without a reason, or answered with "I can only handle text and images" even when the file was an image

Telegram DM policy fails open when the field holds an unknown value like `Pairing` or is cleared, so anyone can chat with the bot

Telegram channel: in a group, @-mentions never reach the bot while BotFather privacy mode is on (the default), but the group activation message and the setup guide tell users to @-mention it

Telegram bot replies "Ich kann derzeit nur Text-Nachrichten und Bilder verarbeiten" to service messages and stickers before any access check: in non-activated groups, to unpaired DM users and under `dm_policy=disabled`

Telegram pairing says "connected as <name>" but links the chat to no omadia user: the identity ID is free text and every turn still runs as the Telegram user

Telegram and Teams turns carry no channel kind: receipts get `channel = NULL`, `telegram=`/`teams=` disclosure overrides never apply, and `/health` reports them as effective

Telegram: generated Excel/Word files never arrive and diagrams go missing with the default base URL, while the answer says "here is your file"

Agent answers in German even when the user writes in English: the system prompt hard-codes German and there is no language setting

Telegram: inline-keyboard button clicks skip the pairing and group-activation checks, so a revoked user or a deactivated group still gets answers

Telegram webhook mode never receives messages: core answers every Telegram delivery to `/api/telegram/webhook` with 401 `auth.missing`

Telegram answers longer than 4096 characters are never delivered: the user gets a "message is too long" error instead of the answer

Docs and package metadata are out of date: docx provenance `category`, diagram/document URL paths, six `smoke:*` scripts, "Proprietary" manifest license, Web Search setup texts

`transcribe_recording` says the full transcript is in the session log, but the session log keeps only the first 1,500 characters of each entry

Generated Office files and diagrams are never deleted: chat, dataset and user deletion and the memory purge leave them in the bucket

OpenAI transcription and embedding adapters declare a placeholder instead of a host in `network.outbound` and bypass `ctx.http`

Under Privacy Shield, `transcribe_recording` hides the transcript from the model, so the agent cannot summarize or answer questions about the recording it just transcribed

Transcripts from `transcribe_recording` re-enter later turns as the uploader's own messages, although the admin page says they are treated as untrusted input

Transcription provider page shows an unconfigured adapter as "active provider" by raw id, and `transcribe_recording` then says no provider is installed

`create_docx` ignores line breaks inside text, and `create_xlsx` fails on the sheet name "History"