π BUGS & UX ISSUES & Leftovers
- [ ] UX for command responses during scalability
- [x] Remove bot command doesnβt look good and big in help Command menu
- [ ] Dropping caller-provided groupId that doesn't match session-derived group context
- [ ] UX can be improved for long running tasks background jobs, with some message or something which works in real time!
- [x] Reactions UX in groups - styling needs improvement
- [x] Bot segregation in groups - inbound messages being shared between bots (separate message routing)
- [x] Provider request fails when running skills
- [x] Some features not working in private groups (comprehensive testing needed)
- [ ] First test and publish to clawhub current and test on windows : skills, cli, gorup chat, non native skills, intehgaret same ai and stt and everything gh etc and test properly
- [ ] Docs needs to stil be clear and much better
- [ ] Add cron instcustions either in house or add in docs so it works out of the box
- [ ] Merge witch current main and sync local and dodaa08βs main as well
- [x] Test and review you find anything hardcoded like some model, file, which is dynamic per os and creates an issues test proply on windows integarte the same setup there.
- [ ] remove dead code for email runner once confirmed
- [ ] in runCronCommand, resolve the agent via readBindingsForAccount(ctx.account.accountId) (channel.ts:654 already does this for !status) and use that agentId for --agent, falling back to rc-${accountId} when unbound. That way !cron works whether the bot is bound to main or a dedicated agent. Want me to make that change?
- [ ] Fix your Email skill and use it well
- [ ] Check why all media files are stored locally on users machine ?
- [ ] "subsystem":"agent/embedded"} effective tool policy: dropping caller-provided groupId that does not match session-derived group context
- [ ] Handling cases for media if server url and CDN is diff