8000 Release v0.8.0 · adeelahmad/lense · GitHub
[go: up one dir, main page]

Skip to content

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 11 Oct 10:00
· 370 commits to main since this release
  • A microsandbox's full edition installs LibreOffice and Chromium the first time they're needed. They were
    installed at every start, so a first start downloaded them before it built Lens, whether or not anything used them.
    A sandbox now starts without them; th 78EF e first Office file, email or web page that needs one waits while it's
    installed, and later starts install it again in the background from the packages kept in the volume. An install that
    already had them keeps them (microsandbox).

  • A microsandbox install gets past name lookups that fail. The first build in a microsandbox could stop at the
    backend's packages with dns error ... No address associated with hostname when this machine's resolvers didn't
    answer inside the sandbox. The sandbox now waits for the names it downloads from, looks them up with public
    resolvers (1.1.1.1 and 9.9.9.9; LENS_DNS_FALLBACK changes or turns that off) when this machine's don't answer
    there, and runs each download step up to three times (microsandbox).

  • Running the install line again keeps the lean edition. An install made lean (LENS_TARGET=lean, or the web
    installer's pick on a computer with less than 4 GB of memory) became full again when the line ran without
    LENS_TARGET, so the next start installed LibreOffice and Chromium. It now keeps the edition the install has, as it
    does the port and the network setting (Get started).

  • A Mac app. Lens.app (Lens-macOS-arm64.dmg, Apple silicon) installs Lens in the web installer shown in its
    window, with microsandbox inside it so no Docker is needed, then lives in the menu bar: open, start, stop and update
    Lens, and show its logs. Lens itself opens in the browser, where passkeys work
    (Get started). It updates itself from each release, checking the update's
    signature, once the repository has an update key (desktop/README.md).

  • Slack, built in. Settings › Slack creates a Slack app from Lens's manifest in one click; paste its two tokens
    and the assistant answers direct messages, what's said to it in channels and /lens …, over Socket Mode: no
    Matterbridge, no public address. Voice clips are heard, files are held for the assistant to import, and everything
    Matterbridge rooms do works there (Chat rooms).

  • The file tree over NFS. Settings → NFS share serves the archive's folders and files (namespaces, collections,
    topics and entities as folders, assets as files) read-only over NFS, to the networks you allow, showing what one
    chosen account sees. Off until turned on; published on port 12049 of the host (File shares).

  • The graph as files over SMB. Settings → SMB share serves the file tree read-only to Finder, Linux and (on port
    445) Windows: each person signs in with a file access key and sees what the web app shows them, from the networks
    an admin allows. Off by default; the SMB server (impacket) is fetched when it's turned on (SMB share).

  • A spending limit from the start. The setup wizard has a Budget step, and the web installer asks for one with a
    cloud provider: a scale for a hard limit on everything Lens spends on AI, with a soft limit at 80% that warns. At
    the hard limit runs wait (or are skipped) and paid model calls stop until it goes up; models on your own computer
    keep working. The model's price comes with it, so the spending is counted. It's the new all budget, changeable in
    Settings › Budgets (Budgets). The web installer now asks only the
    essentials: the folder, port and network under Advanced, the optional extras under More options on the
    review.

  • Cloud model presets. Settings → LLM provider and the setup wizard offer OpenAI, Anthropic, Google Gemini,
    OpenRouter, Groq, Mistral and DeepSeek next to the model servers found nearby: one click fills in the address and a
    model and puts the cursor in the API key field, with a link to where the provider hands out keys, so switching to a
    cloud model is a click and a paste. Agents get the same list from GET /api/v1/setup/llm/providers and the
    assistant's find_model_servers tool (Cloud model providers).

  • The graph as files. Graph nodes are folders, nested along its links: collections inside collections, topics
    inside their broader topics, entities by type. Each folder holds its assets' files, with a .json sidecar of
    metadata and a .txt of the text; everyone sees what the web app shows them. Browse and read it through the API
    (/api/v1/tree) and the MCP tools list_files and read_file (The graph as files).
    An NFS share is in progress.

  • HTTPS with automatic certificates. Lens can serve itself at https:// your domain with a certificate it gets
    and renews on its own from Let's Encrypt or ZeroSSL (or any ACME authority), proving the domain over HTTP, TLS-ALPN
    or DNS, with Cloudflare, Route 53 and the other caddy-dns providers, so wildcards and machines the internet can't
    reach work too. Run the install line with LENS_HTTPS=1 to open ports 443 and 80, then set it up with
    PUT /api/v1/settings/https; the Settings page comes next. Off by default (HTTPS).

  • Budget meter and Costs page. The top bar shows what the namespace picked spent against its budget, used and
    left, highlighted when near or over, and follows the namespace switcher; it opens the details for a day, week or
    month. Costs in the left menu shows spend by day, model and resource, and sets the namespace's budget
    (Budgets).

  • The graph over S3 and WebDAV. Turn on Settings, File shares, and any S3 client (rclone, Cyberduck, the AWS CLI) or
    WebDAV client (Finder, Windows Explorer, file managers) lists and reads the graph as folders and files,
    read-only, with access keys each person makes on their API tokens page (S3,
    WebDAV). Docker publishes S3 on port 9555 (LENS_S3_PORT) and WebDAV on 9556
    (LENS_WEBDAV_PORT), where the web app is.

  • Ask Lens from your browser. The web clipper extension has the Lens assistant in a side panel: Ask Lens in
    its popup or on the right-click menu. It signs in with one click through Lens's own sign-in page (OAuth, nothing to
    copy), and the conversations are the same ones Lens's chat shows, with cited answers, the steps taken and approvals.
    While the panel is open, the assistant can use that browser: open, read, click, type and download files into the
    conversation, only on sites you allow, asking before anything that sends, deletes, buys or posts, never typing
    passwords or card numbers, and showing each action as it happens. Once it has read a page, opening an address or
    typing text you didn't write asks you first too (The assistant in your browser).

  • Telegram, built in. Paste a bot token from @Botfather in Settings › Telegram and the assistant answers there:
    no Matterbridge, no public address. It talks only to people you let in (one click on the settings page), hears
    voice notes, takes files for the assistant to import, and does everything it does in Matterbridge rooms
    (Chat rooms). Chat apps now share one channel layer, so the next one is an
    adapter.

  • The assistant by email. Give it an address of its own in Settings › Assistant email (the address and an app
    password; the servers are guessed) and the people you let in can email or forward things to it: it answers by
    email in the same thread, lists the excerpts it cites with links, and imports what's attached, a forwarded email
    whole. It answers only mail their provider vouched for (DMARC, DKIM or SPF), never automatic mail, and holds a
    stranger's mail until you let them in. lens+pods@… or a routing rule sends mail to a namespace's assistant
    (The assistant by email).

Features

  • assistant: mark third-party text as data in the model's prompts (#302)
  • backups: restore, download, any schedule and copies to an rclone connection from the web app (#263)
  • assistant: let the assistant use a browser connected through the Lens side panel (#311)
  • clipper: build the web clipper for Firefox (#282)
  • assistant: ask before sending data out once an answer read third-party text (#309)
  • monitoring: Prometheus, node-exporter and Grafana as an opt-in compose profile (#297)
  • install: install with the defaults in one click; the API token form opens itself (#331)
  • assistant: flag third-party text that reads like instructions to an AI (#329)
  • ui: new pipelines and routines are named for you and Enter creates them; Enter in a note's title goes to its first line (#336)
  • bridge: break up links a chat-room answer built from what it read (#338)
  • mcp: hand agents what the archive says as data (#343)
  • audit: log what Lens caught of prompt injection (#344)
  • assistant: an optional local classifier for prompt injection (#347)
  • turn Prometheus and Grafana on from the web app (#337)
  • ui: copy the MCP address from the account menu after setup (#340)

Fixes

  • release: keep the API schema's version in step with each release (#310)
  • ui: fewer clicks in setup, Chat, Search and Notes (#315)
  • jobs: skip transcribe and diarize for imported transcripts (#345)
  • ui: open the graph on the namespace that has one (#339)
  • desktop: check the update's signature against the repository's key at build time (#354)

Dependencies

  • bump the python-minor group (#253)
  • bump the javascript-minor group (#316)
0