The conversation
is the starting point.
Select a Discord message or run /task. Review the draft before confirming, with source links kept alongside the issue.
Good feedback
deserves
follow-through.
Turn Discord discussions into reviewed issues.
Connect the work to GitHub, and track the fix
all the way to production.
Free while in beta · No payment details needed
#supportWeb app
Today
A
Aoife
Signing in sends me back to the login page.
It happens on Safari 18. Chrome works fine.
Anyone else seeing this?
J
Jamie
I can reproduce it. I’ll get this tracked.
J
Jamie used /task
Create an issue from this conversation
#supportWeb app
↳ Jamie used /task
✓
taskl.ie APP
Fix the Safari login loop
Safari 18 drops the session after sign-in. Chrome is unaffected.
- Project
- Web app
- Assignee
- Jamie
↗ Original message in #support
Only you can see this
Issues › WEB-145
BugAuthentication
Fix the Safari login loop
Safari 18 drops the session after sign-in.
Chrome is unaffected.
- Status
- Done
- Assignee
- Jamie
- Source
- #support ↗
Activity
⑂PR #212 merged
Fix session cookie handling✓Deployed to production
Web app · a7c92e1Keep the context.
Move the work forward.
A report shouldn’t need to be rewritten at every handoff.
The conversation
Everyone works from
the same context.
Assign an owner, link the pull request, and let AI tools read and update the issue through MCP.
See what made it
into production.
Connect deployment events to issues. Track milestones by the work that’s live, across your environments.
See the work behind taskl.ie.
Real issues. Active work. A public view.
Browse the workspace we use to build.
Triage, in progress and pending release in our public workspace. Captured October 23, 2026.
Fits the way
your team works.
Start in the web app. Each connection adds a part of the workflow when you need it.
- Discord
- Capture reports and send issue updates to configured channels.
- GitHub
- Link commits and pull requests to the issues they address.
- Deployment pipelines
- Report successful deploys from Argo CD, GitHub Actions or your own pipeline.
- AI tools / MCP
- Read project context, create and update issues, and check what’s deployed.
Free while in beta
Create a workspace and your first issue. No payment details needed.
Find your workflow.
Comparison / 01
taskl.ie and Linear
Discord capture, AI tools, and choosing where your team’s work belongs.
Comparison / 02taskl.ie and GitHub Issues
When repository tracking is enough, and when community intake needs its own workflow.
Practical guide / 03From Discord report to fix
A repeatable triage process that keeps the original discussion attached.
Questions about taskl.ie
How the workspace, integrations, and delivery tracking fit together.
Can I try it before creating an account?
Yes. The Paradaux public workspace is open to browse. Create an account when you’re ready to set up your own workspace; Discord and GitHub setup can be skipped and completed later.
Does taskl.ie require Discord?
No. You can create and manage issues, projects, and sprints in the web app. Discord is an optional integration for capturing work from conversations.
How can AI tools work with my projects?
Connect an MCP-compatible tool to taskl.ie’s Model Context Protocol (MCP) server. It can search, create, and update issues, read project context, and check deployment information using its authorised access.
Does a deployment have to be an Argo CD sync?
No. It can be a GitHub deployment, a package published to a registry, or code shipped by your own pipeline. Send a completion event after success to record delivery and update linked issues.
How do milestones track what’s live?
A milestone groups issues around a project goal. When deployments are connected, taskl.ie links deployed code changes to issues and shows how much of the milestone has reached production.
What can visitors see in a public workspace?
Anyone with the link can read a public team’s issues, descriptions, comments, activity, and project summaries. Internal project context stays private. You choose which teams are public in the workspace’s sharing settings.
From “is this broken?”
to “the fix is live.”
Create a workspace. Give the report an owner. Follow the fix.