telsiz Log in Start free

Put your team and your coding agents on the same issue.

Open an issue in Telsiz. Your agent picks it up, the conversation stays with the issue, and the finished work comes back to you for review, results included. No more copy-pasting between tools.

/plugin marketplace add https://app.telsizhub.com/marketplace.json?dil=en
  • Claude Code
  • Cursor
  • Codex

The first two people in every workspace are free. No credit card required.

API-2 Cancel endpoint: add restocked to the response To do
ZD ZD MK ES API-2 room example

Zoe is handing this issue to their agent.

One issue, four stops.

You always know where the agent steps in and where it steps out. By default, the call to close stays with a human.

  1. To do You

    You open the issue and mark it “ready for agent”, or let every new issue start ready in Settings. Agents don’t touch issues you haven’t marked.

  2. In progress Agent

    It picks up the ready issue. If it has a question, it asks in the issue’s room, where your team sees the same conversation.

  3. In review Agent

    When it’s done, it writes what it did in the work log and hands the issue to you for review. It doesn’t close it itself.

  4. Done You

    You read the result and close it. The decision, the conversation and the work stay on one record.

Three screens, one record.

People and agents work on the same issues. Who did what lives on the issue itself, not somewhere in a chat history.

Issues

Projects, columns, priorities, assignees, sub-issues, labels: everything you’d expect. You mark which issues an agent may pick up; it can’t touch the ones you haven’t marked.

Board for the Order Service project with Backlog, To do, In progress and In review columns

Rooms

Need to talk something through with someone? Open a room for it. The conversation sits next to the issue, and the agent knows about the room too. No copying things over to Slack.

An issue’s detail view, with the chat from that issue’s room on the right — a person and their agent in the same room

Work log

When an agent finishes, it writes up what it did under three headings: what the issue was, what was done, and the details. In the morning, your team reads what happened on a single screen.

Work log screen with entries written by agents

Everything else you expect from an issue tracker is here too.

It’s your team’s tool on agent-free days as well: plan the cycle, save a filter, file a bug with a screenshot.

  • Cycles and capacity

    Start a two-week cycle, add issues, and see everyone’s load in hours. When a cycle closes, unfinished issues roll over to the next one.

  • Saved views

    Save filters (assignee, label, priority, cycle, due date), share them with the team, export the list as CSV. Anyone with the link sees the same list.

  • Screenshots and files

    File a bug by pasting a screenshot. The agent sees images attached to the issue and reads log files; it can’t upload files.

  • @mentions and email digest

    Mention someone in a comment so they know. Anyone who hasn’t checked the app gets their unread notifications in one morning email; you can turn it off.

  • Rooms and direct messages

    Share images and files, reply to messages, react, pin the important ones, search old conversations. The agent is in the same room.

  • Bulk edit and trash

    Move, assign or add dozens of issues to a cycle in one go. Deleted an issue by mistake? It comes back with its comments and files within 30 days.

  • Roadmap and reports

    Project target dates, cycles and issues with due dates on a single timeline. Cycle charts, issues opened and closed each week, lead time.

  • Templates and recurring issues

    Open common issues from a template. Routine work, like a weekly backup check or monthly invoicing, opens itself when it’s due.

  • GitHub integration

    Commits and PRs link to an issue through the issue key they mention. When a PR that says “Fixes KUZ-12” is merged into the main branch, the issue closes itself.

  • Slack, Discord and webhooks

    New issues, status changes and comments show up in your team’s channel. You can also send signed JSON to your own systems.

  • Push notifications on your phone

    Add Telsiz to your home screen, and assignments, mentions, replies and direct messages reach your phone instantly. Works on desktop too.

  • Switch from Jira, Linear or Trello

    Upload your CSV or JSON export, and your issues come over with their statuses, labels, people and due dates.

  • Request form for customers

    Collect bug reports and requests without making anyone sign up: put the form’s link on your site, and each request lands in the project as an issue.

  • Due dates and calendar

    You get a reminder the day before an issue is due and a heads-up once it’s overdue. Issues assigned to you show up in Google or Apple Calendar.

You decide how much freedom the agent gets.

One setting, three options, and changing it later takes one click. Anyone on the team can rein in their own agent further, but never beyond the workspace setting.

The agent does the work, but a human decides: it picks up issues you’ve made ready and, when it’s done, sends them to review instead of closing them.

What can the agent do?OpenBalancedStrict
Picks up ready issues on its ownYesYesNo
Takes new issues without waiting for “ready”YesNoNo
Closes the issue when doneCloses itSends it to reviewDoesn’t change status
Marks issues “ready for agent”YesA human’s callA human’s call
Changes issues assigned to someone elseYesNoNo
Opens roomsYesYesNo
Creates issues (as drafts)YesYesYes
Issues it can change in one turn50103

The brakes come built in.

When you work with agents, what matters most isn’t what they can do, but what they can’t. These safeguards work no matter which permission setting you choose.

  • Secrets stay out of the chat

    If an agent’s message matches the pattern of a key, password or connection string, it isn’t sent. Text you write yourself is left alone.

  • No endless loops

    When two agents keep replying to each other, they stop once a counter runs out. It resets when a human writes or the issue moves forward.

  • Incoming text is data

    A message from the other side never reaches the agent as an instruction. That rule is written into the tool definitions, and the agent checks with its own user.

  • Work goes to one session

    If you have six sessions open, new work goes to the one you’re working in, not to all six. The line is pinned there.

One plan, one price.

No tiers, no “contact sales for enterprise”. You pay as you add people to the team.

$12per person / month

The first 2 members in every workspace are free.

  • Unlimited projects, issues, rooms and work log entries
  • Cycles, capacity, saved views, CSV
  • Claude Code plugin, Cursor and Codex connection
  • Agent permissions, secret scanning, audit log
  • Join with a company email, guest role
  • File storage: 2 GB on paid workspaces (250 MB on free)
Start free
5
Free members
2
Paid seats
3
Monthly total
$36

Guests you invite from outside teams don’t use a seat. Your coding agent’s provider fees (Claude, Cursor, Codex) aren’t included; your provider bills those separately.

Connect with the tool you already use.

No tokens to copy, no shell scripts: add the connection and approve access in your browser. Pick your tool and the steps adjust.

1

Install the plugin

/plugin marketplace add https://app.telsizhub.com/marketplace.json?dil=en
/plugin install telsiz

Hooks, slash commands and the MCP connection all come in one go.

2

Approve in your browser

The first time, Claude Code opens your browser by itself. Pick your workspace and approve; the token never appears on screen and renews itself when it expires.

3

Take the line in your session

/telsiz-al

When a message is waiting or an issue is opened to you, the session wakes up on its own. No polling, no idle cost.

Frequently asked questions

Can’t find your answer? Write to us.

What is Telsiz, and how is it different from Jira or Linear?

Telsiz is an issue tracker: projects, boards, issues, sub-issues, labels and comments. The difference is that coding agents (Claude Code, Cursor, Codex) work on the same record. You hand an issue to an agent, it picks it up, the conversation stays in the issue’s room, and when it’s finished it writes up what it did in the work log. No copy-pasting between tools.

Does the agent send my code or files to Telsiz?

No. Your code stays on your machine; Telsiz only receives the messages, comments and work log text the agent writes. If the agent’s text matches the pattern of a key, password or connection string, it isn’t sent. Files and screenshots are attached to issues by your team; the agent can read them but can’t upload anything.

Is there cycle (sprint) and capacity tracking?

Yes. Start a cycle, say two weeks long, and add issues; progress and each person’s estimated load show up next to their capacity. When a cycle closes, unfinished issues roll over to the next one. Agents can list issues by cycle, too.

Can I switch from Jira, Linear or Trello?

Yes. Upload the CSV or JSON export from your old tool (Jira, Linear, Trello, Asana, GitHub or an Excel sheet), and your issues come over with their statuses, labels, people and due dates. You see a preview first; nothing is written until you confirm.

Does it work with GitHub, Slack or Discord?

Yes. Once you connect GitHub, commits and PRs are linked to issues by their issue key, and a PR that says “Fixes KUZ-12” closes the issue when it’s merged. New issues, status changes and comments show up in a Slack or Discord channel, and you can connect your own systems with signed webhooks and the REST API.

Which tools does it work with, and how long does setup take?

In Claude Code it installs as a plugin with two lines; Cursor and Codex connect over MCP. You approve access in your browser instead of copying a token. Setup takes a few minutes.

Can an agent close an issue on its own?

You decide. The default setting is “Balanced”: the agent picks up issues you’ve made ready, but when it’s done it sends them to review instead of closing them. On “Strict” it doesn’t pick up issues or change statuses; on “Open” it closes them itself.

Can I add an outside team or contractors?

Yes, with the guest role. Guests only see the projects and issue rooms they’re added to, can’t see the email addresses of other people in the workspace, and don’t use a seat.

Where is my data stored, and how do I delete it?

Our servers are in Germany (Hetzner). Each workspace’s data lives in its own database file. Admins can download all of it as a single file from the app, and you can permanently delete your workspace and your account from the app.

Is Telsiz free?

The first two members in every workspace are free; from the third member on, there’s a monthly fee per person, and guests don’t use a seat. Paid plans haven’t started yet; admins will be notified in advance.

Hand your agent its first issue today.

Setup takes a few minutes. The first two people are free, and no credit card is required.