2026 needs a new CSV format that supports multiple sheets and that doesn't require escaping.
ASCII US (Unit Separator) for comma
ASCII RS (Record Separator) for newline
ASCII GS (Group Separator) between worksheets
*maybe* ASCII FS (File Separator) for embedded images
Three header rows:
1. name of worksheet
2. Names (like usual)
3. Types (string, int, date, etc)
Editors should treat Unit Separator like tab, except that it should be calculated to the data-width and data can wrap within the column based on maximum display width or column width. RS should obviously represent rows, and GS for tabs.
Binary data must be hex encoded (because it compresses better than base64). Any data containing those control characters or other non-printing, non-UTF characters is considered binary.
Metadata can be stored in a group before the worksheet begins. Lines starting with `#` and followed by `.` and no other separator until GS can be used to pad groups to a rounded standard size to avoid full-file rewrites on simple metadata or single-value update.
No formulas or user-oriented spreadsheet stuff. This is just a data format for APIs and AIs.
@kaihendry@huggingface@badlogicgames@luebken You probably can't go full 1,000,000 tokens with just 48gb, but I haven't done the math on it. I just know that with 32gb I can't even get to a full 100,000.
And this is how I'm running llama.cpp, which has some options to keep the kv cache working, which keeps it fast even as the conversation gets longer.
```
./build/bin/llama-server \
--verbose \
--metrics \
--api-key-file ~/.config/agents/tokens.txt \
--n-gpu-layers 99 \
--ctx-size 1001000 \
--no-context-shift \
--host 0.0.0.0 --port 11234 \
-np 4 --cont-batching \
-hf unsloth/Qwen3.6-35B-A3B-GGUF:UD-Q4_K_XL \
--temp 0.6 \
--top-p 0.95 \
--top-k 20 \
--min-p 0.0 \
--presence-penalty 0.0 \
--repeat-penalty 1.0
```
(right now the model id in my pi config is being ignored, but there's another flag I could use in llama.cpp which would allow the codent agent to pick models based on the name)
You should be able to run 150k context with that, maybe even 2 such parallel agents.
Based on my experience I wouldn't push it beyond that -even though you might be able to fit the full 250k - because it becomes slower and less accurate in that range.
You may be able to use the 27 dense model as well - which is more accurate, but too slow for my M2.
My 32gb M1 maxes out a little past 85k, and it's only slightly slower. Still usable, but only 1 agent at a time.
Also know that a simpler harness with a lightweight system prompt like Pi will have a much snappier start-up / TTFT.
Despite being a local-first guy, I honestly - all bias aside - did not expect this:
I prefer Pi + Qwen 3.6 a3b over Claude + Opus 4.6.
I've retooled my M2 Studio 64gb such that it's only job is serving llama.cpp via port-forward and I use it from everywhere - including on my most recent flight.
This is good.
@chifugah@gonenb@mholt6 At the time the drives were around $300 each. 8 of those, plus the metadata and sync log ssds, server, CPUs, RAM, etc ended up being around 5k.
Total drive capacity is 200tb but 2 x 25tb goes to RAIDZ2,
@MartinAmmerlaan@mholt6 It's an r630 with ZRAID2 - actually 200TB, minus redundancy.
The metadata mirror keeps browsing and searching very fast. The sync log mirror keeps writes relatively fast. Cache is not necessary as there's plenty of RAM. There's a cold spare in the cabinet.
@SpaceGliderX@mholt6 The enterprise term is "employee endpoint backup" - but thankfully it's all encrypted snapshots sent by the backup client, so those incidences are 100% in their wheelhouse.
@gonenb@mholt6 Well, my office lab has about 10TB of Linux ISOs that is but the enterprise stuff...
well... it has a lot of office computer backups so probably quite a bit of the former - but they're encrypted snapshots, thankfully, so that's not my problem.
@mholt6 I run a small enterprise cluster for a handful of customers.
I bought the 150tb in anticipation of a deal that ended up not going through - but I've got a few customers on it and now that everything has gone crazy, it gives me peace of mind to have compute and storage to spare.
@thdxr I have not heard anyone familiar with btrfs recommend it for casual users - even among people who like it.
Both Proxmox and RedHat have dropped plans for future production integration.
Can we get a little more than just "trust me"?