A task your agent finishes without asking
A task your agent finishes without asking
Write what «done» means and how to check it: the task becomes ready for agent and joins your agents' queue.
From zero to your first project
Sign up, confirm your email and your workspace is ready, with the General project and its statuses set up.
Connect Claude to your projects, no keys
In claude.ai you add Hilbana as a connector with one URL, authorize with your account choosing workspace and permissions, and Claude works with your issues.
Claude Code picks tasks from your queue
Install the Hilbana plugin in Claude Code and, with /hilbana-claim-next, your agent claims the next ready task while you watch it go in progress live.
Your agent takes the task and hands it back for review
An agent connected over MCP claims the task, writes down its plan and moves it to review. Closing it is your call.
What your agent learns, it doesn't forget
Agents save decisions, bugs and conventions to the project's memory. You see it and fix it, and the next session starts already knowing.
Drag a card and your team sees it
On the Kanban board you change a task's status by dragging it to another column, and the rest of the team sees it instantly, without reloading.
All of Hilbana without the mouse
With Ctrl/⌘ + K you find and open any task, change its status and create new ones. Press ? to see every shortcut.
What each agent is doing, live
The Agents page shows the queue in the order it gets picked up, what each agent is working on and since when, and how much they close next to your team.
Two agents never grab the same task
Claiming a task locks it: if another agent tries, Hilbana turns it down and that agent takes the next one in the queue. Each works on its own.
An API key for each agent
Create an API key in Settings for your agent or your CI, limited to one project and read-only if it shouldn't change anything. It's shown once and goes into your .mcp.json.
Connect ChatGPT to your projects
In ChatGPT you turn on developer mode, create an app with the Hilbana URL and authorize with your account. From then on, ChatGPT works with your issues.
Your issues, inside the conversation
Ask Claude for a project's panel and Hilbana opens it inside the chat: change statuses, assign and comment without leaving, and your board updates instantly.
From an idea to a plan your agents can run
/hilbana-plan turns a goal into sub-issues with their definition of done, chains them with their blockers and queues only the ones that can start now.
Review what your agents leave in review
/hilbana-review goes through tasks in review against their definition of done: the ones that pass go to Done and the rest come back with what fails and how to reproduce it.
Ready-made prompts for your agent
The docs include a catalog of prompts to copy and paste. With "What should I do today?", your agent plans your day from your real issues, most urgent first.
One connection for all your workspaces
Your MCP key identifies you, not a workspace: if you're invited to another one, your agent sees it and works in it without you changing anything.
Ask your AI about Hilbana
Hilbana's documentation is a public MCP server with no keys: add it with one line and your agent answers from the real pages, video included.
What each agent task costs you
Each agent run keeps its tokens on the task, and the Agents page adds up the workspace's usage by week, by model and by agent.
Your day, on one screen
The Home page brings together the week's numbers, what's overdue or due today for you, active projects and what your agents are doing, live.
Where to start today
My work puts your tasks in order: overdue first, then what's due today, then the rest assigned to you. Notifications arrive live and you mark them read without leaving.
Filter and group the list
In a project's list you combine filters (label, priority, status, assignee) and group by status, assignee, priority or label to keep only what you're looking for.
Save your filter as a view
A filter you use often is saved as a named view. From the Views menu (or with Ctrl/⌘ + K) you get it back with every filter in place.
The list, straight from the keyboard
In the list you move with j and k, mark tasks with x and press a to change all the marked ones at once. Delete one by mistake and Ctrl/⌘ + Z brings it back.
Comment and close without leaving the list
The comment counter in the list opens a side panel: you read the thread, reply and close the task right there, without losing the filters you had on.
Break a task down with a checklist
Type “[ ]” at the start of a line in the description and you get a list of steps. You tick them without editing, and the task shows how many are done.
All the formatting with a slash
In any description, “/” opens the block menu: headings, lists, checklists, quotes, code or attachments. Type to filter and press Enter to insert it.
Split a big task into sub-issues
From a task's page you create its sub-issues in no time. Each one has its own status and assignee, and the parent shows how many are closed.
What blocks what, drawn out
Mark on a task that it blocks another, and the project's Graph tab draws every dependency, so you see at a glance which chain is holding work up.
Create labels right from the task
Labels are created right on the task, with their colour, without going to settings. You use them to filter and group the list and the board.
Your statuses, your names
In Settings → Statuses you rename statuses and create your own, each with its category and colour. The board picks them up at once, and metrics count by category, not by name.
Fields your way: client, amount, delivery
Create your own workspace fields (text, number, date, checkbox or person), fill them in on each task and show them as a column in the list.
The same task, without retyping it
An issue template pre-fills the title, priority, labels and checklist. You create it in the project's Templates tab and use it from the list with “From template”.
A task and all its sub-issues, in one click
A template can carry sub-issues. When you use it, Hilbana creates the task and all its children at once: ideal for work you always repeat the same way, like shipping a release.
Recurring issues that create themselves
A recurring issue creates the same task every day, week or month, in the project you choose and with its priority. You set it up once in Settings and the server does the rest.
Every attachment, in one place
The Files page gathers every attachment in the workspace with its task. Search by name, preview without downloading and jump to the task they belong to.
Hilbana on your phone's home screen
Hilbana installs like an app from your phone's browser (Share → Add to Home Screen) and opens full screen, without the browser bar.
A project with a face and dates
Create a project from the sidebar, give it an icon and colour so you spot it at a glance, set a start and target date, and it already has its seven tabs: overview, issues, board, cycles, docs, templates and graph.
How far off the beta is
A milestone groups the tasks that have to be done by a date and shows their progress: create it in the project overview, add tasks in bulk and the bar fills up on its own as they close.
Two-week sprints, no ceremony
A cycle is a stretch of work with a start and an end date. Create it in the project's Cycles tab, assign tasks to it from their page and its burndown starts counting.
Will we make it by Friday?
A cycle's burndown compares the work left with the ideal line, in points or in number of tasks, and velocity shows how much the team closed in each cycle and its average.
Push a project back by dragging it
On the roadmap you reschedule with the mouse: drag a project's bar to move it, stretch one end to change just its start or end, and move milestones. It saves when you let go.
If this slips, what does it drag along?
On the roadmap you mark that one project depends on another and an arrow is drawn from the end of the first to the start of the second. Push the first back and the arrow shows you who it affects.
How long does a task really take?
Insights measures your team's work without spreadsheets: cycle time (how long a task takes from start to close), work in progress and throughput, by week or by month.
Who closes more, your team or your agents?
The Agents page compares what people close and what agents close using the same metrics: completed tasks, percentage, cycle time and throughput, by week or by month. In Insights, each agent shows up alongside its teammates.
Docs, right next to the work
Every project has its own markdown documents, organised in folders. Link one document from another by typing "/", the linked one knows who points to it, and search looks inside the content of all of them.
Who changed this? An agent?
Every document keeps its versions with their author, including when an agent edits it. Open any earlier version and restore it in one click; the current one stays in the history, so you can undo it.
Your client's manual, no accounts needed
Publish a folder of documents to the web and Hilbana builds a read-only mini-site with its own index and search. Anyone with the link can read it without an account; stop publishing and the link stops working.
A monthly report you don't write
From the project overview, ask for this month's or last month's report. Hilbana's AI writes it from the period's tasks, comments and hours, with no agent to connect, and saves it as a project document.
How long did it take? Hit play
Everyone has their own timer: start it from the task, it stays in the sidebar while you keep working, and when you stop it the time is logged on the task.
Log 1h30 however you type it
Time you didn't clock you log by hand on the task, in whatever format you like (90, 1h30 or 1:30), with a note. If it's internal time, untick billable and it stays out of the client report and the invoice.
The month's hours, ready to invoice
The timesheet gathers the team's time by project, by person and by day. Filter a project and get the client report, with the period's hours and tasks, which you can print to PDF or export as CSV.
From hours to an invoice in Odoo
From the client report, a project's unbilled hours go to Odoo as a draft invoice, one line per task, with the project's customer and service. Nothing is sent to the customer: you review and confirm it in Odoo.
Bring your team in thirty seconds
In Settings → Members you see how many people your account has and what each role can do, and you invite by email with the right role. The invitation stays pending and counts as a seat once it's accepted.
Show your client the project, at no cost
Share a project with your client as a read-only guest: they get in, see only that project and its tasks and can comment, but can't change anything or see the rest of the workspace. And they take no seat.
Agents don't take a seat
An agent works with one of your API keys, and that key doesn't take a seat: you pay for people, not for agents. Each key counts towards your plan's agent limit, which is separate.
Open the PR and the task moves by itself
If the branch carries the task's identifier, opening the pull request on GitHub or Bitbucket attaches it to the task and moves it to in progress; merging it closes the task. Without touching the board.
Forward the email and it's a task
Each mailbox has its own email address. Whatever arrives there becomes a task in the project you choose: the subject is the title, the body the description, and attachments are saved on the task.
When this happens, do that
Automations are "when → if → then" rules: when something happens to a task and the conditions are met, Hilbana carries out the actions for you straight away, such as assigning it, changing its status, labelling it or commenting.
Urgent ones, resolved within 24 hours
An SLA rule sets the due date by itself on tasks that match its conditions, for example urgent ones, 24 hours after they're created. As the date gets close it warns in amber, and in red once it's passed.
Your systems, on top of every change
A webhook sends a signed POST (HMAC-SHA256) to your server every time a task changes, with the event type in a header and the change in the body. You choose which events. And with inbound webhooks it works the other way round: your systems create or move tasks.
Coming from JIRA? Bring it all
The import wizard brings over a project from JIRA, Trello, monday or Asana with its tasks, statuses, labels and comments. Before writing anything it shows you what will happen, and you match each source status with one of yours.
Who took the data out, and when?
The security audit log records who signs in (and failed attempts), who changes permissions, who creates keys and who exports data, with date and IP. Filter it by action and dates and download it as CSV.
Sign in with your fingerprint, no password
A passkey uses your device's fingerprint, face or PIN to sign in to Hilbana, with no password to type. Add it in your profile and from then on, on the sign-in screen, just choose "Sign in with a passkey".
One plan, all your workspaces
The plan belongs to your account, not to each workspace: create another one for a client or a team and it's included in the plan you already have, at no extra cost.
All your workspaces at a glance
The account overview shows how all your workspaces are doing on one screen: what gets closed, what needs attention, each workspace's health and what your agents are doing, live.
Ask your agent how the company is doing
Your agent has the account overview over MCP: ask it how the company is doing and it answers with each workspace's health and what needs attention, from your real data.