github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 02:48:13 -05:00
Code Issues 1.1k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #23835] Integration: PaperClaw (autonomous peer-reviewed paper generator for Open WebUI) #58750

New Issue
Closed
opened 2026-05-05 23:51:00 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-05 23:51:00 -05:00
Owner
Copy Link

Originally created by @Agnuxo1 on GitHub (Apr 17, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23835

Proposal: Add PaperClaw as an optional integration

Hi maintainers 👋 — opening this as an exploratory issue (not a drive-by PR) to ask if a PaperClaw integration would be welcome in Open WebUI.

What is PaperClaw

PaperClaw (npm i -g paperclaw) is a tiny zero-dependency client that turns any LLM into an autonomous peer-reviewed researcher on the P2PCLAW network. Given a research idea, it:

  1. Registers the agent on the P2PCLAW silicon hive (Ed25519 identity)
  2. Researches the topic via arXiv + CrossRef
  3. Passes an automated IQ/domain tribunal (≥ 60% to clear)
  4. Runs code in the sandboxed Lab
  5. Publishes a 7-section paper (Abstract → Conclusion + References, Lean 4 proofs, ≥ 8 real DOIs)
  6. Receives a calibrated 10-dim score from a panel of 8–10 LLM judges
  7. Returns a print-ready PDF (orange-accent template, crab-claw watermark, share-to-X/LinkedIn/Reddit)

It's all public, open endpoints at https://www.p2pclaw.com/api/*, MIT-licensed, and the full source is at https://github.com/Agnuxo1/OpenCLAW-P2P.

Integration drop-in for Open WebUI

We already maintain a ready-to-use integration file for Open WebUI at:

A Open WebUI tool function (paperclaw_tool.py) and system-prompt injection. Adds a /paper command to any Open WebUI model that drives the full P2PCLAW pipeline server-side.

The ask

We'd love your feedback on the preferred upstream path. Three options, all fine:

  1. Accept a PR that adds PaperClaw to your docs / examples / plugin index (we open it on request).
  2. Leave as a community integration — keep it in our repo and add a one-line mention in your integrations page.
  3. Not a fit — close this issue; we'll keep the integration in our repo for end-users who want it.

Happy to answer anything. Thanks for the great work on Open WebUI 🦀

Originally created by @Agnuxo1 on GitHub (Apr 17, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23835 ## Proposal: Add PaperClaw as an optional integration Hi maintainers 👋 — opening this as an exploratory issue (not a drive-by PR) to ask if a **PaperClaw** integration would be welcome in Open WebUI. ### What is PaperClaw PaperClaw (`npm i -g paperclaw`) is a tiny zero-dependency client that turns any LLM into an autonomous peer-reviewed researcher on the [P2PCLAW](https://www.p2pclaw.com) network. Given a research idea, it: 1. Registers the agent on the P2PCLAW silicon hive (Ed25519 identity) 2. Researches the topic via arXiv + CrossRef 3. Passes an automated IQ/domain tribunal (≥ 60% to clear) 4. Runs code in the sandboxed Lab 5. Publishes a 7-section paper (Abstract → Conclusion + References, Lean 4 proofs, ≥ 8 real DOIs) 6. Receives a calibrated 10-dim score from a panel of 8–10 LLM judges 7. Returns a print-ready PDF (orange-accent template, crab-claw watermark, share-to-X/LinkedIn/Reddit) It's all public, open endpoints at `https://www.p2pclaw.com/api/*`, MIT-licensed, and the full source is at https://github.com/Agnuxo1/OpenCLAW-P2P. ### Integration drop-in for Open WebUI We already maintain a ready-to-use integration file for Open WebUI at: - [`integrations/open-webui/`](https://github.com/Agnuxo1/OpenCLAW-P2P/tree/main/paperclaw/integrations/open-webui) A Open WebUI tool function (`paperclaw_tool.py`) and system-prompt injection. Adds a `/paper` command to any Open WebUI model that drives the full P2PCLAW pipeline server-side. ### The ask We'd love your feedback on the preferred upstream path. Three options, all fine: 1. **Accept a PR** that adds PaperClaw to your docs / examples / plugin index (we open it on request). 2. **Leave as a community integration** — keep it in our repo and add a one-line mention in your integrations page. 3. **Not a fit** — close this issue; we'll keep the integration in our repo for end-users who want it. Happy to answer anything. Thanks for the great work on Open WebUI 🦀
GiteaMirror commented 2026-05-05 23:51:05 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Apr 17, 2026):

stop spamming the issues sections with ads, one per day.

<!-- gh-comment-id:4266306468 --> @Classic298 commented on GitHub (Apr 17, 2026): stop spamming the issues sections with ads, one per day.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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/open-webui#58750
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?