Whether you are running a team, a small business, or an individual brand, are there any manual tasks that are wasting your time or requiring headcount to handle? If so, you can consider using CraftBot to automate them for you.
In our team, CraftBot has already taken over 30% of the manual workload, and we are still working to improve it further to the point where it can handle at least 70% of computer-based tasks.
Here are some of our use cases:
Team directory management: CraftBot helps us organize our team folder on GDrive. All we have to do is upload files into a temporary folder, where they are transferred, categorized, and sorted. CraftBot manages an MD file as an index when needed to retrieve data for us.
PM work: CraftBot helps us crawl issues in our GitHub repo and put them into a requirements page in Notion. Then, it keeps track of progress every day at 7 AM and 5 PM JST. No more copying and pasting one by one for me.
Lead sourcing: It helps us research leads that fit given requirements and compile a report of their contact information, reasons why they qualify, and more. Then, I reach out to the leads personally. (as people can sniff out AI and sometimes reject it) But of course, outreach can easily be automated using CraftBot with app integrations and channels.
These are just some of our own use-cases. I would love to hear yours and discuss how CraftBot can help you save time and cost, and create value for you and your team. Please leave a comment below!
CraftBot
For context, CraftBot is a self-hosted, proactive AI agent that can control a PC and take actions for you.
Today, most software, dashboards, apps, and subscription tools are static. When you need a new feature, you email the developer. If you are lucky, it ships six months later. If not, you may never hear back.
Therefore, we are introducing a new concept: 🌱Living UI🌱.
Living UI lets CraftBot build, import, and evolve custom software, apps, and dashboards directly inside the agent. The best part is that CraftBot stays context-aware of the Living UI’s state. It can read, write, update, and act on the interface directly.
Need a Kanban board with a general AI agent built in?
A CRM tailored exactly to your workflow?
A company dashboard your agent can actually operate?
You can spin all of these up as a Living UI. There are three ways to create one.
1. Build from scratch. Just describe what you want, and CraftBot generates the backend, API, and UI, then iterates with you.
2. Install from the marketplace. Use ready-to-use apps built by the community.
3. Import your existing project or GitHub repo. CraftBot converts it into a Living UI and integrates itself into it.
A Living UI is never finished. You can always modify it by telling CraftBot as your needs evolve. So instead of static tools, you get software that grows with you.
Try CraftBot and Living UI today. Build and customize your own Living UI, and stop relying on subscription tools that were never built to fit your needs perfectly. 🟠🌱
PicWish
@tham_yikfoong what happens if local machine runs out of storage for logs/memory? does it have a way to auto-prune old events?
CraftBot
@mohsinproduct There is a logic that prunes logs and MEMORY.md file with respect of their file size, but it does not consider the storage of the local machine! Generally they wouldn't exceed 50MB. Great question!
Flowtica Scribe
The agent era is reshaping the interface.
TUI is one direction, and it makes more sense for devs. But I don’t think agents remove the need for UI. Visual interfaces are still one of the best ways to compress state, context, and actions into something humans can understand quickly.
@CraftBot’s Living UI pushes this in a useful direction. The interface is no longer a fixed app you buy and adapt to. It becomes something the agent can build, read, modify, and operate based on the current task.
This points to a different software shape: not one-size-fits-all dashboards, but interfaces generated around the immediate job, the user, and even the current moment.
For agents, UI may become less of a destination and more of a live surface for action.
Looks amazing. How good is it with integrations? I am thinking about connecting it to some existing Notion databases to make use of it as internal dashboards.
CraftBot
@nelson_milla Notion is a part of our existing external integrations. You can easily set it up using OAuth or creating your own notion app.
You can ask the agent to create a living UI connected to your Notion account and fetch data in real-time in order to keep the living UI and notion continuously in sync.
quick question on the "Build from scratch" flow how does it handle complex API integrations? if i want my Living UI to pull data from multiple third-party tools, can CraftBot set up those connections too? checking the demo now.. @tham_yikfoong
CraftBot
@tham_yikfoong @vikramp7470 Craftbot has a list of external tools and we're continuously adding more. These external tools are provided to the agent with a simple interface. They allow proactive use and can be easily integrated into the Living UIs without any extra work. We are continuously adding more external tools but other than these, yes the agent can integrate any API needed (you might need to set up API keys though).
How CraftBot connects different Living UI seems really cool use of agentic workflows. So, I am curious if it is mainly one agent doing everything, or do you use multiple agents with different roles that work together in some kind of orchestration?
CraftBot
@rupeshpandith It is actually something we have been considering to improve. Currently, the main agent create Living UI with a creator skill. However, having multiple sub-agents can save more tokens and stuff. Please look forward to our future release! This is the direction we are heading.
The 3AM memory consolidation is the most interesting architectural decision here. Love it. Most local agents treat memory as a simple append log (which means the context gets bloated or stale fast). This one is different.
CraftBot
@artstavenka1 Glad you like it! Yes, we also prune it periodically, removing and merging memory depending on the context.