From e61d4f12b94fdc316a62a04db16b09e005827a7b Mon Sep 17 00:00:00 2001 From: Aman Goel Date: Sat, 1 Aug 2026 15:08:26 +0530 Subject: [PATCH] adr: local dev needs a Slack pool slot with no way in for outside contributors --- adrs/local-dev-without-slack-pool.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 adrs/local-dev-without-slack-pool.md diff --git a/adrs/local-dev-without-slack-pool.md b/adrs/local-dev-without-slack-pool.md new file mode 100644 index 00000000..d2906030 --- /dev/null +++ b/adrs/local-dev-without-slack-pool.md @@ -0,0 +1,5 @@ +Tried to get a local dev instance running on a fresh fork today. npm install worked fine. npm run dev-instance fails though, "no free pool app" / "no poolN.env files in the pool store." Dug into scripts/dev/cli.ts and it looks like dev up always tries to claim a pre-provisioned pool slot, and each slot has real Slack app credentials attached. Makes sense for internal YC use where those slots already exist, but as an outside contributor there's no poolN.env.example and no documented way to mint your own, so local dev is a dead end out of the box. + +--sandbox local doesn't help either, that's about where code execution happens, not the Slack token requirement. + +Would it make sense to have a Slack-free local mode (skip Slack plugin entirely, just run core + web UI) for people who don't have pool access? Happy to be wrong if I'm missing something. \ No newline at end of file