Tech Ideas: AI, Cloud, Silicon & Infrastructure Proposals
Our Tech Ideas collection focuses on emerging technology proposals across Artificial Intelligence, Cloud Computing, Hardware & Silicon, and Developer Infrastructure—spanning platforms like OpenAI, Anthropic, NVIDIA, Apple, Google Cloud, AWS, and Cloudflare.
Engineers and technical architects use this board to propose lower-latency inference APIs, persistent model context windows, hardware telemetry hooks, and cross-cloud observability standards.
Curated Community Proposals
I genuinely love using Claude, but there is one UI decision that has been bothering me more than it probably should: the usage circle displayed in the interface.
I understand why usage indicators exist. Anthropic wants users to know how much of their allowance they have consumed and when they might approach their limits. That's completely reasonable.
But why can't we choose to hide it?
I personally experience claustrophobia, and certain interface elements can make me uncomfortable, especially when they create a constant feeling of restriction or pressure.
The usage circle is one of those elements for me.
Every time I use Claude, I am reminded that my usage is limited. I don't want to constantly monitor a circle filling up or worry about how close I am to reaching a limit.
I just want to use the product without that visual reminder following me around.
1. Accessibility Should Include Customization
Accessibility isn't only about screen readers, font sizes, or color contrast.
It should also include giving people control over elements that cause unnecessary visual discomfort.
Different people experience interfaces differently.
Some people find usage indicators helpful. Others find them distracting, stressful, or uncomfortable.
Why should everyone be forced to see the same indicator?
A simple toggle in Settings could solve this:
Settings → Appearance → Show Usage Indicator → Off
That's it.
People who want the circle can keep it. People who don't can hide it.
Nobod
Anthropic · 3 upvotes
Pre-flight checklist
- [x] This is an API feature request, not a consumer app or Comet UI request.
- [ ] Check current documentation and forum topics for closely equivalent functionality before posting.
- [x] The developer workflow or API use case is described below.
Feature type
New response field or metadata; New endpoint or API capability
Affected API area
Search API; Agent API
Summary
Show which parts of a compound claim are supported, disputed or not established by a cited record.
Problem
One source may validate a date but not an alleged motive, impact or causal relationship. A citation alongside an entire sentence can misrepresent its evidential scope.
Proposed API behavior
Return claim components and per-component evidence links, including source spans where permitted, support type, contrary records, missing elements and reviewer qualification. Keep uncertain interpretations explicit rather than converting them to unsupported numerical confidence.
Example usage
For a claim that a policy changed in March and directly caused a later improvement, the API can confirm the dated policy change while marking the claimed causal impact as not established.
Workarounds tried / considered
Developers can manually split claims and compare excerpts, or ask models to do so; these methods require verification and may conflate inference with source-supported fact.
Impact
Research, legal-policy, education and compliance applications benefit
Cohere · 4 upvotes
Allow linking a GitHub/GitLab branch directly to a ChatGPT Project workspace with automatic diff indexing so we don't have to re-upload modified files on every commit.
OpenAI · 1620 upvotes
Pro Max iPhones have massive displays and workstation-class silicon, yet still lack a native persistent clipboard manager and true top/bottom split-screen multitasking between two active apps.
Apple · 1842 upvotes
Extend Claude Artifacts beyond frontend React components so developers can spin up lightweight Node/Python FastAPI endpoints and test full-stack interactions in-browser.
Anthropic · 1180 upvotes
Reviewing 2,000-line PRs is painful, but managing stacked PRs manually when base branches get review commits requires external CLI tools. Build first-class stacked diffs directly into GitHub Pull Requests.
GitHub · 1385 upvotes
Let developers pick any user UUID in the dashboard, run a dry-run SELECT/INSERT/UPDATE query, and see a visual breakdown of which RLS expression allowed or blocked the row.
Supabase · 940 upvotes
Display a native 12-month historical price chart on Amazon listings and allow strict boolean filtering by technical specs (e.g., USB-C PD wattage, display nit brightness) without sponsored overrides.
Amazon · 920 upvotes
Give indie developers and startups a strict dollar spend ceiling per billing cycle that gracefully degrades to static cached pages instead of accruing unexpected overage bills during DDoS spikes.
Vercel · 1690 upvotes
Support zero-compression native DisplayPort alt-mode over USB-C for Quest headsets on macOS and Linux workstations alongside granular cross-platform developer debug logs.
Meta · 745 upvotes
Bring back hardware-accelerated Linux on DeX with dual external 4K monitor support so Galaxy flagship devices can run full VS Code and Docker containers natively.
Samsung · 860 upvotes
Let logged-in users permanently boost official documentation domains and mute low-quality SEO scraper farms directly from search result cards.
Google · 1530 upvotes