man.. opensource is getting so good. I couldnt wait to set this up and play with it.. until my "wonderful" windows OS did its thing again...
opensource is absolutely revolutionary but I dont think people still talk enough about how big of an obstacle installing it could be, especially for non technical people
I ran the quickstart install process: npx paperclipai onboard --yes
and my windows machine just absolutely sh*t the bed trying to run it
without blprnt figuring out and doing 98% of the set up work by itself on my machine to get this running, I would have given up long ago
for someone who loves playing with all the new game changing opensource tools that come out daily I simply wouldnt be able to with my blprnt running the show.
this one blprnt use case has been incredible for a non technical person who wants to be test and using all this new tech
Here is everything blprnt had to do for me while I sat around watching:
------------------------------------------------
1. Initial issue
Paperclip installed, but would not start on Windows because embedded PostgreSQL failed during initialization.
Error:
Postgres init script exited with code 1
failure during: performing post-bootstrap initialization ...
What blprnt did:
- Mapped the repo to find the real startup path
- Traced the embedded Postgres boot code
- Confirmed the failure was happening inside embedded PostgreSQL, not in your app code
- Deleted the broken embedded DB directory and reran the app to verify whether it was just corrupted local state
Result:
- Confirmed it was not just a dirty DB folder
- Identified embedded Postgres on this Windows machine as the real problem
2. Secondary issue
The repo checkout was missing local dependencies after rerun.
Error:
'tsx' is not recognized as an internal or external command
node_modules missing
What blprnt did:
- Diagnosed the missing dependency state
- Had the project dependencies installed in the repo
Solution applied:
pnpm install
3. Confirmation step
Embedded Postgres still failed even after removing the old DB directory and reinstalling dependencies.
What blprnt did:
- Reproduced the startup failure cleanly
- Verified the same exact Postgres init failure came back
- Ruled out “bad install” and “leftover DB files” as the main cause
Result:
- Decided to bypass embedded Postgres completely
4. Alternative path issue
Docker was not available, so a containerized Postgres setup was not possible.
Error:
docker command not found
What blprnt did:
- Checked the machine environment
- Confirmed Docker was unavailable
- Chose the next best path: install native PostgreSQL on Windows
5. PostgreSQL not installed
PostgreSQL was not already on the machine.
What blprnt did:
- Checked for `psql`, `postgres`, and Windows PostgreSQL services
- Confirmed none were installed
- Identified `winget` as the fastest available install path
- Installed PostgreSQL 16 for you
Solution applied:
winget install --id PostgreSQL.PostgreSQL.16 -e --accept-package-agreements --accept-source-agreements
6. Database setup issue
Paperclip needed a database, user, and password, but the installer did not expose the postgres superuser password.
What blprnt did:
- Diagnosed the local auth configuration
- Determined the smallest workable path was temporary auth adjustment
- Guided the setup so the Paperclip DB/user existed and were ready to use
Solution applied:
Created:
- role: paperclip
- password: paperclip
- database: paperclip
Connection string:
postgres://paperclip:[email protected]:5432/paperclip
7. External Postgres startup issue
Paperclip then failed with:
Error:
the database system is starting up
What blprnt did:
- Investigated PostgreSQL service state and logs
- Determined the DB was in crash recovery, not permanently broken
- Confirmed recovery completed and that PostgreSQL became ready to accept connections
Result:
- External PostgreSQL was usable
8. Paperclip launch fix
Paperclip needed to be started against external PostgreSQL instead of falling back to embedded PostgreSQL.
What blprnt did:
- Determined the correct runtime configuration
- Gave the exact launch command using `DATABASE_URL`
- Verified Paperclip successfully started and applied migrations
Solution applied:
cd "C:\Users\maxch\OneDrive\Desktop\blprnt projects\blprnt marketing\paperclip-0.3.1"
$env:DATABASE_URL="postgres://paperclip:[email protected]:5432/paperclip"
pnpm dev:once
9. Filesystem/path issue
The repo was inside OneDrive Desktop, which is a bad place for Windows dev tooling and can cause extra filesystem permission and linking problems.
What blprnt did:
- Identified OneDrive as a likely source of additional friction
- Recommended moving the repo to a plain local path
- Helped sequence the move correctly after the running process was stopped
Solution applied:
Moved repo from:
C:\Users\maxch\OneDrive\Desktop\blprnt projects\blprnt marketing\paperclip-0.3.1
to:
C:\paperclip\paperclip-0.3.1
10. Post-move dependency issue
After moving the repo, the dependency install in the new path was stale/broken.
Error:
Cannot find module ...\server\node_modules\tsx\dist\cli.mjs
What blprnt did:
- Diagnosed the missing module as a moved-install problem
- Identified the fix immediately instead of chasing a fake code bug
Solution applied:
cd "C:\paperclip\paperclip-0.3.1"
pnpm install
11. Current issue
Paperclip now gets much farther, but fails when trying to create a Windows directory symlink for Claude skills.
Error:
EPERM: operation not permitted, symlink
'C:\paperclip\paperclip-0.3.1\skills\create-agent-adapter'
->
'C:\Users\...\AppData\Local\Temp\paperclip-skills-...\ .claude\skills\create-agent-adapter'
What blprnt did:
- Traced the exact code path creating the symlink
- Identified the failing adapter logic
- Confirmed this is a Windows symlink permission problem, not a Paperclip database problem
- Confirmed Paperclip is using directory symlinks where Windows often wants Developer Mode, elevation, or junctions
Root cause:
- Windows is blocking `fs.symlink()` for Paperclip’s skill directory linking
12. Current solution to apply
Enable Windows Developer Mode, then rerun Paperclip.
Launch command:
cd "C:\paperclip\paperclip-0.3.1"
$env:DATABASE_URL="postgres://paperclip:[email protected]:5432/paperclip"
pnpm dev:once
13. If Developer Mode does not fix it
What blprnt already determined:
- The correct code-level fix is to patch Paperclip so Windows uses junctions instead of symlinks for skills
Next fallback options:
- Run Paperclip from an Administrator terminal
- Or patch the repo to use Windows junctions for skill links
Summary of what blprnt saved you from doing manually
- Mapped the codebase and found the real startup architecture
- Diagnosed the embedded Postgres failure path
- Reproduced and ruled out false causes
- Installed and validated external PostgreSQL
- Helped set up the Paperclip DB/user path
- Diagnosed crash-recovery behavior in PostgreSQL
- Verified the exact launch configuration Paperclip needed
- Identified OneDrive as a bad repo location and helped move it
- Diagnosed the moved dependency failure
- Traced the current EPERM symlink issue to the exact adapter code and Windows behavior
Net result
- Paperclip is no longer blocked by embedded Postgres
- The remaining blocker is now isolated to one specific Windows symlink issue in skill injection
- That is a much smaller, cleaner problem than the mess we started with
man.. opensource is getting so good. I couldnt wait to set this up and play with it.. until my "wonderful" windows OS did its thing again...
opensource is absolutely revolutionary but I dont think people still talk enough about how big of an obstacle installing it could be, especially for non technical people
I ran the quickstart install process: npx paperclipai onboard --yes
and my windows machine just absolutely sh*t the bed trying to run it
without blprnt figuring out and doing 98% of the set up work by itself on my machine to get this running, I would have given up long ago
for someone who loves playing with all the new game changing opensource tools that come out daily I simply wouldnt be able to with my blprnt running the show.
this one blprnt use case has been incredible for a non technical person who wants to be test and using all this new tech
Here is everything blprnt had to do for me while I sat around watching:
------------------------------------------------
1. Initial issue
Paperclip installed, but would not start on Windows because embedded PostgreSQL failed during initialization.
Error:
Postgres init script exited with code 1
failure during: performing post-bootstrap initialization ...
What blprnt did:
- Mapped the repo to find the real startup path
- Traced the embedded Postgres boot code
- Confirmed the failure was happening inside embedded PostgreSQL, not in your app code
- Deleted the broken embedded DB directory and reran the app to verify whether it was just corrupted local state
Result:
- Confirmed it was not just a dirty DB folder
- Identified embedded Postgres on this Windows machine as the real problem
2. Secondary issue
The repo checkout was missing local dependencies after rerun.
Error:
'tsx' is not recognized as an internal or external command
node_modules missing
What blprnt did:
- Diagnosed the missing dependency state
- Had the project dependencies installed in the repo
Solution applied:
pnpm install
3. Confirmation step
Embedded Postgres still failed even after removing the old DB directory and reinstalling dependencies.
What blprnt did:
- Reproduced the startup failure cleanly
- Verified the same exact Postgres init failure came back
- Ruled out “bad install” and “leftover DB files” as the main cause
Result:
- Decided to bypass embedded Postgres completely
4. Alternative path issue
Docker was not available, so a containerized Postgres setup was not possible.
Error:
docker command not found
What blprnt did:
- Checked the machine environment
- Confirmed Docker was unavailable
- Chose the next best path: install native PostgreSQL on Windows
5. PostgreSQL not installed
PostgreSQL was not already on the machine.
What blprnt did:
- Checked for `psql`, `postgres`, and Windows PostgreSQL services
- Confirmed none were installed
- Identified `winget` as the fastest available install path
- Installed PostgreSQL 16 for you
Solution applied:
winget install --id PostgreSQL.PostgreSQL.16 -e --accept-package-agreements --accept-source-agreements
6. Database setup issue
Paperclip needed a database, user, and password, but the installer did not expose the postgres superuser password.
What blprnt did:
- Diagnosed the local auth configuration
- Determined the smallest workable path was temporary auth adjustment
- Guided the setup so the Paperclip DB/user existed and were ready to use
Solution applied:
Created:
- role: paperclip
- password: paperclip
- database: paperclip
Connection string:
postgres://paperclip:[email protected]:5432/paperclip
7. External Postgres startup issue
Paperclip then failed with:
Error:
the database system is starting up
What blprnt did:
- Investigated PostgreSQL service state and logs
- Determined the DB was in crash recovery, not permanently broken
- Confirmed recovery completed and that PostgreSQL became ready to accept connections
Result:
- External PostgreSQL was usable
8. Paperclip launch fix
Paperclip needed to be started against external PostgreSQL instead of falling back to embedded PostgreSQL.
What blprnt did:
- Determined the correct runtime configuration
- Gave the exact launch command using `DATABASE_URL`
- Verified Paperclip successfully started and applied migrations
Solution applied:
cd "C:\Users\maxch\OneDrive\Desktop\blprnt projects\blprnt marketing\paperclip-0.3.1"
$env:DATABASE_URL="postgres://paperclip:[email protected]:5432/paperclip"
pnpm dev:once
9. Filesystem/path issue
The repo was inside OneDrive Desktop, which is a bad place for Windows dev tooling and can cause extra filesystem permission and linking problems.
What blprnt did:
- Identified OneDrive as a likely source of additional friction
- Recommended moving the repo to a plain local path
- Helped sequence the move correctly after the running process was stopped
Solution applied:
Moved repo from:
C:\Users\maxch\OneDrive\Desktop\blprnt projects\blprnt marketing\paperclip-0.3.1
to:
C:\paperclip\paperclip-0.3.1
10. Post-move dependency issue
After moving the repo, the dependency install in the new path was stale/broken.
Error:
Cannot find module ...\server\node_modules\tsx\dist\cli.mjs
What blprnt did:
- Diagnosed the missing module as a moved-install problem
- Identified the fix immediately instead of chasing a fake code bug
Solution applied:
cd "C:\paperclip\paperclip-0.3.1"
pnpm install
11. Current issue
Paperclip now gets much farther, but fails when trying to create a Windows directory symlink for Claude skills.
Error:
EPERM: operation not permitted, symlink
'C:\paperclip\paperclip-0.3.1\skills\create-agent-adapter'
->
'C:\Users\...\AppData\Local\Temp\paperclip-skills-...\ .claude\skills\create-agent-adapter'
What blprnt did:
- Traced the exact code path creating the symlink
- Identified the failing adapter logic
- Confirmed this is a Windows symlink permission problem, not a Paperclip database problem
- Confirmed Paperclip is using directory symlinks where Windows often wants Developer Mode, elevation, or junctions
Root cause:
- Windows is blocking `fs.symlink()` for Paperclip’s skill directory linking
12. Current solution to apply
Enable Windows Developer Mode, then rerun Paperclip.
Launch command:
cd "C:\paperclip\paperclip-0.3.1"
$env:DATABASE_URL="postgres://paperclip:[email protected]:5432/paperclip"
pnpm dev:once
13. If Developer Mode does not fix it
What blprnt already determined:
- The correct code-level fix is to patch Paperclip so Windows uses junctions instead of symlinks for skills
Next fallback options:
- Run Paperclip from an Administrator terminal
- Or patch the repo to use Windows junctions for skill links
Summary of what blprnt saved you from doing manually
- Mapped the codebase and found the real startup architecture
- Diagnosed the embedded Postgres failure path
- Reproduced and ruled out false causes
- Installed and validated external PostgreSQL
- Helped set up the Paperclip DB/user path
- Diagnosed crash-recovery behavior in PostgreSQL
- Verified the exact launch configuration Paperclip needed
- Identified OneDrive as a bad repo location and helped move it
- Diagnosed the moved dependency failure
- Traced the current EPERM symlink issue to the exact adapter code and Windows behavior
Net result
- Paperclip is no longer blocked by embedded Postgres
- The remaining blocker is now isolated to one specific Windows symlink issue in skill injection
- That is a much smaller, cleaner problem than the mess we started with
man.. opensource is getting so good. I couldnt wait to set this up and play with it.. until my "wonderful" windows OS did its thing again...
opensource is absolutely revolutionary but I dont think people still talk enough about how big of an obstacle installing it could be, especially for non technical people
I ran the quickstart install process: npx paperclipai onboard --yes
and my windows machine just absolutely sh*t the bed trying to run it
without blprnt figuring out and doing 98% of the set up work by itself on my machine to get this running, I would have given up long ago
for someone who loves playing with all the new game changing opensource tools that come out daily I simply wouldnt be able to with my blprnt running the show.
this one blprnt use case has been incredible for a non technical person who wants to be test and using all this new tech
Here is everything blprnt had to do for me while I sat around watching:
------------------------------------------------
1. Initial issue
Paperclip installed, but would not start on Windows because embedded PostgreSQL failed during initialization.
Error:
Postgres init script exited with code 1
failure during: performing post-bootstrap initialization ...
What blprnt did:
- Mapped the repo to find the real startup path
- Traced the embedded Postgres boot code
- Confirmed the failure was happening inside embedded PostgreSQL, not in your app code
- Deleted the broken embedded DB directory and reran the app to verify whether it was just corrupted local state
Result:
- Confirmed it was not just a dirty DB folder
- Identified embedded Postgres on this Windows machine as the real problem
2. Secondary issue
The repo checkout was missing local dependencies after rerun.
Error:
'tsx' is not recognized as an internal or external command
node_modules missing
What blprnt did:
- Diagnosed the missing dependency state
- Had the project dependencies installed in the repo
Solution applied:
pnpm install
3. Confirmation step
Embedded Postgres still failed even after removing the old DB directory and reinstalling dependencies.
What blprnt did:
- Reproduced the startup failure cleanly
- Verified the same exact Postgres init failure came back
- Ruled out “bad install” and “leftover DB files” as the main cause
Result:
- Decided to bypass embedded Postgres completely
4. Alternative path issue
Docker was not available, so a containerized Postgres setup was not possible.
Error:
docker command not found
What blprnt did:
- Checked the machine environment
- Confirmed Docker was unavailable
- Chose the next best path: install native PostgreSQL on Windows
5. PostgreSQL not installed
PostgreSQL was not already on the machine.
What blprnt did:
- Checked for `psql`, `postgres`, and Windows PostgreSQL services
- Confirmed none were installed
- Identified `winget` as the fastest available install path
- Installed PostgreSQL 16 for you
Solution applied:
winget install --id PostgreSQL.PostgreSQL.16 -e --accept-package-agreements --accept-source-agreements
6. Database setup issue
Paperclip needed a database, user, and password, but the installer did not expose the postgres superuser password.
What blprnt did:
- Diagnosed the local auth configuration
- Determined the smallest workable path was temporary auth adjustment
- Guided the setup so the Paperclip DB/user existed and were ready to use
Solution applied:
Created:
- role: paperclip
- password: paperclip
- database: paperclip
Connection string:
postgres://paperclip:[email protected]:5432/paperclip
7. External Postgres startup issue
Paperclip then failed with:
Error:
the database system is starting up
What blprnt did:
- Investigated PostgreSQL service state and logs
- Determined the DB was in crash recovery, not permanently broken
- Confirmed recovery completed and that PostgreSQL became ready to accept connections
Result:
- External PostgreSQL was usable
8. Paperclip launch fix
Paperclip needed to be started against external PostgreSQL instead of falling back to embedded PostgreSQL.
What blprnt did:
- Determined the correct runtime configuration
- Gave the exact launch command using `DATABASE_URL`
- Verified Paperclip successfully started and applied migrations
Solution applied:
cd "C:\Users\maxch\OneDrive\Desktop\blprnt projects\blprnt marketing\paperclip-0.3.1"
$env:DATABASE_URL="postgres://paperclip:[email protected]:5432/paperclip"
pnpm dev:once
9. Filesystem/path issue
The repo was inside OneDrive Desktop, which is a bad place for Windows dev tooling and can cause extra filesystem permission and linking problems.
What blprnt did:
- Identified OneDrive as a likely source of additional friction
- Recommended moving the repo to a plain local path
- Helped sequence the move correctly after the running process was stopped
Solution applied:
Moved repo from:
C:\Users\maxch\OneDrive\Desktop\blprnt projects\blprnt marketing\paperclip-0.3.1
to:
C:\paperclip\paperclip-0.3.1
10. Post-move dependency issue
After moving the repo, the dependency install in the new path was stale/broken.
Error:
Cannot find module ...\server\node_modules\tsx\dist\cli.mjs
What blprnt did:
- Diagnosed the missing module as a moved-install problem
- Identified the fix immediately instead of chasing a fake code bug
Solution applied:
cd "C:\paperclip\paperclip-0.3.1"
pnpm install
11. Current issue
Paperclip now gets much farther, but fails when trying to create a Windows directory symlink for Claude skills.
Error:
EPERM: operation not permitted, symlink
'C:\paperclip\paperclip-0.3.1\skills\create-agent-adapter'
->
'C:\Users\...\AppData\Local\Temp\paperclip-skills-...\ .claude\skills\create-agent-adapter'
What blprnt did:
- Traced the exact code path creating the symlink
- Identified the failing adapter logic
- Confirmed this is a Windows symlink permission problem, not a Paperclip database problem
- Confirmed Paperclip is using directory symlinks where Windows often wants Developer Mode, elevation, or junctions
Root cause:
- Windows is blocking `fs.symlink()` for Paperclip’s skill directory linking
12. Current solution to apply
Enable Windows Developer Mode, then rerun Paperclip.
Launch command:
cd "C:\paperclip\paperclip-0.3.1"
$env:DATABASE_URL="postgres://paperclip:[email protected]:5432/paperclip"
pnpm dev:once
13. If Developer Mode does not fix it
What blprnt already determined:
- The correct code-level fix is to patch Paperclip so Windows uses junctions instead of symlinks for skills
Next fallback options:
- Run Paperclip from an Administrator terminal
- Or patch the repo to use Windows junctions for skill links
Summary of what blprnt saved you from doing manually
- Mapped the codebase and found the real startup architecture
- Diagnosed the embedded Postgres failure path
- Reproduced and ruled out false causes
- Installed and validated external PostgreSQL
- Helped set up the Paperclip DB/user path
- Diagnosed crash-recovery behavior in PostgreSQL
- Verified the exact launch configuration Paperclip needed
- Identified OneDrive as a bad repo location and helped move it
- Diagnosed the moved dependency failure
- Traced the current EPERM symlink issue to the exact adapter code and Windows behavior
Net result
- Paperclip is no longer blocked by embedded Postgres
- The remaining blocker is now isolated to one specific Windows symlink issue in skill injection
- That is a much smaller, cleaner problem than the mess we started with
We just open-sourced Paperclip: the orchestration layer for zero-human companies
It's everything you need to run an autonomous business: org charts, goal alignment, task ownership, budgets, agent templates
Just run `npx paperclipai onboard`
https://t.co/wuDdEmrSMx
More 👇
blprnt just built and shipped uncle-funkle (UN-FUK for short)
It scans your repo for slop (AI BS): TODO graveyards, debug junk, spaghetti functions, nesting crimes,
Built for humans and agents.
#opensource#aislop#devtools#videcoding
blprnt just built and shipped uncle-funkle (UN-FUK for short)
It scans your repo for slop (AI BS): TODO graveyards, debug junk, spaghetti functions, nesting crimes,
Built for humans and agents.
#opensource#aislop#devtools#videcoding
blprnt just built and shipped uncle-funkle (UN-FUK for short)
It scans your repo for slop (AI BS): TODO graveyards, debug junk, spaghetti functions, nesting crimes,
Built for humans and agents.
#opensource#aislop#devtools#videcoding
I've come to the decision to open source @blprntai
I believe in this project. I want it to succeed. I can't do it completely alone and in the dark.
I'm spending the day getting rid of all the "pay us" shit from the repo. And reliance on our servers is getting ripped out.
Now, everyone can see my shit code 😅
sessions alone will be throw aways
agent/employees run off memories. they learn. they get better with every task
context size become irrelevant since every session itself is a one time use throwaway.
what matters is persistent forever memories / skills and things each “employee / team member / agent” wtvr you wanna call it has and can use any time for any purpose needed
the project builds under this new paradigm
your workers evolve as the project is executed
the concept works on any size task from building a simple app to running a full company with 100’s of workers
New feature idea.
Subagents are old news. Skills are old news. And mcp is dead now?
@blprntai already has persistent memory. But it's scoped to the project.
What if we scope it to an individual. Like, Jerry the Sr React Dec or Brian from marketing.
Employees, not agents.
ppl are strangely attached to their ai tools
they’ll be juggling 16 different tools… get nothing actually shipped and still swear by them
beautiful case study in toxic relationships
blprnt just built and shipped uncle-funkle (UN-FUK for short)
It scans your repo for slop (AI BS): TODO graveyards, debug junk, spaghetti functions, nesting crimes,
Built for humans and agents.
#opensource#aislop#devtools#videcoding
blprnt just built and shipped uncle-funkle (UN-FUK for short)
It scans your repo for slop (AI BS): TODO graveyards, debug junk, spaghetti functions, nesting crimes,
Built for humans and agents.
#opensource#aislop#devtools#videcoding
@balintorosz ppl are finally starting to realize this. this is exact use case for blprnt. orchestration layer above ai that helps you actually deliver things that work