chriddyp

While this is true, there is also a layer in the harness between the output of _any_ tool output (eg stdout or hand-rolled tools) and the LLM. A tool could read the file but then the agentic harness could redact the output before returning it back to the llm if any of the contents matched the file contents. We do something similar in Plotly Studio where we check the entropy of strings in the user input and flag & redact any high entropy strings to the user as “potential credentials” thay the user might have inadvertently copied and pasted into the prompt before sending to the llm.

There are ways around this - the llm can always be clever by invoking tools to read the file contents in a different way than the direct file contents - but this is all to say that the agentic harness layer _does_ allow for deterministic logic in between tool output and the LLM requests.

This is really cool. And timely! Check out the recent paper by Google et al re "Societies of Thought": https://arxiv.org/html/2601.10825v1. It goes into how different conversational behaviors (raising questions or just say "but wait..."), perspective shifts, conflict of perspectives, tension, tension release (jokes!), asking for opinions) and different personalities (planner, expert, verifier, pragmatist) is both a sign of and can result in much higher performance reasoning.

So I'd be curious to see if encouraging certain conversational behaviors might actually improve the reasoning and maybe even drive towards consensus.

The issue goes beyond access and into whether or not the data is "trusted" as the malicious prompts are embedded within the data. And for many situations its hard to completely trust or verify the input data. Think [Little Bobby Tables](https://xkcd.com/327/)

Curious to see Apple using real black as background on their home page but rgb(29, 29, 31) for their black text.

FYI re Dash & HTML - If you aren't using your own stylesheets with HTML, then I'd recommend dash_bootstrap_components.

Here's an example that uses almost entirely higher level components: https://dash-bootstrap-components.opensource.faculty.ai/exam...

We've also been working on `dash.templates`, which provide opinionated, prebuilt UIs - no layout code required: https://community.plotly.com/t/introducing-dash-labs-dash-2-...

Plotly's 3D viz is built with WebGL & SVG, using libraries like regl & stack.gl. SVG is used for axes & text and WebGL for the high performance rendering of points and surfaces. Surfaces, lines, points, and subplots are all supported. See https://plotly.com/python/#3d-charts.

For more complex 3D objects, Dash users can use dash-vtk. This includes things like point clouds, CFD simulations, 3D mesh, or 3D images.

Hello HN! Nice to see this up here. Chris here, cofounder of Plotly.

Falcon is open source and works without an internet connection or a Plotly Chart Studio account. Falcon wires together our graphing library plotly.js (https://github.com/plotly/plotly.js/), the plotly.js chart editor (https://github.com/plotly/react-chart-editor), Electron, and some open source NPM packages for connecting to databases.

Just FYI - As a company (Plotly), we're spending most of our development effort these days on Dash Open Source (https://github.com/plotly/dash) and Dash Enterprise (https://plotly.com/dash). Truth be told, we found that most companies we worked with preferred to own the analytical backend. We also heard many stories of organizations running into roadblocks with off-the-shelf SQL or BI tools (Falcon included!). Our approach with Dash is to provide the visualization and application primitives so that you could build your own tailor-made dashboards, analytical apps, or yes, even SQL editors.

If you want to read more about where we're at, here's an essay we wrote last week on Dash: https://medium.com/plotly/dash-is-react-for-python-r-and-jul...