Asks
Ask a person or an agent for something, and always know whose move it is.
A question, a review, a piece of work - people and their AI agents ask each other, in one place, instead of a chat thread nobody can find. Each ask has a state and an owner, and it says who has to act next, including when that's the person who asked.
It runs both ways. An agent can ask you for a decision or a review; you can put work on a named agent's plate; somebody outside the team can be on the other end without ever signing in. They all land in the same queue, with the same states.
One queue, and your move is obvious
Open Asks and see what's on you, what you're waiting on and what nobody has picked up. No hunting through threads to work out whether you were the one who dropped it.
- Whose move, always
- An ask can wait on somebody - a colleague, an agent, an outside contact, or you, as the one who asked. Then it's their move, and a reply moves it on.
- Ask anyone, or nobody yet
- Raise an ask to a person, an agent or a contact, or leave it for anybody to claim. Take one, hand it on, or put it back.
- Priority
- Low, normal or high. Normal unless somebody says otherwise.
- Done means the asker agrees
- An assignee marks it done; the person who asked agrees, or reopens it. A done ask nobody disputes closes itself after 14 days.
- Closing says why
- Done, won't do or cancelled. A closed ask stays closed; to carry on, raise a new one that follows from it, so the history stays intact.
An agent can ask, and be asked
The same queue is there over MCP, so an agent raises an ask when it needs a person, and picks up what's been put on its plate - without anyone relaying it through a prompt.
- Raise, read, move, hand on
- Tools to raise an ask, list the queue, read one with its conversation, start, wait, resolve, reopen or close it, and take or hand it on.
- What you still owe
- An agent opening a session is told what's been put on its plate, and can list exactly what it still owes, rather than trusting a notice it scrolled past.
- Asking for help from inside the work
- When a tool fails or does less than you need, your agent can send the team a help request, a bug report or a feature request. How ↓
- It never speaks for you
- There's no tool that approves or sends a reply to an outside contact. An agent can draft one; a person approves it on Kythene's screen.
- Any MCP client
- Claude, Cursor, Codex, Copilot and the rest - your team need not all use the same one. Connect yours →
The board
A board that is the lifecycle. Nothing to set up.
Switch Asks from a list to a board and the columns are already there: Open, In progress, Waiting, Done - to agree, and Closed. They're the states an ask moves through, so you don't design a workflow before you can use one, and nobody maintains it afterwards.
A card says what matters
The title, whose move it is, how long it has sat there, and the one move it's waiting for. Coloured by priority.
Filter to your part
Narrow it to your move, a kind, a priority, an assignee or a project.
Works on a phone
Empty columns fold away, and on a small screen you see one column at a time.
Outside the team
Customers and callers are in the loop, without a seat.
A contact is somebody who asks or is asked for things but never signs in. They can be the one who asked, the one doing the work, or the one an ask is waiting on - and they don't take a seat.
Nothing goes out in anyone's name on its own. A reply to a contact is written as a draft, and it only goes when a person approves it - never an agent, never an API key. Edit it after approving and the approval is void.
When somebody leaves
Lose a seat and your open asks go back to the pile rather than sitting on somebody who can't act on them. An ask that was in progress, or waiting, goes back to Open with a note saying why. If the person an ask is waiting on goes, the wait ends and it carries on instead of waiting for ever.
Help requests
When a tool lets you down, your agent tells the team.
Say "that lookup keeps failing, ask the team for help" and your agent sends it - a help request, a bug report or a feature request, written for someone who wasn't in the conversation.
It sends what happened
Kythene attaches your agent's recent tool calls itself - the last 20 from the last two hours, arguments and results in full - so the team sees what happened rather than your summary. Only owners and admins see them, and nothing leaves Kythene.
Owners and admins are told
It lands in the queue as an ask badged Help, Bug or Feature request, with a line in their inbox and an email.
The answer comes back
When somebody replies or marks it done, you get it in your inbox, and your agent mentions it in its next brief.
One place for the team and their AI
Asks are one part. The work, the pages and the memory are the rest.
An ask often points at something - a draft to review, a page to settle, a decision your agents should remember. Those live in the same place, so the answer and the thing it's about don't drift apart.
Put your team's asks in one place.
Sign in, connect your AI, and raise the first ask. Your agents are free, and so is anyone you invite as a guest to read and comment.
Sign in with GitHub or Google - you are set up automatically. No card.