The AI teammate that
답은 여러분이 직접 캡처한 트래픽에서 — 추측이 아닙니다. 대시보드, Telegram, 채팅에서 여러분을 기억합니다.
Ask, understand,
캡처된 트래픽을 답변과, 역할에 묶인 행동으로 바꿉니다.
- RBAC 범위 제한
- 확인 게이트
- 시크릿 마스킹
추측이 아닌 근거 기반
“이 앱은 어떻게 로그인하나요?”라고 물으면 여러분의 캐처에서 바로 실제 흐름을 보여줍니다. 시크릿이 가려진, 실행 가능한 재현 코드까지 함께. 답에는 항상 근거가 따라옵니다.
어디서든 여러분을 기억합니다
한 번만 가르치면 모든 표면에서 따라옵니다 — 대시보드, Telegram, MCP, 터미널. 지우고 싶으면 "그거 잊어버려" 한마디면 됩니다.
샐 수 없는 팀 두뇌
팀 지식은 엄격한 PII 필터와 사람의 검토 큐를 거쳐 모두의 대화에서 추출됩니다. 개인 사실은 팀 저장소와 아키텍처 차원에서 분리되어 있어, 설계상 경계를 넘을 수 없습니다.
필요할 때 부르는 전문가
튜닝된 페르소나를 API의 서비스 그룹에 연결하면, 해당 트래픽이 포커스에 들어올 때마다 BusyBro가 자동으로 그 역할을 맡습니다. 결제 전문가는 결제 트래픽에 나타납니다 — 부탁하지 않아도.
증명 가능한 정직함
활동 추적은 답변 뒤에서 어떤 도구가 실행됐는지 정확히 보여주고, BusyBro의 모든 쓰기는 플랫폼 감사 로그에 기록됩니다. 확인할 수 있기에 신뢰할 수 있습니다.
모델은 여러분의 선택
기본 Anthropic 모델을 쓰거나, OpenAI 호환 엔드포인트로 향하게 하거나, 로컬 모델을 가져오세요. 키는 암호화된 볼트에 보관되고, 메모리는 전환 후에도 유지됩니다.
Ask once,
One brain behind Telegram, the iOS app, the terminal, and your MCP-connected agents — same account, same memory, same rules.
Link once
01On Telegram, /login pairs the bot with your account via a short-lived code — no link, no LLM call at all. The iOS app and the bmc terminal already speak as you.
Ask in plain language
02Name a device by its name, PAC port, or URL; name a host; describe a bug. Attach a screenshot or a PDF on Telegram and it reads those too.
Tools, not vibes
03Answers come from real tool calls over your captured data — drawn from the same registry the dashboard and the MCP server consume — never from guessing at your traffic.
You hold the pen
04Reads flow at your role. Anything that changes state stops and shows you the exact payload first — an inline Confirm on Telegram, an action card elsewhere.
Autonomy with a
Every gate is re-checked at execution time, server-side — the model can neither grant itself a role nor press its own Confirm button.
| You ask it to… | What actually happens | Enforced by |
|---|---|---|
| Read traffic | Owner-scoped by default: it inspects your own devices' captures. Reading wider requires the devices-view capability on your real role. | Row-level security plus your role — the same checks as the dashboard. |
| Change something | It stops and shows the exact change — the script body, the settings diff, the delete scope — and waits for your explicit approval. | A single-use, server-side confirmation the model cannot forge or replay. |
| Do something admin-grade | Admin-only tools re-resolve your current role at the moment of execution — not when you asked, and not from the chat context. | Capability and admin gates re-applied at run time, defense in depth. |
| Touch the database directly | It can't. Raw database and broadcast primitives are excluded from the free-text model entirely — no dashboard screen grants raw SQL, so neither does your mate. | A code-level denylist between the model and the tool registry. |
| Handle a secret | Captured tokens and cookies are treated as secrets in its answers, and provider API keys are referenced by name only — the value never sits in chat-readable settings. | The encrypted vault behind one audited decrypt boundary. |
| Anything at all | Every write, every denial, and every error is recorded with the surface, your role, and whether a real human tap approved it. | The platform audit trail — the same one the dashboard tails live. |
Things people
Each ask maps to a real, bounded tool — not a fuzzy summary of rows it never read.
“How does this app's login flow work?”
It deep-inspects your captured traffic for that host — the auth calls, token refresh, required headers, payload shapes — and hands back repro code with credentials treated as secrets.
“What has my iPhone been doing for the last hour?”
A bounded aggregation answers with top hosts and request counts — never a raw scan of your rows — then drills into the noisy host when you ask it to.
“Clear the noise from that analytics host”
A targeted, filtered delete — and because it mutates your data, it first shows the exact scope it would remove and waits for your confirmation.
The questions sceptics
Can it act without asking me?
Reads run freely at your role. Every write stops for an explicit confirmation — and even if you auto-approve a tool for a thread, destructive and admin-grade tools always still ask.
Does it see my whole database?
No. Raw database primitives are excluded from the model entirely, and every tool it can call runs through the same row-level security and role checks as the dashboard.
What does it remember, and can I erase it?
Personal memory is owner-scoped rows you can list, search, and delete — say 'forget that' or send /forget on Telegram to wipe it. The background memory writer can be switched off for your account.
Can my private details leak into the shared team brain?
The team store is a separate table with no user column at all, a deterministic code filter rejects names, emails, IPs, paths and token-shaped strings before anything is stored, and every candidate waits in a review queue before it becomes recallable.
Which model answers — and can we run our own?
Anthropic Claude by default, configurable per surface. Admins can point the fleet at any OpenAI-compatible endpoint or a local model — the key stays in the encrypted vault — and on non-frontier providers the tool surface automatically narrows to a read-only core.
Is there a record of what it did?
Yes — every write, denial, and error lands in the platform audit trail with the surface it came from, the role that ran it, and whether a real human tap confirmed it.
Say hi to
busymate.ai를 열거나, Telegram에서 @busybrobot에게 메시지를 보내 계정을 연결하세요.