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 ๐
Probably a good idea to put $20 in crypto private keys with your secrets as canaries
If your secrets are compromised almost any hacking agent will steal the funds immediately
In this context, canaries are low-value trap assets mixed into your real secrets. You plant crypto private keys holding about $20 alongside sensitive data. Any thief who steals the secrets will almost always drain those funds right away, giving you an instant alert that a breach occurredโjust like a canary in a coal mine.
196 BILLION TOKENS across 50,000+ @papercliping issues.
Can't wait to unleash what we are building on the world!
Thank you @dotta for transforming the way we build product ๐
the codex docs on /goal are also helpful for improving your prompting in general:
* define your desired end state
* verified by specific evidence
* preserving constraints
* use these inputs, tools, and boundaries
* after each iteration, here's how to choose the next best action
* when you're blocked here's how to report it
it's simple in concept, but requires discipline to actually answer what you want in each of the 6 areas
---
here's the template from the codex docs:
/goal <desired end state> verified by <specific evidence> while preserving <constraints>. Use <allowed inputs, tools, or boundaries>. Between iterations, <how Codex should choose the next best action>. If blocked or no valid paths remain, <what Codex should report and what would unlock progress>.
looking at pstack by @poteto and it's a goldmine of prompt engineering
even her example prompt is the best template i've seen of the four things you need to give your agent in a single prompt:
* a goal
* a checkable finish condition
* the evidence you want to see
* constraints
I'm always surprised by how short pro's prompts are. It's less about length, but ensuring your hitting those four points.
Here's the prompt:
/poteto-mode fix the duplicate notification after retry.
Reproduce it first. Done means retrying produces exactly one notification and normal delivery still works.
Show the failing and passing evidence. Leave a PR for review.
So simple
define what you want, how to know when you're done, what you want to see, and what you shouldn't do
I guarantee you this isn't obvious to most prompters
here's the sauce https://t.co/lZjP8Ajset
Really like @papercliping but needed a really nice way to understand which agents need me. Plus it's a really nice totally different view to see your teams working, as if in a virtual office ๐ @dotta