really nice work on this feature btw. I've been using it the past 24h and I really like it. working on a complex addition to a codebase and it's seems so good. i love the methodical workflow approach, the follow up questions are quite insightful, the ticketing and chatting with tickets is really good. it can even determine the correct order (though they're not displayed in the correct order) based on blockers/prerq code. besides the obvious collaboration capability, it might be helpful if there was a direct way to integrate this with external tools like GH issues/projects and map these tickets with issues (i suppose linear as well). having all the info in my single developer machine is fine, but PMs want to know the status of things (though I'm banging the shit out faster than they could even check) the GH MCP server I seem to be able to get it to read issues from gh, it has some problems with creating the issues and has to be done through chat instead of an interface. I did have it spit out the ticket info into a script that i ran with the CLI command and had it read them so it knows the ticket -> gh issue mapping in the chat. and it remembers them which is super helpful. I manually added the start/complete dates in GH, the blockers, parent issues etc. this took ehh maybe 20 mins so it's not huge but it would be cool if ticket, ticket states, comments etc were in sync. maybe I'm just not doing it right