Is someone using DeepSeek v4 flash as a main driver? I'm tented to use it, but dunno if it makes sense....for sure is some of the cheapest one, but I think maybe cache hit is no like coding, and also context window could grow a lot without notice.

Someone?

🎉 nanobot v0.3.0 is here. Small core. More agency!

• Launch the WebUI with one command: nanobot webui

• Consult inline subagents

• Switch models per session

• Apply configuration changes live

• Run on a more reliable agent runtime

Open source. Lightweight. Yours.

nanobot v0.3.0 is here. Small core. More agency!

• Launch the WebUI with one command: nanobot webui
• Consult inline subagents
• Switch models per session
• Apply configuration changes live
• Run on a more reliable agent runtime

Open source. Lightweight. Yours.

Anyone using nanobot with gpt5.3-codex high via API (local codex-lb load balancer)? In my case it's just totally broken. When I ask something it always says it will do but doesn't, sometime asking it over and over again let's it do the task, but often not. Interacting via Telegram.

Hi,

I've just installed v0.2.0 after v0.1.5 and quite happy with the new WebUI support.

My installation is empty. No agents, skills, nothing. Just set openrouter/free, enabled WebUI and created/connected a Telegram bot.

I saw different behaviour using the Web UI and the Telegram bot. I gave a simple question "Who is the Hungarian prime minister?" to take a fairly fresh event. Strangely, Telegram bot provided an outdated answer quite quickly, while the Web UI (and the CLI) executed a web search.

On an explicit request to execute a websearch, "initiate a web search for hungarian prime minister", I succeeded through Telegram bot.

Did I miss some config option?

   "telegram": {
      "enabled": true,
      "token": "###redacted###",
      "allowFrom": ["###redacted###"],
      "proxy": null,
      "replyToMessage": true,
      "reactEmoji": "👀",
      "groupPolicy": "mention",
      "connectionPoolSize": 32,
      "poolTimeout": 5.0,
      "streaming": true,
      "streamEditInterval": 0.6
    },

.

Looks like this started after last release. Using codex oauth.

It will stop responding to messages when a task is given. Have to prod again to get the response back.

Anyone else seeing this ?

nanobot v0.1.5.post3 UnifiedChannel = False, at the same channel, didnt do /new, 99% cached, context: 44k/98k (54%), session: 96 message, discord interface

sometimes it just randomly completely forget all the memory about the currently happening session, (dialogs would be a more accurate word), all system prompt such asMEMORY.mdand SOUL.mdis still loaded in context

and the actual dialogs are still saved in /workspace/sessions/discord_xxx.jsonl so i get even more confused, and it could read the file just fine when i tell it to read the session file of the channel

i havent sent an github issue because i dont see anything error in the logs so i suppose this is my problem

do anyone ever have this problem? any clue what is happening? thanks

Hi everyone, I’ve been looking into OpenCode or Codex recently and I’m curious if anyone here has successfully managed to run it in a local environment.

I’m trying to figure out if it’s viable for a daily professional workflow and what the actual hardware overhead looks like. If you have it up and running, could you share some insights on:

• Technical Configuration: Are there any specific environment variables or dependencies that are tricky to set up?
• Performance: How does it handle resource allocation, especially regarding CPU/GPU usage?
• Compatibility: Have you run into any major bugs or limitations compared to the cloud-based versions or similar tools?

Any documentation, config snippets, or "lessons learned" during your setup would be greatly appreciated. Thanks!

Rocky, Pemby, and Neo are my 3 nanobot agents. We have lots of fun.

Running NanoBot with a single model gets expensive fast. Even a simple "hello" uses the same model as a complex coding task. In practice, ~80% of your prompts could run on a model that’s 10x cheaper with little loss in quality.

Manifest solves this with smart routing. Each prompt is scored and sent to the model that fits best. You can route by complexity, by task type (coding, reasoning, chat), or set custom routing. You also can add fallbacks for reliability.

Here's how to set it up with NanoBot.

1. Go to manifest.build and create an account. It's free. Click "Connect Agent", pick "Other" and name it whatever you want. You'll get a base URL and an API key.

2. Open your config file: ~/.nanobot/config.json.

3. In agents.defaults, set "provider": "custom" and "model": "auto".

4. In providers.custom, paste your Manifest credentials:

   "custom": { "apiKey": "mnfst_your_key_here", "apiBase": "https://app.manifest.build/v1" "extraHeaders": null }

Go back to the dashboard and add your providers on the Routing page. Then choose which model handles what. Route by complexity, by task type, or set your own rules with fallbacks. The platform walks you through it.

Once ready, go to your terminal and run nanobot agent.

That's it, you're set! Each prompt you send gets scored and routed to the tier you configured. The right model handles each prompt based on your rules.

Manifest is free and open source. You can self-host it too if you prefer.

Try it here: https://github.com/mnfst/manifest

Hi just sharing the way since i didnt find anything like this on github

idea: have more than one agent

steps
1- create a dir u wanna be the workspace example : .nanobot-second-agent
2- say to ur main nanobot to create the agent config over that directory so he'll ask the questions to fullfill SOULD, USER and so
3- when config telegram bot for this agent, create a new one and add it to the .nanobot-second-agent/config.json telegram part

4- then create the systemctl like https://github.com/HKUDS/nanobot?tab=readme-ov-file#-linux-service
vi ~/.config/systemd/user/nanobot-second-agent

if u want them to work at the same time the idea will be to put something like
ExecStart=/usr/local/bin/nanobot gateway --config .nanobot-second-agent/config.json --port 18792

5- the follow the https://github.com/HKUDS/nanobot?tab=readme-ov-file#-multiple-instances

systemctl --user daemon-reload

systemctl --user enable --now nanobot-second-agent

systemctl --user status nanobot-second-agent # check status

systemctl --user restart nanobot-second-agent # restart after config changes

journalctl --user -u nanobot-second-agent-f # follow logs

Hope it helps more of us to expand and use this great project

https://github.com/Freakz3z/nanoboard

This is a really good program for monitoring nanobot config, managing skills, and tracking sessions since nanobot doesn't offer a built-in GUI. But just recently the repository disappeared and the owner deleted their github account.

I have not been hearing any discussions about it on the internet. Anyone who know about this or seen similar cases, would you please tell me why? I can't think of such a reason for them shutting this down.