Feed aggregator

I built PrismoDev after noticing my Claude Code and Codex sessions were getting expensive in ways that were hard to explain.

After digging through local session logs, the recurring issue was not just model pricing. A lot of the waste came from context bloat: generated artifacts, logs, build output, oversized CLAUDE.md / AGENTS.md files, repeated tool output, broad repo exploration, stale session state, and command loops.

PrismoDev is a local CLI that scans a repo plus local Claude Code / Codex logs and tries to explain where token/context waste is coming from. It does not require API keys or login, and nothing leaves the machine.

A few commands:

```bash npx getprismo doctor ```

Scans the repo, flags missing `.claudeignore` / `.cursorignore`, oversized instruction files, generated artifacts exposed to agents, and creates compact `.prismo/` context summaries.

```bash npx getprismo watch ```

Monitors live context pressure during a coding session and warns about repeated file reads, artifact leaks, oversized tool output, and possible loops.

```bash npx getprismo cc timeline ```

Builds a postmortem timeline showing where context spikes, repeated reads, command loops, or generated artifacts appeared in a session.

There are also scoped context policies:

```bash npx getprismo firewall auth-bug ```

which creates a task-specific context boundary before starting work.

The main idea is to make AI coding sessions easier to reason about before the bill surprises you: what got loaded, what repeated, what could have been avoided, and what should be ignored next time.

Repo: https://github.com/shanirsh/prismodev

I’d be especially interested in feedback from people using Claude Code, Codex, Cursor, or similar tools on larger repos. I’m trying to tune the false positives and find more real-world waste patterns.

Comments URL: https://news.ycombinator.com/item?id=48200057

Points: 1

# Comments: 1

Article URL: https://old.reddit.com/r/programming/comments/1thewau/raven_software_released_the_jedi_academy_source/

Comments URL: https://news.ycombinator.com/item?id=48199756

Points: 1

# Comments: 0

In my day job, I run AI pentest agents against real targets like banks, fintechs, and secured production stacks with paid WAFs. I also deal with multilayer infrastructure and dedicated security teams. Despite these defenses, I keep finding high and critical vulnerabilities using just an LLM agent loop, a few open-source tools, MCP servers, and Burp Suite.

The volume of traffic is increasing quickly. Agent-driven activity in web logs has shifted from occasional noise to a constant background presence. Tools like PentestGPT, CAI, Strix, and HexStrike allow you to set up fully autonomous agents against any target for under a dollar an hour of API cost. Most teams haven’t noticed this change because their tools weren’t designed to detect it.

This repetition started to concern me. Despite all the paid WAFs, the rules, and the layered infrastructure, I could still guide an AI agent through a secured target and find critical issues. So what is the actual defense?

The realization that changed my perspective: blocking doesn’t work. A 403 error is simply a signal in an LLM's context window. The agent sees "defended here," updates its model, and pivots in milliseconds. Every block provides free information that shows the attacker where your weaknesses are.

That’s why I created VeilGate as a deception proxy, not just another blocker. It sits in front of your app and operates in modes such as `observe`, `challenge`, `tarpit`, or `auto`. Each request is scored based on protocol fingerprints, behavioral signals, and online machine learning. Requests below the threshold are forwarded to your main app normally. Ambiguous traffic receives a browser proof-of-work challenge. High-confidence agent traffic gets redirected into tarpit mode, where it encounters a deception layer instead of your actual app.

Comments URL: https://news.ycombinator.com/item?id=48199725

Points: 1

# Comments: 0

Article URL: https://thespinoff.co.nz/science/20-05-2026/the-latest-step-in-the-quest-to-de-extinct-the-moa-hatching-chicks-from-fake-eggs

Comments URL: https://news.ycombinator.com/item?id=48199703

Points: 1

# Comments: 0

Article URL: https://en.wikipedia.org/wiki/Auto-brewery_syndrome

Comments URL: https://news.ycombinator.com/item?id=48199701

Points: 1

# Comments: 0

Article URL: https://www.nature.com/articles/s43587-026-01121-2

Comments URL: https://news.ycombinator.com/item?id=48199699

Points: 1

# Comments: 0

Article URL: https://github.com/enforra/enforra

Comments URL: https://news.ycombinator.com/item?id=48199671

Points: 1

# Comments: 1

Article URL: https://twitter.com/perplexity_ai/status/2056749555346235704

Comments URL: https://news.ycombinator.com/item?id=48199641

Points: 1

# Comments: 0

Article URL: https://antigravity.google/blog/google-antigravity-built-an-os

Comments URL: https://news.ycombinator.com/item?id=48199639

Points: 3

# Comments: 4

Article URL: https://www.theverge.com/tech/932973/google-gmail-live-ai-keep-docs-io-2026

Comments URL: https://news.ycombinator.com/item?id=48199618

Points: 1

# Comments: 1

Article URL: https://www.amusingplanet.com/2023/04/the-telescope-that-got-shot.html

Comments URL: https://news.ycombinator.com/item?id=48199611

Points: 1

# Comments: 0

Article URL: https://techcrunch.com/2026/05/19/openai-co-founder-andrej-karpathy-joins-anthropics-pre-training-team/

Comments URL: https://news.ycombinator.com/item?id=48199609

Points: 3

# Comments: 0

Article URL: https://tminus.one/

Comments URL: https://news.ycombinator.com/item?id=48199598

Points: 2

# Comments: 2

Article URL: https://pinionengineering.github.io/storage-proofs/

Comments URL: https://news.ycombinator.com/item?id=48199586

Points: 1

# Comments: 1

Hi HN!

I've built a plugin for Obsidian that adds lightweight, highly customized, and native-feeling chart layouts (Bar, Line, Pie) specifically for the new database-like "Bases" feature.

Repository: https://github.com/zobweyt/obsidian-bases-chart-layouts Plugin page: https://community.obsidian.md/plugins/bases-chart-layouts

### The Problem

I needed a way to visualize my structured note data in Obsidian without the bloat. Existing chart solutions either required writing complex JavaScript inside codeblocks or felt like heavy web-views slapped onto the app.

I wanted charts that feel like a built-in, core feature of Obsidian—lightweight, snappy, and deeply integrated with the UI.

### What makes it "Native-Feeling"

It goes beyond basic SVG rendering to mimic Obsidian’s native desktop UX patterns:

- *Interactions:* Full support for `cmd/ctrl + click` and middle-click (`auxclick`) to open underlying data files in new tabs or split panes. - *Context Menus:* Right-clicking the chart triggers native Obsidian context menus, not generic browser ones. - *Theme Adaptation:* It doesn't just switch light/dark modes. It dynamically inherits your exact Obsidian theme CSS variables and fonts.

### Tech Stack & DX

I wanted to keep the codebase as clean as the UI:

* *No Node/NPM Boilerplate:* The entire project is built purely with Deno (fmt, lint, build). This kept the development environment exceptionally lightweight and fast. * *Rendering:* Powered by Apache ECharts under the hood for crisp vector rendering. The final plugin size is only ~1MB. * *I18n:* Built-in localization support (currently English and Russian).

### How to try it

1. Ensure you have Bases enabled in Obsidian. 2. Add a chart layout to your view. 3. Map your columns using the native Properties panel.

I’d love to hear your thoughts on the UX integration, and especially on using Deno for building Obsidian plugins. Any feedback or feature requests are welcome!

Comments URL: https://news.ycombinator.com/item?id=48199577

Points: 1

# Comments: 0

Article URL: https://twitter.com/addictedtoigno1/status/2056072770987970825

Comments URL: https://news.ycombinator.com/item?id=48199575

Points: 1

# Comments: 1

Hi HN,

I built Limitless because I wanted to create a unified, high-fidelity platform for Open Source Intelligence (OSINT), dark web collection, and interactive threat training.

Most cybersecurity training systems are either standard slide decks or text-heavy questionnaires. At the same time, actual analyst tools are scattered across hundreds of disconnected command-line scripts and API wrappers.

Limitless merges real analyst tools with a reactive, browser-based training simulator.

The Ecosystem Components: 1. *Feynman (OSINT search): An intelligence search engine that maps digital footprints, uncovers hidden connections, and aggregates intelligence across 200+ online sources instantly. 2. *Sentinel (Darknet Agent):* An autonomous AI agent designed for deep-web collection, learning, and reasoning across darknet forums. 3. *Interactive Training Sandboxes:* Scenario-driven tutorials that teach cybersecurity operations through visual tools: * GEOINT Simulator: Uses Leaflet and coordinates to calculate physical proximity (Haversine formula), supporting tolerance radii and partial scoring. * Steganography Lab: Toggles Red/Green/Blue color channels and bitplane depths on canvas elements dynamically in the browser. * Draggable Chronology & Classification: Drags event timelines and classifies logs using `@dnd-kit`. * Audio & Video Intel: Custom playback speed modulators and zoom canvas overlays.

Localization: Reactive, real-time translations supporting 9 languages (English, Spanish, Portuguese, French, Russian, Hebrew, Arabic, Japanese, and Hindi).

You can explore the interactive intelligence based sandboxes for learning directly https://limitless-osint.com/

I’d love to hear your feedback on the investigative tools (Feynman & Sentinel), the workspace user experience, or what intelligence tools you would like to see us build next.

Thanks!

Comments URL: https://news.ycombinator.com/item?id=48199574

Points: 1

# Comments: 0

Article URL: https://gisbi.me/blog/article-1779175137638

Comments URL: https://news.ycombinator.com/item?id=48199572

Points: 1

# Comments: 0

Article URL: https://thevarsity.ca/2026/03/15/the-enhanced-games-the-line-we-keep-moving/

Comments URL: https://news.ycombinator.com/item?id=48199554

Points: 1

# Comments: 0