github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[PR #13957] [CLOSED] rename Clawdbot -> Moltbot for user-facing side. #19725

New Issue
Closed
opened 2026-04-16 07:14:27 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 07:14:27 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/13957
Author: @GhostScientist
Created: 1/28/2026
Status: ❌ Closed

Base: main ← Head: moltbot

📝 Commits (1)

  • 12fdc64 rename Clawdbot -> Moltbot for user-facing side. npm install is still using clawdbot since the npm moltbot package is being initialized right now.

📊 Changes

6 files changed (+108 additions, -108 deletions)

View changed files

📝 cmd/config/integrations.go (+2 -2)
📝 cmd/config/moltbot.go (+9 -9)
📝 cmd/config/moltbot_test.go (+48 -48)
📝 docs/docs.json (+1 -1)
➖ docs/integrations/clawdbot.mdx (+0 -48)
➕ docs/integrations/moltbot.mdx (+48 -0)

📄 Description

Attempts to address the issue detailed in https://github.com/ollama/ollama/issues/13956

image

Some additional context:: The upstream NPM package is still published as clawdbot (https://www.npmjs.com/package/clawdbot), so the CLI executable and config paths (~/.clawdbot/clawdbot.json) remain unchanged in this PR. Once the Moltbot team publishes a renamed package, a follow-up PR will be needed to update the executable lookups and config paths. As of January 28th 2026, npm install -g clawdbot@latest is still the correct installation method.

Testing

  • go test ./cmd/config/... - all 108 tests pass
  • go run . launch --help - shows moltbot in supported integrations list
  • go run . launch moltbot --config - correctly prompts for model selection and displays "Select models for Moltbot"

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/13957 **Author:** [@GhostScientist](https://github.com/GhostScientist) **Created:** 1/28/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `moltbot` --- ### 📝 Commits (1) - [`12fdc64`](https://github.com/ollama/ollama/commit/12fdc64afccbd8b4f071e2f2446a36872ff0c6f8) rename Clawdbot -> Moltbot for user-facing side. npm install is still using clawdbot since the npm moltbot package is being initialized right now. ### 📊 Changes **6 files changed** (+108 additions, -108 deletions) <details> <summary>View changed files</summary> 📝 `cmd/config/integrations.go` (+2 -2) 📝 `cmd/config/moltbot.go` (+9 -9) 📝 `cmd/config/moltbot_test.go` (+48 -48) 📝 `docs/docs.json` (+1 -1) ➖ `docs/integrations/clawdbot.mdx` (+0 -48) ➕ `docs/integrations/moltbot.mdx` (+48 -0) </details> ### 📄 Description Attempts to address the issue detailed in https://github.com/ollama/ollama/issues/13956 <img width="513" height="148" alt="image" src="https://github.com/user-attachments/assets/c3f647cb-ce97-451a-ad93-693935eb6e15" /> > **Some additional context::** The upstream NPM package is still published as `clawdbot` (https://www.npmjs.com/package/clawdbot), so the CLI executable and config paths (`~/.clawdbot/clawdbot.json`) remain unchanged in this PR. Once the Moltbot team publishes a renamed package, a follow-up PR will be needed to update the executable lookups and config paths. As of January 28th 2026, `npm install -g clawdbot@latest` is still the correct installation method. Testing - `go test ./cmd/config/...` - all 108 tests pass - `go run . launch --help` - shows `moltbot` in supported integrations list - `go run . launch moltbot --config` - correctly prompts for model selection and displays "Select models for Moltbot" --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 07:14:27 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#19725
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?