Build the product, not the process.
Bugs and requests, specs, release notes and what customers say, in one place, with coding agents picking up work beside your team.
Request access
Bugs and requests,
filed right
Every bug and feature request lands under its product, with where it happens, how urgent it is and who owns it. Similar tasks show up while you type, so duplicates don't.
Bugs and features
Every task is a bug or a feature request, filed under the product it belongs to.
Surface and environment
Say where it happens, web or app, and for bugs whether it's in production, staging or local.
Similar tasks
While a new task's title takes shape, up to three existing tasks that may cover it appear.
Pull requests
Link a task to its GitHub pull request and see where the change has got to.
Coding agents
in the loop
Agents read a task, do the work and hand it back as ready to test, through Olamma's MCP address. Your team sees every change with the agent's name on it.
Claude Code, Codex, Cursor
Any MCP client that can send headers connects with its own agent key.
To test, not done
Agents mark work they haven't verified as ready to test, so a person confirms the fix.
Roles, like people
An agent reaches only the projects its role opens.
Every write signed
Each change records the agent that made it.
Specs and runbooks
people find
Write specs, runbooks and meeting notes in pages filed by product, discuss them line by line, and post what you learned as write-ups your team and customers can follow.
Filed by product
Every page belongs to a product or project, in folders three levels deep.
Comments beside the text
Talk about a paragraph next to it, and resolve the thread when it's settled.
Versions
Look back at any earlier version, and restore it if you need to.
Word, PDF and Markdown
Bring Word and Markdown files in, and send pages out as PDF, Word or Markdown.
Release notes
customers read
Record each change with its pull request, ship it with the deploy that carries it, and publish it in your customers' words on your own changelog site.
From pull requests
One change for each pull request, so nothing ships unannounced.
Ships with the deploy
Changes whose pull requests missed the deploy wait for the next one.
Customer wording
Public lines in plain words, with a team note only your team sees.
Tell the people who asked
Email the customers and teammates who reported what shipped.
Hear from
your users
Website chat, email, WhatsApp and in-app messages in one inbox, with an AI agent answering from your help articles and the rest turned into tasks for the team.
Every channel
Website chat, email, WhatsApp and chat inside your own app.
Answers from your articles
An AI agent answers only from what you publish, and hands over when it should.
Tasks from conversations
Create a task or link an existing one, right from the conversation.
What users ask about
Questions no article answers show you what to write next.
And the rest
of the team
A help centre
Publish help articles on your own site, with search that forgives typos.
Onboarding journeys
Welcome new users with messages that follow what they do in your app.
Launch trackers
Track launches, budgets and sign-off in tables with the right field for every value.
A plan for each day
Each person plans their day from the work assigned to them.
Project access
Keep a project to the people listed on it.
Team chat, coming soon
Rooms and pings next to your work are built and being tested.
Bring your product team together
Tell us about your team and we'll help you set up your workspace.
Request access