$ npx chartli data.txt -t ascii -w 24 -h 8
8 chart types spanning a fun range of Unicode density:
- ascii (line charts with ββββ markers)
- spark (βββββ
βββ sparklines, one row per series)
- bars (horizontal, ββββ shading per series)
- columns (vertical grouped bars) Introducing chartli π
A CLI for rendering charts in your terminal from numeric text data.
$ πππ‘ πππππππ
I wanted terminal charts with zero setup. No browser, no Python env, no matplotlib. Pipe numbers in, get a chart out.
Again built it my coding taste using Command Code. 
Ever wondered what Cursor's Agent would feel like if it weren't running in Electron? You don't have to wonder anymore!
Buy and manage domains without leaving Railway π
railway.com/domains We're working on it right now!
ππππ
Swatantra Sohni with a strong reminder from the Community Showcase:
AI needs structure. Define requirements. Set expectations. Plan first, then build.
πΊ Full video: www.youtube.com/watch?v=oKpF... 
Log Drains are now on Pro
Send your Postgres, Auth, Storage, Edge Functions, and Realtime logs directly to Datadog, Sentry, Grafana Loki, Axiom, S3, or your own endpoint
Full-stack observability, no context switching
supabase.com/blog/log-drains-now-available-on-pro 
"If I took Bugbot away from our engineering team, there would be a mutiny."
How PlanetScale builds with Bugbot:
cursor.com/blog/planets... If your agent signs up for a service today, it gets treated like a scammer.
That is not a hot take. It is how bot defenses are designed to work.
So what replaces βprove you are humanβ when the user is an agent acting for a human?
biilmann.blog/articles/my-... Star the repo here
β³ github.com/ahmadawais/g... 
This is a preview. We're curious what you'll build with it, and we'd love to hear what you'd want to see before we fully launch.
Check out some API examples for inspiration: github.com/elicit/api-... Getting started:
1) Create an API key at elicit.com/settings
2) Give Claude or ChatGPT your question + the docs.
3) Run the script it writes or copy a code snippet from the docs and swap in your key.
Within a minute, get your first results from the Elicit API. Build on top of Elicit. Now you can build research dashboards or combine Elicit evidence with your own datasets. Integrate Elicit into your workflow. Call the API from Claude or ChatGPT to get real citations while writing a paper, or build a Slack bot that pulls evidence into team discussions. We built one internally to settle debates with data instead of anecdotes. 
Run research at scale. Got 30 compounds to check or 20 hypotheses to test? Write a short script and get structured results for all of them instead of running each one manually. The Elicit API is now available in preview for Pro and Teams users. You can search 138M+ papers and generate Research Reports from your code, scripts, or AI tools.
Get your API key at elicit.com/settings and check out docs.elicit.com 
this is possibly the coolest place I have ever visited
If you're building Node.js tools that search files, stop spawning subprocesses. Call a function.
While it has feature parity with ripgrep, i'm still building out a couple of optimizations that will make it even faster on large codebases. ignoreCase: true,
}));
// 17ΞΌs. No subprocess.
// No IPC.
// No stdout parsing.
```
Zod validates at the boundary.
Types inferred from schemas.
`readonly SearchResult[]` out, no mutation.
$ npm i grepts
$ pnpm i grepts `grepts-async` beats ripgrep 1.34x on common patterns, 3.33x on large files. Worker pool saturates I/O without subprocess setup per query.
```
import { search, searchOptionsSchema } from 'grepts';
const results = search(searchOptionsSchema.parse({
pattern: 'TODO',
paths: ['./src'], Per-invocation cost:
grepts (in-process) 17ΞΌs π€
ripgrep (subprocess) 7.6ms
grep (subprocess) 5.9ms
435x less overhead vs ripgrep. 1000 searches:
16ms vs 7.6s.