idode

always up to something. stuff i’ve built is in my highlights. prev: meta, intel.

[idode @idode_k]

“i was never going to be limited by hoodies and t-shirts… no matter how much it made sense” - virgil abloh

[idode @idode_k]

"you don't have to predict the future if you can see the present moment clearly."

[idode @idode_k]

you can't run from reality.

[idode @idode_k]

@_zidkim yep. writing is clarifying as always.

[idode @idode_k]

trying to write for 30 uninterrupted minutes really exposed how cooked my attention span really is

[idode @idode_k]

@_zidkim working through framing and positioning for the product. went through yc's app and had claude come up with a bunch of questions that are intended to force clear thinking and expose gaps

[idode @idode_k]

https://t.co/deFs1okVzG

[idode @idode_k]

reading sam presti press conference transcripts like they are warren buffet annual letters

[idode @idode_k]

@_zidkim gotta move as quickly as possible.

[idode @idode_k]

launch in 9 days. time to put belt to ass.

[idode @idode_k]

reading sam presti press conference transcripts like they are warren buffet annual letters

[idode @idode_k]

@_okdara_ @AoraBCI lets go!

[idode @idode_k]

@ohryansbelt @karpathy trying to figure out how they got him with the salary cap

[idode @idode_k]

it gets real interesting. stale context gets updated by a subagent that the main agent calls autonomously or that you could explicitly call to update something.

agents stepping on each other is still tricky*.
right now, it still takes a bit of manual curation and is best either having subfolders per person (tech leads own `./engineering/`, pm owns `./product/` etc.) or having someone take point on keeping things clean.

all changes are logged in a changes.jsonl file so there's explicit paper trail and you can have an agent manage overwrites/bad merge conflicts much the same way you could for code.

*but i'm also working on something new (and of course open source) that will make this much more seamless.

[Adrian @aelson389]

@idode_k Shared context is where things get interesting. How are you handling stale context and ownership when several agents edit the same files?

[idode @idode_k]

open source plugin for shared context across your entire team and all of your coding agents

[idode @idode_k]

i made a coding agent plugin (works across claude code, codex, cursor) that helps you share and collaborate on your team's shared context layer.

connect context across sessions via your local file system and share/collaborate on those files with your team.

github below.

[idode @idode_k]

@190k thank u!

[idode @idode_k]

i made a coding agent plugin (works across claude code, codex, cursor) that helps you share and collaborate on your team's shared context layer.

connect context across sessions via your local file system and share/collaborate on those files with your team.

github below.

[idode @idode_k]

@_zidkim thank u!

[idode @idode_k]

released/open sourced a plugin that has been helping me build and work with teammates for a while

[idode @idode_k]

i made a coding agent plugin (works across claude code, codex, cursor) that helps you share and collaborate on your team's shared context layer.

connect context across sessions via your local file system and share/collaborate on those files with your team.

github below.

[idode @idode_k]

mit license - https://t.co/tdhpQhEzkc

[idode @idode_k]

@Watch_Velocity lmao its based on real events wth

[idode @idode_k]

@Watch_Velocity this first scene is nuts