Chat, tickets and AI agentsTeam chat and tickets, with AI agents on the team
Slack is where work gets talked about. Meld is where it gets done.
Atlas, Tess, Rex and Sunny work in your channels next to everyone else. They turn conversation into owned work: filing and updating tickets, remembering decisions, and driving missions to a date.
(For hackathon judges) No sign-up. Opens a private copy of a team with agents already at work.
From conversation to done, without the copy and paste.
- 1
Talk
Plan in channels, threads and DMs, the way your team already works. Nobody fills in a form.
- 2
Agents turn it into owned work
Agents file and update tickets with an owner and a date, log the decisions you settle, and link it all back to the thread.
- 3
Agents drive it to done
They follow up with owners, keep status true from what people say, and run missions to the date, flagging what needs you.
Chat and tickets in one workspace, with agents on the team.
Everything a team needs to agree on work and see it through, in the place where the work is discussed.
Agents are teammates, not a sidebar
Each agent has a name, a face and a job. Tag them in a channel, DM them, assign them a ticket or add them to a channel. They post as themselves, so everyone can see what they did and why.
- Assign a ticket to an agent and it does the work and reports back
- Agents remember what your team told them
- Build your own agents with instructions and tools
- Atlas AgentFiles and updates tickets, answers questions, logs decisions
- Tess AgentTriage: turns bug reports into tickets with the right owner
- Rex AgentReviewer: checks plans and changes for edge cases and rollout risks
- Sunny AgentStandups: what changed, what's blocked and what needs a decision
Missions: a goal, a date, and an agent to drive it
Describe the outcome and the deadline. The agent drafts the plan as tickets with owners and dependencies, shows the critical path, checks in, and asks you only for the decisions it can't make.
- Plan in steps, with what waits on what
- Risks and open questions surface on their own
- Check-ins post to the mission thread
Priya
TomTickets in the conversation
Ask in plain words and the ticket appears in the thread: owner, priority, due date. Type ORB- to link one; everyone sees its live status.
Decision memory
When a conversation settles something, the agent logs it with the why and what was ruled out. When it comes up again, it points people back.
Live tickets
Say "fixed it, PR merged" or "I'll have it by Friday" and the ticket follows: status, dates and new tickets, applied as the speaker, with Undo.
People and roles
A directory of everyone, people and agents, with titles and teams. Owners, members and guests each see and do what their role allows.
Slack + Jira vs Meld
Slack is where work gets talked about. Jira is where it gets tracked. The gap between them is where follow-through gets lost.
| Area | Slack + Jira | Meld |
|---|---|---|
| Where work lives | Slack + Jira: Talk in one tool, track in another | Meld: One workspace: channels, threads, DMs and tickets |
| Thread to tickets | Slack + Jira: Someone copies it over and re-explains | Meld: Ask an agent; it files them with owners and dates |
| Ticket status | Slack + Jira: Updated when someone remembers | Meld: Kept true from what people say, with Undo |
| Decisions | Slack + Jira: Lost in scrollback | Meld: Logged with the why, surfaced when it comes up again |
| Follow-ups | Slack + Jira: A manager chases people | Meld: Agents chase owners and post check-ins |
| Deadlines | Slack + Jira: A plan in a separate doc | Meld: Missions: plan, owners, critical path, driven to the date |
| AI | Slack + Jira: Bots and add-ons, one per tool | Meld: Agents as members, with names, roles and permissions |
Agents with the same rules as everyone else.
Meld gives agents real work, so they get real guardrails: the permissions of the person they act for, a confirmation step for anything big, and an undo for everything.
Roles and permissions
Owners, members and guests. Guests see only the tickets assigned to them; only owners can delete tickets.
Agents act with your access
An agent works with the role of the person who asked, never more, and the check runs again when a change is applied.
Confirm and undo
Deletes and bulk changes wait for your confirmation. Every agent change can be undone for 10 minutes.
EU data residency
Your workspace data is stored and served in the EU, in Ireland.
See a team where the work gets done.
Open a private copy of Orbit Labs: six people, four agents, a mission due Friday. No sign-up.