Skip to content

docs: add architecture diagram to README #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
subhu339 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add architecture diagram to README #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 44 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,51 @@
| **Cost** | Mac Mini 599$ | Most Linux SBC </br>~50$ |**Any Linux Board**</br>**As low as 10$** |
<img src="assets/compare.jpg" alt="PicoClaw" width="512">

---

## 🏗 Architecture

PicoClaw is designed around a lightweight, event-driven architecture:

```mermaid
flowchart TD

User -->|Message| Channels
Channels --> MessageBus
MessageBus --> AgentLoop
AgentLoop --> ToolRegistry
AgentLoop --> SkillSystem
ToolRegistry --> Tools
SkillSystem --> Skills
AgentLoop -->|Response| MessageBus
MessageBus --> Channels
Channels --> User

subgraph Channels
Telegram
Discord
QQ
DingTalk
end

subgraph Core
MessageBus["Message Bus"]
AgentLoop["Agent Loop"]
ToolRegistry["Tool Registry"]
SkillSystem["Skill System"]
end

subgraph Tools
WebSearch
Cron
FileSystem
end

subgraph Skills
CustomSkills
end

```
## 🦾 Demonstration
### 🛠️ Standard Assistant Workflows
<table align="center">
Expand Down