Member Session Agent

[Mookse]

Need to proxy as [active] human, one per session (inactive would be separate, that would be animating

• 'login' via .env
• session core creation
  • watch scoping in ctx.session
  • sub-agent references via routes
• build out /board routes, each of them leading to the MyLife Agent of 'them' instead of Maht...?
  • I think that makes sense...
• response commands using 'Maht' and proxy (perhaps put var in called local command bot? i.e., mine would be Maht?)
• how to handle such nested routes? Emit routes to parent? koa must have, need to set all sub-routes to ${sysName}

[Mookse]

• 'login' via .env
  • MYLIFE_SERVER_MBR_ID [server.js agent]
  • MYLIFE_MEMBER_MBR_ID [session agent]
  • not yet multi-sessionable

[Mookse]

where do I put routes for member? I think it is okay that it is in /member, so long as they have dynamic route prefixes - about to try that

[Mookse]

routing management should be its own ticket, for now, I am hard-coding with prefixes etc - in order to use variables, which are stored in ctx.params, it requires a colon after pathL /:bid