Beta Chatick is in beta: it works, it is used daily, and things still change and occasionally break.

Where your coding assistant joins the team

Built for developers. Connect Claude Code to your project and it works there as you: creates and closes tasks, reads the whole history, answers in chat, sees what everyone has been doing.

Free while in beta

Hand this to your assistant

Read https://chatick.com/ai.txt and tell me in plain words what Chatick is, whether it fits my team, and how to connect you to it.

  1. Copy the prompt
  2. Paste it into your assistant
  3. It joins the project and starts working

Claude Code

Install the skill to get started

The skill teaches Claude to work inside Chatick: take tasks, move statuses, tick checklists and report in comments.

  1. Restart Claude Code
  • “What is on me today?” instead of hunting the board
  • Task, estimate and status straight from the conversation
  • Every result lands in a task comment

The assistant works inside the project, not next to it

That second command installs the MCP server — the part that connects your coding assistant to the workspace itself. Without it the skill still works; you just retype a code every session.

  1. It works where the team can see

    It picks up tasks, moves them along and reports back in comments. The work lands in the project history instead of disappearing into a chat window nobody else reads.

  2. You decide how much it sees

    One project, a whole company, or everything you belong to. It never grants more than your own access — every call checks your permissions — and you can close the tunnel in one click.

  3. Everything is signed with your name

    Whatever the assistant does, the history records it as done by you, through an assistant. Six months later it is still clear who changed what and why.

With the desktop app running, approving takes one button — no code to copy at all.

Use it wherever you work

The same workspace in the browser and on your desktop, with a tray panel that keeps the timer and your notifications one click away.

Beta software. Expect rough edges, and please report anything broken — every report is read.

The macOS builds are not signed yet

The Windows build comes from the Microsoft Store and is signed by the Store itself — no warnings there. macOS is another matter: a signing certificate costs money, and Chatick is free with no sponsors behind it, so macOS will warn you about the file. Nothing is hidden: the source is open, and you can build the same app yourself.

Store blocked on your machine? Direct download: Chatick-Setup-0.4.0.exe

Mobile apps are on the roadmap.

For companies with their own system

Keep your system. Move the work here.

You already have projects, clients, deadlines and reporting. Chatick takes tasks, time, chat and documents — your system stays the source of truth, and the two talk over an API.

  • Projects and people come from your system. We never invent them.
  • Your reporting keeps working: tasks and hours are readable back at any moment.
  • One click moves a person from your system straight into a project — no second sign-in.
  • Events reach you the moment they happen, so your dashboards do not poll us.
How the integration works

Copies the machine-readable guide. If the clipboard fails, it lives at chatick.com/integration.txt

Sound familiar?

Your AI is blind to the project

It writes great code and knows nothing about the task, the thread where it was agreed, or who is waiting for it.

You are the copy-paste layer

Pasting the task in, pasting the result back, restating the context every session.

History dies at the scroll limit

The decision was made two months ago in a chat nobody can search anymore. So it gets made again, differently.

Two sources of truth

Tasks live in a tracker, the real conversation happens in a messenger. Nothing matches.

Your assistant works inside the project

Not a chatbot bolted onto a tracker — a connection that gives your AI the same access you have.

It runs the tasks

Creates, updates, closes, assigns, breaks a task into a checklist, comments — through the bridge, with your permissions, under your name.

It reads the whole history

The chat is compressed into per-day summaries; your assistant searches them, finds the right period and pulls up the exact words. Nothing is ever deleted.

It sees who did what

The project log is open to it: who changed which task, when a file was deleted, what happened while you were away.

It answers in the chat

Replies to the team, attaches builds, posts what it finished — as a participant, not as a tool you narrate for.

And a real workspace around it

Everything the project needs, next to the conversation that drives it — and all of it reachable by your assistant.

Several companies at once

Work across companies and projects in parallel, in one window and one tray panel. Your assistant can hold them all or just one — you choose at connection time.

Tasks & checklists

Sprints, priorities, estimates, comments, drag & drop, Excel import/export. A task splits into checklist items your AI can fill in and tick off.

Documents, co-edited

Rich editor with tables and images, real-time editing with live cursors, version history and public links.

File manager

Attach from chat, tasks or clipboard. Images optimised automatically; originals kept only when you ask. Your own S3/R2 if you want no limits.

Resources & secrets

Links, panels and credentials in one place, encrypted at rest and revealed only on demand. The AI can save them, and can never read the values back.

Notes for the team — and the AI

Decisions, solutions, contradictions and reminders as a searchable journal. Mark a solution company-wide and other projects find it before debugging it twice.

Time tracking

Timers and after-the-fact entries, reports by person, task and day, with export. Your assistant can start, stop and report on them.

Backups & export

Scheduled encrypted backups, seven days of undo, and full export whenever you want. Nothing here is held hostage.

The bridge

One line, and your assistant is part of the project

Claude Code — or any assistant that can read docs and call HTTP — connects to Chatick and works there: tasks, checklists, chat, files, documents, notes, time, and the full compressed history.

  • One line to paste. Your assistant reads the guide and connects itself — no SDK, no integration to write.
  • You approve access in the browser — no token ever goes through your chat.
  • It acts as you, within your permissions, and every action lands in the project history under your name.
  • Connect to one project, a whole company, or everything you have access to.
  • A connection is a tunnel: close it and the access is gone.

No permanent tokens. Nothing to leak. It can never do more than you can.

Paste this into your assistant

Connect to my Chatick project: read https://api.chatick.com/x and follow the instructions.

How it works

1

Create a project

A project is a group. Invite your team — chat, tasks, files and documents are ready.

2

Connect your assistant

Paste one line into Claude Code. It reads the guide, you approve access in the browser, and it starts working in the project.

3

Work as usual

You write code, it handles the project around it — tasks, answers, history. The chat AI meanwhile translates, deduplicates and turns talk into tasks.

Built to be trusted with your team’s work

The unglamorous parts, done properly — losing someone’s work once is enough to lose them.

No lock-in, by design

Export and import everything, whenever you want. The source code is open: if you like the system, run it on your own servers — and if we ever stop maintaining it, nothing you built here dies with us.

Free, and honestly so

No card, no trial countdown, no seats to count. Every project gets room for real work, and the limits are stated plainly instead of hidden in a plan comparison.

Backed up, not hoped for

The database is backed up on a schedule and the copies are encrypted. Deleted documents and notes stay recoverable for seven days — a mistaken click is not the end of the story.

Encrypted where it matters

Everything travels over HTTPS. Credentials kept in Resources are encrypted before they reach the database, and access inside a project is decided by roles.

Dangerous things ask twice

Deleting a project or a company wipes everything belonging to it, files included. So it lives in a clearly marked danger zone, needs confirmation, and emails every member afterwards.

Servers in the EU

Data sits on servers in Germany. Export it or delete it whenever you like — the privacy page names exactly who else processes it.

Nothing hidden in the log

Every release is written down before it ships; the build refuses to run otherwise. What changed is always readable on the changelog page.

Behind this project

Who is behind Chatick

A partner who backs it, a developer who writes it, and a product both of them use.

Partner and sponsor

Building people, creating entrepreneurs

An Israeli startup consultancy with more than ten years behind it. Its founders have helped raise hundreds of millions of shekels for the companies they backed. They back Chatick and use it in their own work.

AnyApp

Development studio

A major Israeli studio building mobile apps for Android and iOS and web systems — the whole way from spec to launch. Dozens of products shipped.

Development

One developer, fifteen years of building software, writing Chatick daily and using it to run the work on Chatick itself.

Development company

The studio behind the work. Chatick is open source and free while in beta — everything on this page is running today, none of it is a mockup of something planned.

Get in touch

Questions, bugs, ideas — all of it reaches a person, not a queue.

Common questions

Is it really free?
The source is open — take it and do what you want with it. Or use our server while you are getting a feel for it: free during the beta, no card, no trial timer.
Where does my data live?
On our servers by default. Connect your own S3 or R2 bucket and files never touch our infrastructure — backups included.
Who can technically see our data?
On our server, we can — the same as with any hosted service, and we will not pretend otherwise. If that is not acceptable, run Chatick on your own machine: the source is open. Either way, resource secrets are encrypted and files can live in your own S3 or R2.
What does the AI actually do?
It reads the project history, creates and closes tasks, answers in chat, and works through your own Claude Code or Cursor — the code stays on your machine.
Can we leave and take everything?
One JSON file with the whole company: projects, tasks, chat, documents. Open format, readable without Chatick.
Topic

Sent — thank you. You will get an answer by email.

Or email us directly: support@chatick.com

Give your assistant somewhere to work

Web today. Desktop for Windows & macOS next.

Open Chatick