[{"data":1,"prerenderedAt":18},["ShallowReactive",2],{"release:0.3.11":3},{"version":4,"title":5,"description":6,"date":7,"url":8,"markdownPath":9,"prerelease":10,"html":11,"newer":12,"older":15},"0.3.11","L4 0.3.11","This release makes Telegram a full Shell: open L4 from @L4agent, keep your Servers there, create new ones and get notifications from them in Telegram. Landing, Shell, installer, Server, portable runtime and Docs share…","2026-10-30","\u002Fchangelog\u002Fv0.3.11","\u002Fchangelog\u002Fv0.3.11.md",false,"\u003Cp>This release makes Telegram a full Shell: open L4 from \u003Ca href=\"https:\u002F\u002Ft.me\u002FL4_agent\" rel=\"noopener\">@L4_agent\u003C\u002Fa>, keep your Servers there, create new ones and get notifications from them in Telegram. Landing, Shell, installer, Server, portable runtime and Docs share \u003Cstrong>0.3.11\u003C\u002Fstrong>. It stays on the \u003Ccode>server-v2\u003C\u002Fcode> lineage and adds one migration, \u003Ccode>0003_telegram_notifications\u003C\u002Fcode>. Customer Servers update only when their operator chooses an update.\u003C\u002Fp>\n\u003Ch2 id=\"telegram-shell\">\u003Ca class=\"heading-anchor\" href=\"#telegram-shell\">Telegram Shell\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>@L4_agent opens the Shell on \u003Cstrong>My Servers\u003C\u002Fstrong>, like the installed app. It keeps clear of Telegram's controls, the notch and the home indicator, including the embedded Server.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Create → Cloudflare\u003C\u002Fstrong> offers \u003Cstrong>Continue in browser\u003C\u002Fstrong>, because Cloudflare sign-in does not work reliably inside Telegram. When the Server is ready, \u003Cstrong>Open in Telegram\u003C\u002Fstrong> next to it brings it back to the Telegram Shell.\u003C\u002Fli>\n\u003Cli>You sign in on each Server with its own account, as on the web. L4 keeps no Telegram accounts.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"telegram-notifications\">\u003Ca class=\"heading-anchor\" href=\"#telegram-notifications\">Telegram notifications\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>In the Telegram Shell, \u003Cstrong>Settings → Telegram notifications\u003C\u002Fstrong> asks Telegram to let @L4_agent message you, then sends mentions, direct messages, Live sessions and email as a short message with an \u003Cstrong>Open\u003C\u002Fstrong> button.\u003C\u002Fli>\n\u003Cli>Messages name only the Server, never what was said. The Server stores an opaque delivery token and never learns your Telegram ID; llll.gg keeps no list of subscriptions.\u003C\u002Fli>\n\u003Cli>Blocking the bot, or turning the switch off, removes the subscription. Telegram notifications need no Web Push keys and work next to Web Push on your other devices. See \u003Ca href=\"https:\u002F\u002Fllll.gg\u002Fdocs\u002Fguides\u002Ftelegram\">Telegram\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"git\">\u003Ca class=\"heading-anchor\" href=\"#git\">Git\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Server settings → Git → Gitea\u003C\u002Fstrong> names the token scopes L4 needs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"update-to-this-release\">\u003Ca class=\"heading-anchor\" href=\"#update-to-this-release\">Update to this release\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>A Cloudflare Server that keeps Cloudflare access updates from Server settings → Deployment → Updates by itself. A Docker Server updates by its image tag in Coolify or Docker Compose; the VPS installer uses \u003Ccode>llll upgrade\u003C\u002Fcode>. The update applies \u003Ccode>0003_telegram_notifications\u003C\u002Fcode>, which adds three columns to push subscriptions; the Telegram notifications switch appears once the Server runs 0.3.11.\u003C\u002Fp>\n",{"title":13,"url":14},"L4 0.3.12","\u002Fchangelog\u002Fv0.3.12",{"title":16,"url":17},"L4 0.3.10","\u002Fchangelog\u002Fv0.3.10",1793363283738]