Skip to content

feat: add qwe-qwe template — self-hosted AI agent#1390

Open
dray-supadev wants to merge 7 commits into
easypanel-io:mainfrom
dray-supadev:add-qwe-qwe-template
Open

feat: add qwe-qwe template — self-hosted AI agent#1390
dray-supadev wants to merge 7 commits into
easypanel-io:mainfrom
dray-supadev:add-qwe-qwe-template

Conversation

@dray-supadev

@dray-supadev dray-supadev commented May 8, 2026

Copy link
Copy Markdown

qwe-qwe — Business-Oriented AI Agent

GitHub: https://github.com/deepfounder-ai/qwe-qwe
Community: https://t.me/qwe_qwe_ai

What is qwe-qwe?

A business-oriented AI agent designed to drop into real workflows — customer ops, internal automation, knowledge retrieval, scheduled reporting, and custom integrations. Deploy on your own infrastructure and bring any OpenAI-compatible LLM provider.

Bring your own LLM: Azure OpenAI, AWS Bedrock, OpenAI, Groq, OpenRouter, DeepSeek, Together — or a local model via LM Studio / Ollama for fully on-prem deployments. Switch providers without restarting.

Features

  • 🏢 Business-ready — routines, scheduled tasks, Telegram notifications, knowledge retrieval
  • 🧠 Long-term memory — hybrid vector search (dense + sparse + BM25) via Qdrant
  • 📚 RAG — index PDFs, DOCX, URLs, YouTube videos (50+ formats via MarkItDown)
  • 🌙 Knowledge graph synthesis — night worker builds entity graph from conversations
  • 🔄 Routines — chat threads with a schedule, each firing visible as a conversation
  • 🔌 Skill plugins — drop a .py file to extend; or create skills from chat in 60s
  • 🛡️ Encrypted Vault — API keys stored with Fernet encryption
  • 📱 Telegram bot + Web UI + terminal CLI

Template parameters

Parameter Default Description
App Service Name qwe-qwe Service name in Easypanel
App Service Image ghcr.io/deepfounder-ai/qwe-qwe:latest Docker image
LLM Provider URL https://api.openai.com/v1 Any OpenAI-compatible endpoint
LLM Model Name gpt-4o-mini Model identifier
LLM API Key (empty) Your provider API key
Web UI Password (empty) Optional password to protect the UI

Data persistence

All user data stored in a named volume at /root/.qwe-qwe — conversations, memory, uploaded files, and knowledge base survive restarts.

Docker image

Published to ghcr.io/deepfounder-ai/qwe-qwe:latest on every push to main via GitHub Actions.

@netlify

netlify Bot commented May 8, 2026

Copy link
Copy Markdown

Deploy Preview for easypanel-templates ready!

Name Link
🔨 Latest commit d8e3fe2
🔍 Latest deploy log https://app.netlify.com/projects/easypanel-templates/deploys/6a04efaa2801e60008d35d9a
😎 Deploy Preview https://deploy-preview-1390--easypanel-templates.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

deepfounder-ai added a commit to deepfounder-ai/castor that referenced this pull request May 8, 2026
Builds and pushes ghcr.io/deepfounder-ai/qwe-qwe:latest on every main push,
and versioned tags (e.g. :0.18.4) on version tags. Required for Easypanel
template (PR: easypanel-io/templates#1390).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Ahson-Shaikh

Copy link
Copy Markdown
Collaborator

Hi @dray-supadev,

There are a lot of changes required on this PR.

  • The logos and screenshot has to go in a separate folder named "assets"
  • At the root of the template, there are only two files required; meta.yaml and index.ts.

Please make sure to follow the what's being followed by taking any of my PRs as a reference that are still open.

…back

PR review feedback (easypanel-io#1390): root of template should contain only
meta.yaml and index.ts; logos and screenshots belong in an `assets/`
subfolder. Moving logo.png accordingly to match the convention used
by ackee, pgweb, firefox, syncthing, etc.
@dray-supadev

Copy link
Copy Markdown
Author

Thanks for the review @AhsanShahbaz! Fixed: moved logo.png into templates/qwe-qwe/assets/ per the convention. The template root now contains only meta.yaml and index.ts as required. Ready for re-review.

… PRs

Following the style used in easypanel-io#1392 (Paperclip) and easypanel-io#1396 (ZeroClaw):
- Blank line between top-level sections (description, instructions,
  changeLog, links, contributors, schema, benefits, features, tags)
- changeLog date corrected to 2026-05-13 (was an old placeholder)
- Image tag pinned to v0.22.0 instead of :latest, matching the
  pin-to-version convention used by ZeroClaw and others
- Instructions reworded to reference the UI labels (LLM Provider URL,
  LLM API Key) rather than internal env-var names, since users
  configure these via the Web UI Settings page rather than env vars
@dray-supadev

Copy link
Copy Markdown
Author

Sorry for the misnamed handle in my previous comment, @Ahson-Shaikh!

Took another pass against #1392 (Paperclip) and #1396 (ZeroClaw) as references. Changes in the latest commit:

  • logo.png moved into templates/qwe-qwe/assets/ (root now has only meta.yaml + index.ts)
  • ✅ Blank lines between top-level meta.yaml sections to match your style
  • changeLog date corrected to today (was an old placeholder from before the rebase)
  • ✅ Image tag pinned to v0.22.0 instead of :latest
  • instructions rephrased to reference the Web UI labels users actually see, not internal env-var names

Happy to add a screenshot.png to assets/ if you'd like one — let me know and I'll capture the Web UI dashboard.

@dray-supadev

Copy link
Copy Markdown
Author

Added screenshot.png to assets/ — shows the Memory view with knowledge graph + indexed entities. Final structure now matches your reference PRs:

templates/qwe-qwe/
├── assets/
│   ├── logo.png
│   └── screenshot.png
├── index.ts
└── meta.yaml

Ready for re-review whenever you have a moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants