Chaser is a task and project management app that runs inside Slack. It keeps each task linked to its original conversation, shows who owns it and when it is due, and follows up through Slack.
A request in Slack can be perfectly clear and still easy to forget. People add files, answer questions and make decisions in the thread, so it often becomes the best account of the work. Once newer messages take over the channel, the request can slip out of view along with its owner and deadline.
Copying the request into a separate tracker splits the record of the work across two places. The tracker may hold the due date while Slack holds the latest decisions, and someone has to keep both current. Chaser keeps the task with the thread and collects open work in shared views and scheduled reports, so people can get an overview without moving the discussion elsewhere.
Key Takeaways
- Chaser is a task and project management app integrated within Slack, linking tasks to their original conversations.
- It helps users track deadlines, follow-ups, and updates without splitting information across multiple trackers.
- Chaser allows creation of tasks from various tools and can work with external partners using Slack Connect.
- Recurring tasks and checklists can be easily managed, maintaining unique discussions for each instance.
- The app simplifies project oversight, keeping everything current and visible directly within Slack.
Table of contents
From Slack threads to project views
A short task title leaves out much of the discussion behind a request. The scope may shift after a file is reviewed or a question is answered. When later feedback sends the work in a new direction, the Slack thread shows how that decision was reached.
Because Chaser links the task back to that conversation, anyone returning later can review the relevant messages and understand what changed, even after days of discussion among several people.
Chaser also gathers tasks from separate threads into one overview. Its dashboard groups them by assignee or channel, and the web app offers Kanban and calendar views. Someone checking a project can see what is open and go directly to the conversation for each item.
Tags can bring related work together across different channels, while custom statuses can reflect the stages people actually use, such as waiting for feedback, in review or ready to publish. Those statuses also serve as columns on the Kanban board, and changes made there appear in Slack. The project view stays current without becoming a separate record of the work.
Files and links from a task thread remain available through the dashboard, so the context is easier to find later. People who need to keep an eye on a task can follow it without becoming an assignee. They receive an update if its status, owner or deadline changes, and when the work is completed.
Task reminders and status reports
With several requests open at once, keeping track of follow-ups takes time. Whoever assigned the work needs to remember the deadlines and send status messages, even when all they need is confirmation that the work has been picked up.
Chaser handles those routine checks. It shows whether a task has been acknowledged, posts deadline reminders in the task thread and keeps overdue work visible. If an assignment has not been acknowledged, Chaser can also nudge the assignee privately. When the scope changes or a blocker causes a delay, the conversation continues in the original thread.
When everyone in a group needs to complete the same task, Chaser tracks each person separately and stops reminding those who have finished. If the work needs only one owner, the task can be left open for someone to claim, and Chaser keeps following up until somebody takes it.
Scheduled status reports post to a channel and show what is complete, in progress, overdue or stuck. The broader reporting view lets someone filter by person, status, tag or project and see completion rates over time. Each item leads back to the relevant Slack discussion. A regular review can begin with the work that needs attention instead of somebody compiling status notes first.
Recurring tasks and checklists
Recurring work often follows the same outline while varying in the details. Chaser can save that outline as a checklist, with a separate assignee and deadline for each item. When one run needs an extra step or a different owner, the active checklist can be changed without altering the version saved for next time. Individual tasks can also repeat on a schedule.
A repeating task does not overwrite the previous one. If the earlier task is still open when the next interval arrives, it keeps its follow-ups and the new occurrence is created separately. Each cycle keeps its own discussion. Round-robin assignment can pass a recurring duty to the next person in the rotation, and someone can be skipped temporarily when they are away.
External partners in Slack Connect
Chaser also works in Slack Connect, where a client or partner can respond to and complete a task in a shared channel. They do not need their own Chaser subscription or a separate installation. Task visibility follows Slack permissions, so external participants can see the work in the shared channel without gaining access to private internal tasks.
Creating tasks from tools other than Slack
Not every request begins in Slack. Chaser’s browser extension can create a task from a web page and attach its link or a screenshot. Zapier and incoming webhooks can turn events from forms and other software into Chaser tasks, while the API gives internal tools a direct way to create and update them. In each case, the resulting task appears in Slack alongside tasks created there.
Through the Model Context Protocol, a compatible AI assistant can check overdue work, reschedule a task or assign new work using Chaser’s existing data. Any changes apply to the same tasks people see in Slack, rather than producing another list for somebody to reconcile.
Who uses Chaser
Chaser fits organizations that use Slack for day-to-day discussion and decisions. When a separate task list falls behind because the updates stay in conversation, linking each task to its thread reduces the copying needed to keep everything current.
Someone handling one request can stay in its Slack thread, while someone coordinating several projects can use the dashboard, Kanban board or calendar. A one-way Google Calendar sync places Chaser deadlines alongside the rest of a person’s schedule and keeps them current when a task changes. All of these views draw on the same tasks, so updates do not have to be copied between them.
The same approach works for quick approvals as well as longer projects that span several channels. People can update a task from Slack, so they don’t have to open another app to acknowledge it or change its status.
People still decide which requests should become tasks, who owns them and when they are due. Chaser keeps those commitments visible and handles the routine follow-up in Slack.
