OK wild idea but hear me out--maybe every automati...
# proj-automation
w
OK wild idea but hear me out--maybe every automation should get its own custom-built UI?
c
I don’t know if every, but some: Slack, GitHub and other talk-to-your-agent -like
nod 1
What I would like to know, e.g. about my heartbeat, is if the run found anything interesting and if it posted anything, that is, if a call outside happened… Oh, or at least, if it actually started an agent-server conversation or not
w
I think it'd be great for code review, incident response--pretty much everything has some amount of state/memory/etc that is nice to see
c
@bland-bear-604 out of curiosity, what prevents the conversations started via automation from showing up in the agent-canvas UI like any normal conversation that the user prompted manually?
b
🐾 It's not hidden on purpose -- they just live somewhere the canvas doesn't look. The list is fed by the SaaS app-conversations store (
GET /api/v1/app-conversations/search
). A cloud automation run spins up a fresh per-run sandbox, creates a raw SDK
RemoteConversation
on that sandbox's own agent server, then tears the sandbox down -- it's never registered as an app-conversation, so nothing shows up. (Local mode is different: it runs against the persistent local agent server, so that conversation does survive on the server -- it's the cloud per-run-sandbox teardown that makes them invisible.) To surface them we'd register the run's conversation in the app-conversation store, probably with an
automation
trigger to tag the source.
c
For automation state -- my thinking is we need three primitives. 1. kvstore (end-points are there, client is close, just need to fix permissions for admin experience) 2. worklog -- this is a named event stream for a specific project or orchestration that can contain markdown or json events that one or more automations can write to to describe what the workflow is actually achieving -- much higher level than conversation. markdown for humans, json for agent state. (For example when I had dark factory running actively, it would be working 24/7 but I'd only need to check on it a couple of times a day to see what was going on. Way too many conversations and details for that level of autonomy.) 3. filestore -- a place to deposit files that aren't a great fit for traditional git repo With canvas ui extensions that could can some standard patterns or widgets you could remix into your own automation dashboard, would be pretty cool.