parsak

16 ms·

1.
Doom, in a Terminal(twitter.com)
3 points by parsak 26d ago|1 comments
2.
Minecraft, in a Terminal(twitter.com)
4 points by parsak 26d ago|0 comments
3.
by parsak 6mo ago
the two-plane idea here is really interesting -- separating long-lived planners from short-lived workers is a clean mental model. curious what happens when you're on windows though? tmux + ttal means you're locked out of a decent
4.
by parsak 6mo ago
the way i handle it in pane: every pane is one worktree, and the diff viewer + keyboard shortcuts (squash, rebase, merge) are right there before you ever push. so the review step isn't a context switch -- it's just... the next thi
5.
by parsak 6mo ago
i built this because i was running claude code and cursor on the same repo and they kept overwriting each other's files -- that sentence is exactly what motivated pane too. git-lanes solves the isolation problem cleanly as a CLI layer.
6.
by parsak 6mo ago
the "containers manually vs compose" framing is exactly right -- that's the coordination layer that's missing from raw worktrees. one thing i'm curious about with chatml: how's the experience on windows and lin
7.
by parsak 6mo ago
the persistent markdown approach to context drift is clever - treating state files as a first-class primitive rather than hoping the agent remembers between sessions is the right instinct. one thing i've noticed: even with perfect cont
8.
by parsak 6mo ago
the "45 minutes watching one agent" framing is exactly right - the serial bottleneck is the real problem, not the model. one thing worth thinking through as shard matures: the management layer for those parallel agents running in
9.
by parsak 6mo ago
Cool concept with the Blueprints system - defining agent teams declaratively is a nice touch. I'm building something adjacent called Pane ( https://runpane.com ) that comes at it from the terminal management side rather than
10.
by parsak 6mo ago
The auto-snap detection is clever - automatically splitting when it detects an agent CLI is a great UX decision. I took a similar "own the terminal" approach with Pane ( https://runpane.com ), but organized around git wo
11.
by parsak 6mo ago
Nice work! The at-a-glance status monitoring is a great idea - the "what are all my agents doing right now" problem is real once you're running 4+ sessions. I'm working on something in the same space called Pane ( https:
12.
by parsak 6mo ago
Here's a more in depth writeup on the workflow: https://www.runpane.com/blog/ai-native-development-workflow
13.
by parsak 6mo ago
Oh, arguably the best part (which I forgot to mention) is that our terminals continue running in the cloud, so dev work isn't blocked by our computers going to sleep.
14.
300 Founders, 3M LOC, 0 engineers. Here's our workflow
2 points by parsak 6mo ago|4 comments
15.
by parsak 6mo ago
Fair enough - with that said - be mindful of the times. I am pretty deeply involved in Seattle's startup scenes and a notable startup recently laid off 35% of its engineers, and may lay off more, specifically because the engineering te
16.
by parsak 6mo ago
glad you feel the sentiment :) any in particular you recommend?
17.
by parsak 6mo ago
Fair enough, I spend a maximum of 200 a month given I use the MAX plan from CC. I don't find myself every hitting the weekly limits - but recently I've gotten close!
18.
Is anyone else drowning in terminal tabs running AI coding agents?
2 points by parsak 7mo ago|8 comments
19.
by parsak 2y ago
I wonder if you could make a workflow like this run well completely local. I might try to build it. I saw this fully local open source tool recently that helps categorize your photos and screenshots… https://www.reddit.com/r