How the dog works.
Operator INU is a lightweight AI community operator for token projects. You give it verified project facts, rules, links, and a BotFather bot. It handles repetitive questions and content work, and routes unknowns back to humans instead of pretending to know.
Overview
The workflow is simple: load a token, create the agent profile, teach it approved knowledge, choose how strict it should be, then connect Telegram. The web workspace is your control panel; Telegram is where the agent works with the community.
Create an INU
Paste the Solana mint
INU looks up the active DexScreener pair and imports available name, symbol, links, and market data.
Complete the project profile
Add the official website, X, Telegram, project description, preferred personality, and operating mode.
Deploy
The browser stores the private agent key locally so the workspace can manage that INU.
Training
Training is rule-based and explicit. Enter a trigger such as staking or dev wallet, then provide the approved answer. When a community question matches those terms, INU uses your answer.
Good training rules
- Use factual language.
- Include official links when useful.
- Do not train speculative price promises.
- Write the answer exactly how you want the community to receive it.
Leash modes
Leashed
Very strict. Unknown questions are logged for a human and the bot avoids replying unless it has a verified answer.
Trained
Recommended default. INU answers project facts and trained rules, and tells the user when it has escalated an unknown.
Off Leash
Still refuses to fabricate facts, but responds more freely and conversationally around uncertainty.
Connect Telegram with BotFather
Create the bot
Open Telegram and message @BotFather. Run /newbot, choose a display name and username, and copy the token BotFather gives you.
Paste the token into Operator INU
In the workspace, open Put INU in Telegram and paste the BotFather token. Operator INU validates it with Telegram's getMe API.
Webhook installs automatically
After validation, Operator INU calls Telegram's setWebhook API and points the bot at your specific INU webhook URL.
Add the bot to your group
Add the new bot to the project Telegram group. If you want it to see normal messages in addition to explicit commands, adjust BotFather privacy settings as appropriate for your group.
What actually happens in Telegram?
Once the BotFather token is connected, Telegram sends new messages to your INU webhook. What the bot does next depends on the message and the leash mode.
In BotFather use /setprivacy, choose your bot, and select Disable. Otherwise Telegram usually sends the bot only commands, mentions, and replies rather than every normal group message.
Automatic answers
In Trained and Off Leash mode, INU automatically considers normal messages that look like questions or contain project terms such as CA, contract, website, Telegram, Twitter/X, price, liquidity, or “what is”. If it has a supported answer, it replies directly to that message.
Leashed mode
In Leashed mode, a normal unknown question is still processed and can create an escalation, but INU stays quiet rather than posting an uncertain answer into the group.
Commands
Commands are explicit and work regardless of the normal auto-answer flow: /inu status, /inu ca, /inu links, /inu recap, and /inu ask your question.
Example
A member writes wen staking?. Telegram sends it to INU. INU checks project facts and trained rules. If you trained a staking answer, it replies. If not, it records an escalation. In Trained mode it can tell the member the question needs a human answer; in Leashed mode it can stay silent and simply add the task to the Human Queue.
Telegram commands
/inu status shows operating mode and answer/escalation counts.
/inu ca returns the configured token mint.
/inu links returns configured official project links.
/inu recap creates a current activity recap.
/inu ask your question explicitly asks INU a project question.
Token watch
For projects with a configured Solana mint, INU refreshes DexScreener data periodically. It records notable liquidity and volume changes in the work ledger and can add a human task when a material move needs review.
Human escalation
Unknown questions enter the Human Queue. This is a core behavior, not an error. The goal is to make the agent useful without allowing it to invent official project information.
FAQ
Does INU answer every single Telegram message?
No. It responds to explicit INU commands and, when Privacy Mode is disabled, automatically evaluates question-like project messages. It is designed to avoid becoming a noisy spam bot.
Does it need admin rights in the Telegram group?
For basic question answering, no special admin power is required beyond being present and receiving messages. Future moderation features may require additional Telegram permissions.
What if somebody asks something INU was never taught?
INU checks the project profile, trained rules, and available project/market facts. If it still cannot support the answer, it escalates instead of inventing official information.
Can I change what it knows after the bot is already live?
Yes. Teach a new rule in the web workspace and the same trained knowledge is used by the connected Telegram bot.
Can I change tokens/projects?
Yes. Use Clear in the token loader to reset the current build form, or Start New Project from an active workspace. The current INU remains intact until you deploy another one.
Can several people manage the same INU?
Not yet. The MVP stores the agent owner key in the browser that created it. Team accounts and shared access are on the roadmap.
What happens if I clear browser storage?
In the current MVP, that browser can lose its local owner key. Account-based recovery is part of the planned authentication roadmap.
Does the community connect a wallet?
No. Community members do not need to connect a wallet to ask questions or interact with the Telegram bot.
Is this supposed to replace DexScreener, GMGN, or Axiom?
No. Those are analytics and trading products. Operator INU is an operator for repetitive community work, with token data used as context rather than as the product itself.
Where is the BotFather token stored?
The current MVP stores the Telegram connection server-side with the agent. Encrypted secret storage and account-level credential management are planned before a broader production rollout.
Roadmap
The current build proves the core operator loop: create an INU, teach it, test it, connect Telegram, and let it answer or escalate. The next phases turn that into a durable multi-user product.
Phase 1 · Make the operator stronger
- Richer website, docs, FAQ, whitepaper, and announcement ingestion.
- Semantic knowledge matching beyond simple trigger terms.
- Better Telegram conversation context, reply threading, rate limits, and anti-spam controls.
- Optional human approval for sensitive answers and scheduled content.
Phase 2 · Accounts and teams
- Email magic-link accounts rather than passwords.
- Multiple INUs per account and a real agent dashboard.
- Team invitations, roles, shared access, and recovery from any device.
- Encrypted BotFather-token storage, secret rotation, and safer credential management.
Phase 3 · More channels and automation
- Discord and additional community channels.
- Optional X publishing and approval workflows.
- Scheduled recaps, summaries, project alerts, and moderation workflows.
Phase 4 · Analytics and commercial product
- Question trends, unresolved-topic analytics, response quality, and knowledge gaps.
- Usage plans, billing, limits, and higher-capacity agent tiers.
- Exportable work ledger and team activity reporting.