It’s a plugin that integrates into Visual Studio Code. As the developer uses various “online coding assistants,” Prism shows an estimate of how much CO\u2082 they’re releasing in the process of outsourcing their mental activity to a datacenter somewhere.<\/p>\n
As the plugin’s homepage says: “It captures token usage from GitHub Copilot Chat, Claude Code, and runtime LLM API calls, then calculates CO\u2082 equivalents and surfaces them in the sidebar, status bar, and a live dashboard.”<\/p>\n
Prism comes out of a collaborative effort between the University of Bristol<\/a> and ustwo<\/a>, a majority employee-owned “global digital product studio.” Ustwo’s Nick Hegarty said: “Developers are not the problem, but a fundamental part of the solution. By making AI emissions visible during development, we hope to create greater awareness and support better decision-making. We believe even directional estimates can be valuable if they help start conversations and encourage more thoughtful AI usage.”<\/p>\n \n The Prism developers from the University of Bristol The emissions estimate uses “a transparent token-to-energy-to-carbon methodology informed by Green Software Foundation<\/a> guidance and recent academic research.”<\/p>\n Super Productivity<\/p>\n Maintainer Johannes Milan wrote to tell us about “Super Productivity.” Normally a name like that would set our mental alarm bells ringing, but he did it just right. As a handy lesson for all the other breathlessly excited organizations out there, this is how to do it: with no hyperbole, and a terse text-only email with no formatting<\/a>. <\/p>\n He told us: “I maintain Super Productivity, a mature MIT-licensed local-first task manager and time tracker. It runs on Linux, Windows, macOS, web, and mobile; has Linux packages for Flatpak, Snap, AppImage, deb, and rpm; and works without accounts or telemetry.”<\/p>\n This is a good intro, so what does it do? It is “a local-first productivity app that is not another cloud suite: tasks, timeboxing, Pomodoro, time tracking, review, and issue tracker integrations in one offline-capable app.”<\/p>\n The phrase “local-first” twice makes us think he has a better idea of our interests than the PR people who tell us that they liked a random article from three years ago and so should write about their new AI-based product.<\/p>\n If you want to see the source, it’s on GitHub<\/a>, and if you are more used to a bit of hyperbole, the product’s homepage<\/a><\/p>\n TAMOSS<\/p>\n TAMOSS is a far more specialized tool, but may be very valuable to the people who need it. The name is short for Time-Addressable Media Open Source Store<\/a>, and the product’s homepage says “TAMOSS is an open source, Kubernetes-native implementation of the BBC TAMS API.”<\/p>\n Which of course merely left us wondering what the BBC TAMS API was, but happily, the Beeb has a bit over 100 years of experience at explaining stuff. It has some pretty good educational resources of its own. We suggest starting with the BBC R&D division’s TAMS in 2025<\/a> \u2013 we found the introductory video there packed a decent summary into three and a half minutes.<\/p>\n TAMS, short for Time-Addressable Media Store<\/a>, is an API for a server that “can be used to store, query and access segmented media over HTTP.” Most audio-visual media online is in the form of single, big, fat media files, which contain video, soundtrack, subtitles and more, all mixed together. This is very unhelpful if you want to edit the material, split off a soundtrack, or slow part of it down or whatever. It’s a lowest common denominator sort of thing, but that’s what all the tools understand and what existing servers know how to send.<\/p>\n The TAMS spec lets a client request and receive separate parts of this (the sound, or the video, or both, or other data) by timeline using AMWA NMOS-compatible<\/a> UUIDs over HTTP. NMOS here is the Networked Media Open Specifications<\/a> from the Advanced Media Workflow Association<\/a>.<\/p>\n Did you know the BBC has its own GitHub<\/a>? Us neither, but on it you’ll find the open source TAMS API spec<\/a>. The TAMS standard has its own site<\/a> as well, and the Beeb hosts the BBC R&D white paper<\/a> that the spec is based on.<\/p>\n![\"The](\"https:\/\/www.newsbeep.com\/uk\/wp-content\/uploads\/2026\/06\/5261648.webp\")
<\/p>\n
\n Pic courtesy ustwo\n <\/p>\n