levix-bot 2.1.2 → 2.2.1

package/README.md

@@ -18,9 +18,11 @@ go to **Connection**, press **Start session** and scan the QR — see
 [SETUP.md](SETUP.md) for the longer version, Docker, and running it as a
 service.
 
-Starting Levix does not connect it to WhatsApp. The panel, the database and the
-commands come up on their own, and the WhatsApp session is started from the
-Connection screen when you want it.
+On a brand-new install, starting Levix does not begin WhatsApp pairing by
+itself: the panel, database and commands come up first, and the Connection
+screen starts the first session when you ask. After that first successful link,
+the saved WhatsApp session resumes automatically after a process, Docker or
+systemd restart unless you explicitly stop or unlink it.
 
 ```
   levix                    start Levix with the web panel
@@ -54,7 +56,9 @@ is a Markdown file you can edit from the panel.
 per-chat file. Plain Markdown, hand-editable, injected into every prompt.
 
 **Scheduled messages** — one-off (`!schedule`) or recurring (`!autoschedule`),
-stored in the database and listed in the panel.
+including daily and weekly schedules with Arabic or English day names. Jobs
+survive restarts; their latest delivery result is shown in the panel, where a
+failed message can be retried manually.
 
 **Optional proxy** — Settings → WhatsApp proxy routes the WhatsApp connection
 through an HTTP, HTTPS or SOCKS5 proxy, including the media it sends and

package/SETUP.md

@@ -58,9 +58,14 @@ The terminal prints something like:
    bot before you do.)
 3. You land on the control panel. Go to **Connection**, press **Start session**,
    and scan the QR with WhatsApp → Settings → Linked devices → Link a device.
-   Levix does not connect to WhatsApp until you ask it to.
+   A brand-new install does not begin pairing until you press Start.
 4. Send `!ping` in any chat. The bot answers.
 
+After that first successful pairing, the saved WhatsApp session resumes
+automatically after a Levix, Docker or systemd restart. You only need the
+Connection screen again if you deliberately stop/unlink the session or WhatsApp
+requires a new link.
+
 Levix only opens a browser when there is one to open: over SSH, under systemd,
 in Docker or in CI it just prints the address and says why. `--no-open` turns
 it off anywhere.
@@ -85,7 +90,8 @@ Then open <http://localhost:3001>. The setup code is in the logs:
 docker compose logs levix | grep -F '[Setup] Setup code:' | tail -1
 ```
 
-Everything the bot owns lives in the `levix-data` volume.
+Everything the bot owns lives in the `levix-data` volume. Once WhatsApp has
+been paired, restarting the container reuses that saved session automatically.
 
 ---
 
@@ -181,11 +187,11 @@ journalctl -u levix --no-pager | grep -F '[Setup] Setup code:' | tail -1
 
 Read the script first if you like — it is short, and it explains each step.
 
-That always installs the newest stable Levix. To stay on one version — the same
-script, pinned — use its own URL:
+That always installs the newest stable Levix. To stay on this release — the
+same script, pinned — use its own URL:
 
 ```bash
-curl -fsSL https://levix.leviro.net/install/v2.0.0.sh | bash
+curl -fsSL https://levix.leviro.net/install/v2.2.1.sh | bash
 ```
 
 **Behind a proxy** — if this server reaches the internet through a proxy, the

package/app.cjs

@@ -19,6 +19,7 @@ const { assetPath } = require("./src/config/paths.cjs");
 const brand = require("./src/config/brand.cjs");
 const settings = require("./src/config/settings.cjs");
 const secrets = require("./src/config/secrets.cjs");
+const { PanelSessionStore } = require("./src/panel/session-store.cjs");
 const { getQrCode } = require("./src/utils/storage.cjs");
 const {
   clientAddress,
@@ -151,9 +152,14 @@ app.locals.brand = brand;
 app.use(express.static(assetPath("public")));
 app.use(express.urlencoded({ extended: true, limit: "100kb" }));
 
+// Levix is intentionally one process and one operator, so a small expiring
+// in-memory store is enough. Unlike express-session's development MemoryStore,
+// it is explicitly bounded and prunes expired entries instead of growing for
+// the lifetime of the process. Sessions still disappear on restart by design.
 const sessionMiddleware = session({
   name: SESSION_COOKIE_NAME,
   secret: secrets.getSessionSecret(),
+  store: new PanelSessionStore({ ttlMs: SESSION_MAX_AGE_MS }),
   resave: false,
   saveUninitialized: false,
   cookie: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "levix-bot",
-  "version": "2.1.2",
+  "version": "2.2.1",
   "description": "A self-hosted personal WhatsApp bot with an AI agent, group moderation and a web control panel.",
   "main": "src/index.js",
   "scripts": {
@@ -57,7 +57,7 @@
     "type": "git",
     "url": "https://github.com/Abdodiab2005/levix.git"
   },
-  "homepage": "https://github.com/Abdodiab2005/levix",
+  "homepage": "https://levix.leviro.net",
   "bugs": {
     "url": "https://github.com/Abdodiab2005/levix/issues"
   },