Software Ideas: Engineering Tools, IDEs, APIs & Enterprise Apps

The Software Ideas collection highlights proposals for desktop and cloud software used by engineering and operations teams every day—including GitHub, GitLab, JetBrains, Cursor, Docker, Postman, Supabase, Datadog, and Obsidian.

From native stacked pull requests and local-first offline sync to SQL query profiling and webhook replay queues, these software ideas address real engineering bottlenecks.

Curated Community Proposals

Anthropic: Anthropic, PLEASE Let Us Hide the Usage Circle in Claude. This Is an Accessibility Issue.

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

Cohere: Claim-to-Evidence Coverage and Contradiction API

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

Frequently Asked Questions

Does CrowdFeatures also build free software tools for developers?

Yes! Alongside our community software ideas board, CrowdFeatures provides 13 free, 100% client-side developer utilities at /tools—including a JSON Formatter, Time Converter, SQL Formatter, JWT Decoder, and Swagger Editor.