vibecoded mockup of what automations onboarding mi...
# proj-agent-canvas
w
vibecoded mockup of what automations onboarding might look like https://artifacts.app.rbren.io/1476b16bde914469a00d27dd9f1cffaa/index.html
šŸ‘Œ 1
nod 2
šŸ™Œ 1
you can enter anything for API keys
l
nice! some comments: 1. we need to add links to where the API keys can be acquired 2. you'll need oauth client id and oauth client secret for things requiring oauth
c
what automations onboarding might look like
Are you thinking to include Jira or Linear? I do think GitHub, Slack are expected; various others like Discord or Whatsapp too
w
none of these (for MVP) should use OAuth--Oauth requires a backend with a host
For launch, Slack and GitHub are the targets. Jira and Linear as stretch goals
I'm hoping the community picks up other integrations like Discord, Whatsapp, etc
nod 1
I think we'll need to be very clear on what's got "first tier" support (probably Slack, GitHub, Jira, Linear, Datadog, maybe a few others), and what is "community tier" support
like, which ones are we going to QA on every release
and update when the underlying API changes
and which ones are we going to ask folks to fix themselves
c
I understand, though I don't love that TBH... I think the agent can handle API updates just fine... and test, likely šŸ¤” What if we require e2e for all maybe?
w
e2e tests that touch live APIs are really hard to manage šŸ˜•
you need test credentials, need to worry about rate limits, and your CI pipeline goes down every time one of the underlying services goes down
agreed agents should be able to do the work just fine though
c
Maybe not in CI, every week?
w
but we're currently struggling just to keep github, gitlab, and bitbucket happy
c
I totally understand that... though these seem simpler, maybe... Just for clarity, sorry, I'm just nitpicking really, it's because I'd kinda love it if we could avoid the tiny implication I'm hearing • "official" = supported by us • "community" = probably bad, cuz "community" is "not a serious" thing (tm) I... don't know if the project is in a good place to be able to write that and not see negative consequences. Sorry, maybe it's just me... probably šŸ™
w
yeah the second I typed that I was like "this was the wrong wording" šŸ˜…
ā¤ļø 1
thanks for pointing it out
c
For whatever it's worth, I have like 70+ LLM API creds in my old config.toml šŸ˜… They were like rabbits 🫠
I feel maybe it's doable - but maybe it's a question for another time!
l
i don't think slack is possible without oauth, but i might be wrong
(not first party anyway, there is second-party support)
w
Yeah I have my slack app posting as
rbren-experiments
but I think that's actually desirable for a slackbot
l
Does that use an API key or an oauth client/secret?
w
I created an app to get a "bot token"
l
Got it, cool.