Skip to content

My PAI Has FOMO #2

@emory

Description

@emory

My PAI Sundae offered to write this for me, but I didn't need to subject anyone to an impassioned plea by my voracious sidekick that, honest to g-d, kept asking for access to my ObsidianMD vaults once she knew how I used them 😂

Impressions

From what I've seen so far from casual observation and seeing how it's plumbed in earlier iterations of the PAI repo, Daemon may be a great way to control access to potentially sensitive context on-demand with clear visibility on 'custody' of the output from those endpoints? If nothing else it would be a great way for me to extend some of that context to external systems and make my use of these systems much more cohesive.

So that would solve an immediate challenge in an elegant way, based related projects and the way it seems some of us think about this sort of scaffolding.

I know you do a lot of things but if there was some guidance on what expectations should be that would help me figure out if this is something I can endure for a bit or if I dare to ask a question and end up with having software written for me. My primary use of my PAI is as assistive technology. The fact that I didn't request that and Sundae just rapidly figured out that was where I needed the most support is something I'm still thinking about.

ty for your time and attention, sorry for shissue-posting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions