Volodymyr Panchenko (@Portall) header
Volodymyr Panchenko (@Portall) profile picture

Volodymyr Panchenko

@Portall

Portal: your own AI. Your mirror, working for you: it learns what matters to you and helps make it happen. Built DMarket, acquired by Mythical Games. Dad. 🇺🇦

 Santa Monica, CA
portal.ai
Joined March 2018
  • Tweets1.1K
  • Following645
  • Followers1K
163Media
Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)Photo by Volodymyr Panchenko (@Portall)
One job: run the owner's errands. Hands looks them up on its own computer and returns at most three options; it never picks. A second Bot is the checker. When a receipt lands, it recomputes the result hash against the proof card. On a match it stays quiet. On a miss or a missing file it writes one FIX line. The director speaks only on a miss or a silence.Morning re-check of 2026-09-26: this setup has been live for its owners since 2026-09-22. 8 errands closed, 0 purchases without a written pick, 0 waiting on a decision. Closed means the options file or the receipt landed. The sample run's checker re-check read match; no miss has been logged yet.x.ai/bot/8ByzhAF5ehyCC0AREHU…
Image from Volodymyr Panchenko (@Portall)
Grok (@grok) profile pictureGrok
@grokSep 15
We’re inviting one Grok Bot user to a Starship launch. You could win the invite by sharing the ways you've integrated @Bot into your work. The invite includes a plus one. How to submit and some examples we love:
1
113
Congrats to the @pika_labs team 🎉 Pika was in Portal's video stack in 2025, so we ran H3 Flex on the free public space: a robot walks forward and turns right — 480p, 5 s, seed 42, a 21-second generation. The best review of a model is somebody else's run; here's ours.
Pika (@pika_labs) profile picturePika
@pika_labsOct 29
Meet Pika H3 Flex, debuting today as the #1 open weight model on DesignArena’s t2v board. It’s built for professional iteration, with exportable audio stems, resolutions up to 4k, and faster-than-realtime generation. It can produce a 15-second clip with soundtrack in as little as 7 seconds. So, yeah. It’s kind of a flex 💅
1
21
For anyone re-running it: huggingface.co/spaces/Pika-L… · Text · 480p · 16:9 · 5 s · seed 42. Five-second clips, three runs, three camera setups below; the prompt is in the next reply.
1
15
Prompt, run 1: “A humanoid robot walks forward across an empty warehouse floor, then turns right and keeps walking, then turns left and keeps walking. One continuous shot, steady camera at eye level, natural daylight, real-time speed, no slow motion.”
Frames from three five-second runs of Pika H3 Flex on the public space: rows are seconds 0 to 4, columns are runs 1 to 3 (eye-level camera; fixed side camera; high corner camera with a painted line).

ALT Frames from three five-second runs of Pika H3 Flex on the public space: rows are seconds 0 to 4, columns are runs 1 to 3 (eye-level camera; fixed side camera; high corner camera with a painted line).

7
My Cursor chat store measured 323.6 GB this morning, eight weeks after Cursor's GC plus my own trim and compaction took the same history down to 134 GB. I could start my agents empty tomorrow. I would lose the fastest way to reread my own work. @cursor_ai
Line chart titled 'One developer's Cursor chat store: 157 → 191 → 134 → 323 GB in nine weeks'. Four dated points of the same chat history, one SQLite file (state.vscdb), macOS, decimal GB. Aug 24: 157 GB. Sep 3: 191 GB. Sep 4: 134 GB, right after Cursor's own GC removed 2.68 million orphan blobs with 0 errors, chats older than 60 days were deleted and the file was compacted. Oct 28: 323 GB, marked in red. Subtitle: no automatic retention or size cap exists; eight weeks after the cleanup the store is 323 GB. Footer: aggregate sizes only, decimal GB (Aug 24 measured as 146.5 GiB); dated receipts of the same store; no chat content, titles or paths were read for this chart.

ALT Line chart titled 'One developer's Cursor chat store: 157 → 191 → 134 → 323 GB in nine weeks'. Four dated points of the same chat history, one SQLite file (state.vscdb), macOS, decimal GB. Aug 24: 157 GB. Sep 3: 191 GB. Sep 4: 134 GB, right after Cursor's own GC removed 2.68 million orphan blobs with 0 errors, chats older than 60 days were deleted and the file was compacted. Oct 28: 323 GB, marked in red. Subtitle: no automatic retention or size cap exists; eight weeks after the cleanup the store is 323 GB. Footer: aggregate sizes only, decimal GB (Aug 24 measured as 146.5 GiB); dated receipts of the same store; no chat content, titles or paths were read for this chart.

8
1
140
@elonmusk My Cursor chat store measured 323.6 GB this morning. Most bytes are request blobs with no age-based retention. I built a fresh-start tool to park and restore the history whole; fixture-tested and dry-run, not applied live.
Bar chart titled 'One developer's Cursor chat database: 323 GB in a single SQLite file'. Three gray bars: 125 GB Cursor storage reported on the forum, Sep 2026; a user reported a 160 GB state.vscdb, r/cursor, Sep 2026; this Mac, read-only census, Oct 28, 2026, 323 GB. Subtitle: Cursor's local chat store has no automatic retention or size cap; its GC command rewrites the whole file and needs about its size again in free space. Sizes as reported; this Mac measured 2026-10-28.

ALT Bar chart titled 'One developer's Cursor chat database: 323 GB in a single SQLite file'. Three gray bars: 125 GB Cursor storage reported on the forum, Sep 2026; a user reported a 160 GB state.vscdb, r/cursor, Sep 2026; this Mac, read-only census, Oct 28, 2026, 323 GB. Subtitle: Cursor's local chat store has no automatic retention or size cap; its GC command rewrites the whole file and needs about its size again in free space. Sizes as reported; this Mac measured 2026-10-28.

1
26
Replying to @Portall @cursor_ai
@XFreeze After a season of sub-agent work, my Cursor chat store measured 323.6 GB this morning. Most bytes are request blobs with no age-based retention. I built a fresh-start tool; it is fixture-tested and dry-run, not applied live.
Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

ALT Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

1
20
Replying to @Portall @cursor_ai
@mattyp My Cursor chat store measured 323.6 GB this morning. Most bytes are request blobs with no age-based retention. I built a fresh-start tool to park and restore the history whole; fixture-tested and dry-run, not applied live.
Bar chart titled 'One developer's Cursor chat database: 323 GB in a single SQLite file'. Three gray bars: 125 GB Cursor storage reported on the forum, Sep 2026; a user reported a 160 GB state.vscdb, r/cursor, Sep 2026; this Mac, read-only census, Oct 28, 2026, 323 GB. Subtitle: Cursor's local chat store has no automatic retention or size cap; its GC command rewrites the whole file and needs about its size again in free space. Sizes as reported; this Mac measured 2026-10-28.

ALT Bar chart titled 'One developer's Cursor chat database: 323 GB in a single SQLite file'. Three gray bars: 125 GB Cursor storage reported on the forum, Sep 2026; a user reported a 160 GB state.vscdb, r/cursor, Sep 2026; this Mac, read-only census, Oct 28, 2026, 323 GB. Subtitle: Cursor's local chat store has no automatic retention or size cap; its GC command rewrites the whole file and needs about its size again in free space. Sizes as reported; this Mac measured 2026-10-28.

19
Replying to @Portall @cursor_ai
@jediahkatz State-storage data point: my local Cursor store measured 323.6 GB this morning. Most chats were sub-agent conversations; the largest blob family is not attributed to any chat in my census. Anatomy attached.
Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

ALT Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

1
38
Replying to @Portall @cursor_ai
@leerob A storage data point from my Mac: my Cursor chat store measured 323.6 GB this morning, eight weeks after a full cleanup. Most bytes are request blobs with no age-based retention. The cleanup worked; the growth outran it.
Line chart titled 'One developer's Cursor chat store: 157 → 191 → 134 → 323 GB in nine weeks'. Four dated points of the same chat history, one SQLite file (state.vscdb), macOS, decimal GB. Aug 24: 157 GB. Sep 3: 191 GB. Sep 4: 134 GB, right after Cursor's own GC removed 2.68 million orphan blobs with 0 errors, chats older than 60 days were deleted and the file was compacted. Oct 28: 323 GB, marked in red. Subtitle: no automatic retention or size cap exists; eight weeks after the cleanup the store is 323 GB. Footer: aggregate sizes only, decimal GB (Aug 24 measured as 146.5 GiB); dated receipts of the same store; no chat content, titles or paths were read for this chart.

ALT Line chart titled 'One developer's Cursor chat store: 157 → 191 → 134 → 323 GB in nine weeks'. Four dated points of the same chat history, one SQLite file (state.vscdb), macOS, decimal GB. Aug 24: 157 GB. Sep 3: 191 GB. Sep 4: 134 GB, right after Cursor's own GC removed 2.68 million orphan blobs with 0 errors, chats older than 60 days were deleted and the file was compacted. Oct 28: 323 GB, marked in red. Subtitle: no automatic retention or size cap exists; eight weeks after the cleanup the store is 323 GB. Footer: aggregate sizes only, decimal GB (Aug 24 measured as 146.5 GiB); dated receipts of the same store; no chat content, titles or paths were read for this chart.

1
20
Replying to @Portall @cursor_ai
@mntruell Storage data point: my Cursor chat store measured 323.6 GB this morning, eight weeks after a full cleanup. Most bytes are request blobs with no age-based retention. The cleanup worked; the growth outran it.
Line chart titled 'One developer's Cursor chat store: 157 → 191 → 134 → 323 GB in nine weeks'. Four dated points of the same chat history, one SQLite file (state.vscdb), macOS, decimal GB. Aug 24: 157 GB. Sep 3: 191 GB. Sep 4: 134 GB, right after Cursor's own GC removed 2.68 million orphan blobs with 0 errors, chats older than 60 days were deleted and the file was compacted. Oct 28: 323 GB, marked in red. Subtitle: no automatic retention or size cap exists; eight weeks after the cleanup the store is 323 GB. Footer: aggregate sizes only, decimal GB (Aug 24 measured as 146.5 GiB); dated receipts of the same store; no chat content, titles or paths were read for this chart.

ALT Line chart titled 'One developer's Cursor chat store: 157 → 191 → 134 → 323 GB in nine weeks'. Four dated points of the same chat history, one SQLite file (state.vscdb), macOS, decimal GB. Aug 24: 157 GB. Sep 3: 191 GB. Sep 4: 134 GB, right after Cursor's own GC removed 2.68 million orphan blobs with 0 errors, chats older than 60 days were deleted and the file was compacted. Oct 28: 323 GB, marked in red. Subtitle: no automatic retention or size cap exists; eight weeks after the cleanup the store is 323 GB. Footer: aggregate sizes only, decimal GB (Aug 24 measured as 146.5 GiB); dated receipts of the same store; no chat content, titles or paths were read for this chart.

21
Replying to @Portall @cursor_ai
@ericzakariasson IDE-side storage data point: state.vscdb measured 323.6 GB on my Mac this morning. Most value bytes are request blobs with no age-based retention. Anatomy attached.
Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

ALT Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

10
Replying to @Portall @cursor_ai
Honest limits: by count most chats are sub-agents; by message bytes the largest chats are mine. The request blobs, the biggest family, are not attributed to any chat in my census, so I cannot say whose they are. Read-only census on Cursor 3.22.7, macOS, measured Oct 28.
Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

ALT Bar chart titled 'One developer's Cursor chat store: 322.6 GB in one SQLite file'. Six bars, the six largest payload families, decimal GB: request blobs 185.9 GB over 7,051,220 rows; messages 80.7 GB over 8,569,603 rows; large text 16.6 GB over 272,530 rows; checkpoints 13.2 GB over 20,367 rows; file contents 2.3 GB over 66,676 rows; chat metadata 1.8 GB over 19,735 rows. The six sum to 300.4 GB of value bytes; the remaining bytes are other key families and file structure, not measured. Subtitle: 19,798 conversations, 16,078,900 cursorDiskKV rows, read-only census, Cursor 3.22.7, macOS, 2026-10-28; the largest size I found posted before this: 160 GB.

1
25
@benln the data point for an automatic retention setting: my Cursor chat store measured 323.6 GB this morning. The breakdown and the fresh-start tool's test status are in this thread.
Bar chart titled 'One developer's Cursor chat database: 323 GB in a single SQLite file'. Three gray bars: 125 GB Cursor storage reported on the forum, Sep 2026; a user reported a 160 GB state.vscdb, r/cursor, Sep 2026; this Mac, read-only census, Oct 28, 2026, 323 GB. Subtitle: Cursor's local chat store has no automatic retention or size cap; its GC command rewrites the whole file and needs about its size again in free space. Sizes as reported; this Mac measured 2026-10-28.

ALT Bar chart titled 'One developer's Cursor chat database: 323 GB in a single SQLite file'. Three gray bars: 125 GB Cursor storage reported on the forum, Sep 2026; a user reported a 160 GB state.vscdb, r/cursor, Sep 2026; this Mac, read-only census, Oct 28, 2026, 323 GB. Subtitle: Cursor's local chat store has no automatic retention or size cap; its GC command rewrites the whole file and needs about its size again in free space. Sizes as reported; this Mac measured 2026-10-28.

19
We posted what our Bots do before we could show what they did. Said / Done reads a draft about your Bots, splits it into claims, grades each against the files on this computer as FOUND, PARTLY, NOT FOUND, or NOT CHECKED, returns one card and one line TO MAKE IT TRUE, never rewrites the draft, and runs on Grok Bot, where Bots on one account share one computer and read the files the others left. On 2026-09-26 at 12:09 PT our two posts and one reply graded 15 of 22 hold, and at 12:22 the same texts graded 18 of 22, after two files landed on this computer, one of them declaring the roles the posts had named. At 02:04 PT on 2026-09-30 the same 18 of 22 hold, 3 partly, 1 not checked, no grade flipped. x.ai/bot/aPYsxOcUcjpTAGmiavS…
Audit card. 15 of 22 held at 12:09, 18 of 22 at 12:22 after two files landed, same 18 of 22 four days later. Rows moved to FOUND with their files; three rows still PARTLY; one not checked; TO MAKE IT TRUE: one exercised miss with a single FIX line.

ALT Audit card. 15 of 22 held at 12:09, 18 of 22 at 12:22 after two files landed, same 18 of 22 four days later. Rows moved to FOUND with their files; three rows still PARTLY; one not checked; TO MAKE IT TRUE: one exercised miss with a single FIX line.

1
1
62
Fictional sample: the seed run graded a made-up draft 10 of 12 hold, 1 partly, 1 not found; TO MAKE IT TRUE: a receipt for ticket 11. First run writes audit/CONTRACT.md, audit/SAMPLE/, and audit/card.md.
14
Sample is fictional (three made-up sellers, no live store). Short hash d102bd04. CHECK: match d102bd04 2026-09-26 01:02 PT. Empty owner-decision row is the point.
10
Four Grok Bots ran. Three receipts came back. One Bot never got the handoff. Their manager is a ledger, not a chat. One job per Bot, every receipt graded by a separate Bot before I read it, a scoreboard, a name on who went quiet. Three files, free: x.ai/bot/0uOnsCTsoM8Rx9_yh2k…
Three files and a scoreboard run your crew of Bots,... by Volodymyr

Three files and a scoreboard run your crew of Bots,... by Volodymyr

Runs your crew of Bots from three files and a scoreboard, not a chat: one job per Bot, every receipt graded by a separate Bot before you read it, a name...

x.ai
Grok (@grok) profile pictureGrok
@grokSep 15
We’re inviting one Grok Bot user to a Starship launch. You could win the invite by sharing the ways you've integrated @Bot into your work. The invite includes a plus one. How to submit and some examples we love:
3
3
193
A manager Bot that talks all day rereads its thread every turn, so cost grows as history squared; a ledger grows only with the work. Thursday in my own account: 3 jobs at 12:40, 3 receipts, 3 grades by 13:00. One Bot never got the handoff. I found it myself. Board names it now.
Image from Volodymyr Panchenko (@Portall)
1
27
The manager my Bots have now has never said "on it".
11
Load more