Daily AI · 2026-09-07
Useful AI Daily - September 7, 2026
Start the week with small improvements to work you already do: listening across languages, sketching a soundtrack, choosing repository context, and preparing for a model retirement. The common thread is keeping an editable original and a clear record of where the result came from.
Archive backfill added September 8 for the September 7 edition. This is a week-ahead catch-up on September 2-4 announcements, not a claim that they broke on September 7. It uses no September 8 news.
The Short Version
- Try: Google Translate adds Android background listening and worldwide iOS earpiece playback; the two platforms do not yet have identical features.
- Create: Lyria 3.5 in Gemini offers a quick way to sketch an instrumental idea before spending time on a finished edit.
- Check: Copilot Business and Enterprise customers can apply administrator-defined content exclusions in the app and CLI.
- Plan: GitHub has announced an October 2 retirement for selected Copilot models. Test a replacement before a familiar option disappears.
- Watch: a new newspaper lawsuit is a reminder to keep source attribution and publication permission separate. Allegations are not a court ruling.
5 Updates Worth Your Time
Translate's mobile updates solve two different listening problems
- What changed
- In its September 4 announcement, Google says Android live translation can continue while another app is open or the screen is locked. iOS users worldwide can listen through the phone earpiece; background support on iOS is still described as coming soon.
- Why it matters
- For someone following an announcement or a public talk, the useful improvement is less handling of the phone, not a promise of perfect interpretation.
- Try, watch, or skip?
- Try a short public recording in a language pair you can check. Confirm names, numbers, and negation yourself; do not assume an Android feature is already on your iPhone.
Lyria 3.5 makes a soundtrack sketch easier to specify
- What changed
- Google's September 4 release brings Lyria 3.5 to Gemini, with genre selection, vocal or instrumental choices, templates, and short or longer tracks. Google also lists API and AI Studio access.
- Why it matters
- A small creator can explore the mood of a video before committing to a final soundtrack. The announcement describes the tool, not the rights clearance for your particular project.
- Try, watch, or skip?
- Make two instrumental drafts for your own sample video. Compare speech intelligibility and pacing, then check applicable terms and the destination platform's requirements before publishing.
Copilot file exclusions reach the app and CLI
- What changed
- GitHub's September 2 changelog says the Copilot app and CLI respect exclusion policies set by enterprise, organization, and repository administrators. Excluded files are not used as context. The release is for Business and Enterprise customers.
- Why it matters
- Teams moving between an editor and a terminal need to know which material contributes to suggestions. This is an edition-specific context feature, not a blanket guarantee covering every AI tool or data path.
- Try, watch, or skip?
- Ask an administrator to review the actual exclusion policy. Use a harmless sample repository to check the supported workflow, and keep confidential material out of the initial test.
An October Copilot retirement deserves a September rehearsal
- What changed
- On September 3, GitHub announced October 2 deprecation of Gemini 3.5 Flash, Gemini 3.6 Flash, Kimi K2.7 Code, and Claude Opus 4.7 across Copilot experiences. Its notice lists alternatives and says administrators may need to enable those models.
- Why it matters
- For a solo developer or small team, a disappearing model can disrupt saved routines even when the surrounding application still works. A suggested successor is not proof of equivalent behavior on your tasks.
- Try, watch, or skip?
- Inventory affected settings and saved instructions. Compare the proposed alternative on three representative tasks, record failures, and schedule the switch with time to fix the workflow before October 2.
Newsday and The Seattle Times challenge AI use of their journalism
- What changed
- Reuters reported on September 4 that the newspapers sued OpenAI and Microsoft over alleged unauthorized use of reporting. OpenAI defended its training practices as fair use; Microsoft said it was surprised and open to discussion. These are competing positions, not a resolved legal finding.
- Why it matters
- For newsletter writers and small publishers, a fluent AI summary should not erase the distinction between an original report, an allegation, and your own interpretation.
- Try, watch, or skip?
- Read the underlying source, write a brief original explanation, and link readers to the reporting. Do not treat attribution alone as permission to republish an article; seek qualified advice for uncertain commercial uses.
Tool Worth Trying Today
Lyria 3.5: the two-draft soundtrack comparison
Use one video you own. Write its purpose, mood, and approximate duration; make two contrasting instrumental drafts. Listen beneath the same spoken passage and choose by clarity, not novelty.
Best for: Creators testing a rough cut, a presentation, or a personal video before doing a final audio edit.
Watch out: Check your account's availability and limits. Avoid uploading someone else's song or private client assets. Keep the prompt and output together, and verify publication terms separately.
Privacy / Cost Watch
- Before translating live speech, tell the people involved and check relevant consent and data-handling requirements. Start with public audio rather than a private conversation.
- Generation limits and publication rights are different questions. Check both before paying for more drafts or placing generated audio in a commercial video.
- A repository exclusion policy is not a reason to paste excluded material manually into another prompt. Review each product and account separately.
- Keep original text, links, prompts, and edited output distinct. A citation helps readers verify a claim; it does not itself grant reuse rights.
One Practical Workflow
Make a source-aware creative handoff
- Choose one small asset you own: a short script, a sample recording, or a rough video.
- Write a brief with the audience, intended use, and the parts that must remain unchanged.
- Produce two drafts and save the original, prompt, tool name, and creation date together.
- Compare meaning, names, numbers, pacing, and clarity against the original; get a competent reviewer where needed.
- Check applicable terms, attribution, and publication requirements, then export an editable version with a short source note.
Builder Note
A useful creative feature should retain the source asset, transformation settings, and export path. Keep model selection outside a hard-coded prompt so a scheduled retirement becomes a testable maintenance change. Let users compare drafts and recover the untouched original without regenerating everything.
Ignore For Now
A polished demo without an editable handoff
Skip judging a creative tool only by its best sample. If you cannot compare it with the original, revise it, export it, or explain the source, a faster first draft may create more work later.
Bottom Line
Bottom line: improve one ordinary workflow this week. Keep the original, test the actual feature on your device or plan, and make the handoff easy to inspect and edit.
Sources
- Google: Google Translate rolls out new upgrades for iOS and Android (September 4)
- Google: Create your best tracks yet with Lyria 3.5 in Gemini (September 4)
- GitHub: Content exclusions generally available in Copilot app and CLI (September 2)
- GitHub: Upcoming deprecation of selected GitHub Copilot models (September 3)
- Reuters: Seattle Times, Newsday sue OpenAI, Microsoft, alleging copyright infringement (September 4)