let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename clawdbot to moltbot with legacy compat

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-27 12:19:58 +00:00
parent 83460df96f
commit 6d16a658e5
1839 changed files with 11250 additions and 11199 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/experiments/plans/cron-add-hardening.md
View File

@@ -1,6 +1,6 @@
---
summary: "Harden cron.add input handling, align schemas, and improve cron UI/agent tooling"
owner: "clawdbot"
owner: "moltbot"
status: "complete"
last_updated: "2026-01-05"
---

4
docs/experiments/plans/openresponses-gateway.md
View File

@@ -1,6 +1,6 @@
---
summary: "Plan: Add OpenResponses /v1/responses endpoint and deprecate chat completions cleanly"
owner: "clawdbot"
owner: "moltbot"
status: "draft"
last_updated: "2026-01-19"
---
@@ -9,7 +9,7 @@ last_updated: "2026-01-19"
## Context
Clawdbot Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
Moltbot Gateway currently exposes a minimal OpenAI-compatible Chat Completions endpoint at
`/v1/chat/completions` (see [OpenAI Chat Completions](/gateway/openai-http-api)).
Open Responses is an open inference standard based on the OpenAI Responses API. It is designed

12
docs/experiments/research/memory.md
View File

@@ -2,7 +2,7 @@
summary: "Research notes: offline memory system for Clawd workspaces (Markdown source-of-truth + derived index)"
read_when:
- Designing workspace memory (~/clawd) beyond daily Markdown logs
- Deciding: standalone CLI vs deep Clawdbot integration
- Deciding: standalone CLI vs deep Moltbot integration
- Adding offline recall + reflection (retain/recall/reflect)
---
@@ -155,16 +155,16 @@ Opinion evolution (simple, explainable):
## CLI integration: standalone vs deep integration
Recommendation: **deep integration in Clawdbot**, but keep a separable core library.
Recommendation: **deep integration in Moltbot**, but keep a separable core library.
### Why integrate into Clawdbot?
- Clawdbot already knows:
### Why integrate into Moltbot?
- Moltbot already knows:
- the workspace path (`agents.defaults.workspace`)
- the session model + heartbeats
- logging + troubleshooting patterns
- You want the agent itself to call the tools:
- `clawdbot memory recall "…" --k 25 --since 30d`
- `clawdbot memory reflect --since 7d`
- `moltbot memory recall "…" --k 25 --since 30d`
- `moltbot memory reflect --since 7d`
### Why still split a library?
- keep memory logic testable without gateway/runtime