Google Renames NotebookLM to Gemini Notebook, Adds Cross-App Syncing and Code Execution

·1 views

Google has rebranded NotebookLM as Gemini Notebook, integrating it more closely with the broader Gemini ecosystem. Users can now create, edit, and sync notebooks across Gemini Apps, Gemini Notebook, and AI Mode in Google Search, allowing research to move seamlessly between interfaces without rebuilding source sets. Google is also rolling out a cloud-based code execution feature that assigns each notebook a secure cloud computer, initially available to AI Ultra and eligible Workspace users, with Pro user access planned for subsequent weeks. However, the sync is not fully bidirectional — while notebooks and sources sync across all three surfaces, chats from Gemini and Gemini Notebook do not sync back to AI Mode. Teams with audit, compliance, or provenance requirements should carefully determine which interface serves as their system of record for a given workflow.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Keybound tool audits prompt cache isolation in multi-tenant LLM relays

A developer named Pedro Sordo Martínez has released Keybound, an open-source auditing tool designed to verify prompt cache isolation in multi-tenant LLM relay systems. The tool tests whether a relay correctly prevents one tenant from reading cache data written by another tenant sharing the same upstream credential. Keybound implements the defense contract defined in the KeyPooling paper (arXiv:2608.17485), which requires that a namespace derived from authenticated tenant identity be applied to every cache lookup and write. The tool runs formal test fixtures against a synthetic mock gateway — returning a FAIL verdict when namespaces collapse and a PASS when per-tenant isolation is enforced. The project achieves 90% overall test coverage, with 97–100% coverage on the core audit logic, and is available under the AGPL-3.0-or-later license on GitHub.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Vagrant and Ansible Still Viable for Dev VMs, Though Containers Now Dominate

A 2014 blog post on setting up development virtual machines using Vagrant and Ansible has been reposted to DEV Community with minor edits. Vagrant was once the standard tool for spinning up local dev VMs, allowing multi-machine environments to be created in seconds. Unlike provisioning tools such as Puppet or Ansible, Vagrant itself only manages the VM lifecycle and delegates configuration to external tools. The author notes that while most teams now prefer containers, the Vagrant-plus-Ansible workflow remains relevant for use cases requiring full VMs, such as kernel-level testing or OS-specific work. An example project, vagrant-lamp-ansible, is still available on GitHub for developers who want to try the setup.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

DEV Community Writer Explains Switching Profile Photo to VTuber Character Shigure Ui

A developer and writer on DEV Community recently changed their profile picture to an image of Shigure Ui, a character from the VTuber world, prompting them to write a detailed personal post explaining the decision. The author connects the change to themes explored in earlier writings about poverty, creative struggle, and emotional hardship. Growing up without internet or a computer in a small village, they describe having built their skills entirely from scratch while facing repeated professional setbacks. The profile picture change is framed not as trivial but as a meaningful reflection of where they currently find joy and emotional grounding. The post is intended as an honest account of how unexpected sources of comfort, including animated characters, can carry genuine personal significance.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Custom New Relic Transaction Naming for eZ Publish via PHP Extension

A developer originally published in 2013 a solution for improving New Relic monitoring on eZ Publish PHP applications. By default, the New Relic PHP agent groups all eZ Publish transactions under '/index.php', making performance diagnosis difficult. The developer built an open-source extension called 'ezpublish-newrelic' that hooks into New Relic's PHP API to assign distinct, meaningful names to individual module and view transactions. The extension remains available on GitHub and can be installed via Composer from Packagist. Although New Relic's PHP agent has evolved since, the core approach of manually naming transactions instead of consolidating them into a single bucket remains a valid practice today.

0 comments Read more at DEV Community