Introducing Dev Teams
Your team and Dev404, in one conversation. Talk the work through together, hand it to Dev404 with a mention, and follow it all the way to a pull request without leaving the chat.
What Dev Teams is
Dev Teams is messaging for the people you build with, with Dev404 in every conversation. Start a direct conversation with a teammate, or a group for a team, a project or a workstream. Messages arrive live, with replies, reactions, photos and files, read receipts and typing.
Teammates find each other by their Dev404 username. Everyone you add to a group gets an invitation, and nobody joins until they accept it.
Bring Dev404 in with @Dev
Mention @Dev in any conversation and Dev404 reads the thread before it replies. If you asked a question, it answers in the conversation. If you asked for work, it starts a task.
A task shows up as a card that everyone in the conversation can follow. The card updates as Dev404 works: what it’s doing now, then what came of it, with the files it changed, the checks that passed and a link to the pull request. If Dev404 needs something from you, it asks in the conversation, and replying there lets it carry on.
The person who asked, or the group’s owner or admins, can stop a task at any time. The work done so far stays on its branch.
Repositories, shared carefully
A group’s owner and admins choose which repositories Dev404 can work in, and it works only in those. Each repository is reached through the access of the member who added it. Nobody else in the group receives that access, and joining a group never gives anyone access to your GitHub or GitLab.
Tasks run in the group’s own workspace, which its owner can open in full.
Who pays for the work
Each group decides how it pays for Dev404:
- Whoever asks pays. The default. Each request comes out of the credits of the person who made it.
- Shared usage. The cost of each task is split equally between the members who were in the group when it started. Everyone accepts the arrangement before it applies to them, and nobody is charged for work that began before they joined or after they left.
Either way, you stay in control of your own spending. Every member sets a monthly limit for each group, the most it can take from their credits in a month. Every task has a budget too. When a task reaches it, Dev404 pauses until someone approves more.
The group is yours to run
The owner chooses the model Dev404 runs on in the group, the budget per task, and whether usage is shared. Admins invite and remove members and manage the repositories. Everyone controls their own notifications: every message, mentions only, or nothing.