Burmese
Company brain (shared) and personal brain (private) for AI assistants - knowledge with access control.
Last verified:
What is Burmese?
Burmese is an AI-powered knowledge assistant that maintains a shared 'company brain' (team knowledge with provenance) and private 'personal brain' (individual-only knowledge) for each user. It integrates with development tools like Claude Code, Cursor, GitHub, Slack, and other platforms, and runs across desktop (macOS), web, terminal, and mobile (iOS/Android coming soon) with a unified interface for querying from any device.
Burmese pricing
Pricing model: Freemium
Burmese pros
- Dual-brain architecture separates company knowledge from private individual knowledge with permission controls
- Multi-platform access including desktop, web, terminal, and upcoming native mobile apps
- Integrates with major development and communication tools (Claude Code, Cursor, GitHub, Slack, Gmail, Notion, etc.)
- Real-time visual feedback on agent activity through customizable animated companion designs
- Cross-device consistency—same question answered on desktop, mobile, or terminal with contextual awareness
Burmese cons
- Native iOS and Android apps are not yet available ('coming soon')
- Conversational interface still in development ('Someone to talk to' not shipped yet)
- Requires setup with specific integrated tools/platforms for full functionality
Frequently asked questions about Burmese
What's the difference between company brain and personal brain?
Company brain is shared knowledge accessible to permitted team members with full provenance tracking. Personal brain is private to each individual—not queryable by managers or founders.
Can I access Burmese from my phone?
Yes, via web browser by scanning a code from your desktop (connects over your own network or remotely). Native iOS and Android apps are coming soon.
What platforms does it integrate with?
Connected on arrival: Claude Code, Codex, Cursor, opencode. Opt-in integrations: GitHub, Notion, Gmail, Google Calendar, Slack, WhatsApp, and Meet notes.
How does it track decisions?
It reads from integrated sources (Slack threads, emails, calendar attendees, meeting notes) to attach source and date to company decisions, preventing misremembering what was agreed.