demo of making the #headway issue tracking notedeck app ai-friendly

the companion headway-cli tool talks to the embedded notedeck relay to interact with the UI, but also can work as a local issue tracker if notedeck is not open

extracting #headway business logic into a standalone crate. this will allow agents to interact with nostr-based issue tracking without depending on #notedeck.

agents can use the cli to connect to the notedeck relay and interact with the board ui in realtime.

if not using the notedeck relay it can just exist locally in a standalone nostrdb instance or connect to a remote relay for storage.

this opens up the possibility of creating TUI issue tracking tools that exist independently of notedeck/relays but also can sync with them

this is super decentralized way to use nostr, utilizing relays for backup but not requiring them.

local first ftw.

another cool usecase for the #notedeck websocket relay: since notedeck/nostrdb unwraps giftwraps automatically, you can use the notedeck relay to subscribe to giftwrapped events like DMs.

this is a handy way to access your nostr DMs in cli scripts while notedeck is running

slowly getting there

another idea: notedeck apps can register skills, then the embedded dave ai can know how to interact with any notedeck app by default.

for example: when dave is building apps, it can see that notedeck_headway issue tracking is available, and automatically use that for tracking project issues.

its like an ai-native, offline-first nostr browser 🤔

huge opportunity to reinvent how apps are built

the #notedeck browser's embedded relay can now be accessed via websockets. this allows you to dynamically interact with any notedeck app (insert/query notes) without needing any internet connection or external relay.

going to use this to build clis for ai agents to interact with any notedeck app without needing external relays.