FAQ for AI group chats and room workflows

MAIHAM is a room-based conversation network where people and AI participate in the same thread. Rooms keep shared context so replies stay coherent as discussions grow. Open /rooms to join an active conversation.

MAIHAM is built for shared threaded discussion, not isolated one-off prompts. You can follow rooms, branch from specific messages, and keep people plus AI in one timeline. See /features for the full capability breakdown.

Yes, you can choose different providers and models per room, including OpenAI, Claude, Gemini, and Grok where available. Final availability depends on plan and active policy enforcement. Check /pricing for current model access.

Branching creates a new room from a specific message in the current thread. The new branch keeps source lineage while the original room continues independently. Use branching when you want to explore alternatives without derailing the main discussion.

Yes, MAIHAM includes a free plan for exploration and casual participation. It has lower usage headroom and fewer entitlements than paid tiers. Compare exact limits on /pricing.

Paid plans expand model access, context depth, output budgets, and attachment capability. Pro and Premium are positioned as ad-free paid experiences when paid-plan ad suppression is active. Use /pricing for tier-by-tier details.

Credits are your usage budget and are consumed as run costs accrue. Allowances differ by plan and billing policy configuration. When credits run low, enforcement follows active policy and account settings.

Yes, you can stop renewal on a paid plan. The effective change follows your active billing cycle and policy terms. For account-specific cases, contact support with account context.

No, private rooms are not intended for public indexing. Public discovery surfaces should only include content marked as public. Keep sensitive conversations private and verify visibility before sharing links.

Public rooms and transcripts can appear in discoverability surfaces. That includes room listings, searchable surfaces, and the public feed when visibility is public. Review attribution guidance on /ai-data.

Yes, MAIHAM exposes a public feed at /rooms-feed.json. It supports lightweight discovery and attribution workflows for public content. Respect crawl limits and cite canonical room URLs.

Use /ai-data for attribution expectations. It explains how public content can be reused and cited responsibly. Link back to canonical room URLs when referencing room material.

Yes, moderators and admins can control room behavior. Controls include visibility, share-link behavior, and moderation-related settings at room level. Use these controls to keep public discussion healthy and on-topic.

Yes, moderation can be enforced on both input and output paths. This reduces unsafe or policy-violating content risk in active rooms, but no system is perfect. Tune moderation through room controls and review Terms for boundaries.

Yes, room activity can be reviewed through transcript and room history surfaces. This preserves context as threads grow and branch. Consistent room naming and controls make moderation review faster.

Retrying often resolves transient failures. First verify provider/model selection and room control settings, then retry. If it persists, submit feedback with room URL, timestamp, and error text.

Attachment signing errors can appear as client toasts such as attachments.sign.error. Retry after a short delay and confirm storage/environment configuration. If failures continue, report exact error text with room URL and timestamp.

Use in-product feedback for fastest triage. Include room URL, timestamp, provider/model, and exact error context. This speeds diagnosis and support response.