Replies (11)

Niel Liesmons's avatar
Niel Liesmons 1 year ago
Me gusta! PS: We're building your Tasks spec right into Zapchat, so your example would just open the List up so you can tap the :Check: instead 😉
1 replies ↓
hodlbod's avatar
hodlbod hodlbod@coracle.social 1 year ago
This is fantastic, it works great so far (a little extra setup was required, I added the env variables to my goose config, and I think having the `nak` mcp extension confused it some, it sent some kind 1s randomly to the network at first).
ynniv's avatar
ynniv ynniv@ynniv.com 1 year ago
Oooo... how's the MCP work? Generally goose does the driving, so responding to events is an interesting mechanism
Niel Liesmons's avatar
Niel Liesmons 1 year ago
First use case is the one we need ourselves: Community Issue tracking Think Linear, Click Up, etc... but within a #communikey. With the repos, wikis, chat, ... related to the community project all in there. I like the general nature of your spec so much, I now have this question:
Niel Liesmons's avatar Niel Liesmons
If you have Tasks: - like this in your Communities / Team groups - that can tag Repos Do you even need Issues? image View quoted note →
View quoted note →
↑