soliplex-concierge 0.8

Soliplex extension for LLM-driven room access / creation requests.

soliplex-concierge: room access / creation support

This project provides a Soliplex extension for LLM-driven, on-demand room requests: users chat with a self-serve "about" room to request access to a non-public room or the creation of a new room, and the concierge files each request as a tracking issue on a Gitea repository for an administrator to resolve.

📖 Full documentation: https://soliplex.github.io/soliplex-concierge/

Components

• The Python library backs both the in-room issue-filing tool and the admin scripts that resolve filed requests (see the API reference).

• Three Agent Skills under skills/:

  • soliplex-concierge-installer — wire the extension into a stack
  • soliplex-concierge-room — the in-room request formatter, installed into the about-room
  • soliplex-concierge-admin — triage and resolve the filed requests

  See Skills for where to find each one and how to install it.

Quick start

Installing the concierge onto a soliplex-template-generated stack is a job for an AI coding agent (e.g. Claude Code) running the soliplex-concierge-installer skill — you point it at your stack rather than running the wiring script yourself:

1. Install the skill into your coding agent — download the latest soliplex-concierge-installer release and unpack it into the agent's skills directory.
2. Ask the agent to wire up your stack, giving it the stack path and your Gitea owner / repo. The skill runs its bundled scripts/install_concierge.py to apply what it changes, idempotently.
3. Bring up the stack — set real Gitea values in .env, then docker compose build backend && docker compose up -d.

The Gitea token's account must have Write access to the tracking repo, not just Read — Gitea lets a Read-only account open issues but silently drops their labels, so requests would be filed untagged (see issue #59). A fine-grained token additionally needs the write:issue and read:repository scopes.

See Setup for the full option list (version pinning, --with-truststore for an enterprise / internal CA, …), running install_concierge.py directly, and the manual-wiring steps for a non-generated installation.

Once the stack is up, users file requests through the about-room — and you resolve them from your coding agent with the soliplex-concierge-admin skill (installed the same way as the installer). Its gitea_issues.py CLI lists and filters open requests, follows up on them, and closes each with a comment and a decision label. See Admin for the workflow.