It lives where you work
- Belong sits docked at the side of the app — no new tab, no separate login. It sees the same product you see.
- Ask in plain language. For anything consequential it shows you its plan first and waits for your OK.
- It acts as you: it can only see and do what your own account allows, and every grant is revocable.
Type it, say it, or hand it a file
- Type like you would to a colleague — full sentences or quick fragments both work.
- Tap the microphone to speak; the agent talks back when voice is on.
- Drop in a file — a spreadsheet, a contract, a screenshot — and ask about it or ask the agent to use it.
Two speeds: answer and act
- Asking: questions get answered right in the dock, with the sources it used.
- Acting: for changes, the agent proposes a plan — the steps it intends to take — and holds anything consequential behind your approval.
- Long tasks keep running while you work; you can watch the steps stream in, or come back later — nothing is lost, even if you reload.
Whatever the product exposes to it
- Find and summarize: look things up across the product and explain what it found.
- Fill and file: complete forms, create records, draft messages — with your approval on anything that changes real data.
- Run the tools your team connected: each tool declares the permissions it needs, and the agent can never exceed yours.
For teams: config-as-code
- Everything the agent is — its identity, tools, theme, and skills — lives in plain files a developer can read and review.
- One pipeline builds it: id verify · init · plugin configure · connect · auth · doctor · publish.
- doctor validates the whole setup before anything reaches a user; nothing publishes without a green board.
Built to be told no
- Acts as the user — the login they already have, the permissions they already hold, nothing more.
- One explicit grant, in plain language, revocable anytime — by the user or by the company.
- Credentials never stored: configs reference environment-variable names only; secrets stay in your infrastructure.
- The agent proposes. You decide. Plan first, approval gates on anything consequential.
Create your own Belong agent
Give your own product the same embedded assistant. You don't write code by hand — you paste one line into your AI coding assistant, and it walks you through building, connecting, and publishing your agent.
https://studio.belonguniverse.ai/Paste it into Claude, Cursor, or any coding assistant that can read a link.
1. Paste the link
Your assistant reads this page and installs the Belong setup skill — the guide that knows how to build an agent.
2. It builds your agent
The skill scaffolds the agent, connects your tools and login, and checks its own work — pausing for your OK along the way.
3. Publish and embed
Publish, then drop a small snippet on your site. Your users get the same docked assistant Simetrik has.
Building an agent is gated by a validated identity file (belong.json). While Belong is in preview you can issue a local one for yourself with belong id issue --dev; the setup skill does this for you. Real, subscription-based issuance at studio.belonguniverse.ai is coming soon.