# LINE## Features

What the LINE bridge can do

| Direction         | Feature                                               |
|-------------------|-------------------------------------------------------|
| Matrix -&gt; LINE | Text, images, videos, files, voice notes, audio, GIFs |
| Matrix -&gt; LINE | Mentions, replies, read receipts                      |
| Matrix -&gt; LINE | Reactions (limited to ~120 emojis)                    |
| Matrix -&gt; LINE | Message unsending and deletion                        |
| Matrix -&gt; LINE | Leaving group chats                                   |
| LINE -&gt; Matrix | Text, images, videos, files, voice notes, audio, GIFs |
| LINE -&gt; Matrix | Location sharing (receive only)                       |
| LINE -&gt; Matrix | Contact sharing (receive only, LINE friend and vCard) |
| LINE -&gt; Matrix | Mentions, replies, read receipts                      |
| LINE -&gt; Matrix | Stickers and link previews                            |
| LINE -&gt; Matrix | Call notifications (voice and video, with duration)   |
| Misc              | Prefetch missed chats on bridge start                 |
| Misc              | Group chat support                                    |
| Misc              | Automatic session recovery on start and after expiry  |

## Usage

This bridge runs LINE inside Matrix. It does that by presenting itself to LINE as the LINE Chrome extension, and that one detail decides most of this page.

### When the bridge goes quiet

Did something log in to LINE’s Chrome extension while the bridge was running? That is your answer. LINE allows exactly one Chrome extension session per account, the bridge was sitting in it, and the extension took the seat. LINE told nobody: messages simply stop arriving while the bot goes on answering you as if all is well.

The two cannot both be logged in. Log in to the extension and the bridge gets kicked; the bridge reconnects on its own and kicks the extension right back. That loop runs until somebody gives up, and the bridge retries a lot longer than you will. Pick one. If you want the extension back, log the bridge out first.

Once that is settled, send `login` again.

### Before you log in

Your LINE account needs an email address, and plenty of accounts that were created on a phone never got one. Set it in the LINE mobile app under Settings → Account → Email address. If the bot tells you LINE rejected the email or password and you are certain the password is right, this is why.

### Invite the bot to a management room

Start a chat with `@linebot:your-server.com` to create a management room.

**Replace `your-server.com` with your actual base domain.** Leaving it as `your-server.com` or `example.com` will not work.

The bot posts a confirmation to the room. That is your signal to log in.

### Authentication

Your phone does the interesting part here, so there is no devtools spelunking and nothing to copy out of a browser.

⚠️ Get the password wrong enough times and LINE temporarily locks login on the whole account, so a second attempt from anywhere else is blocked too. Type it carefully the first time, and if the bot says LINE has locked login, wait it out instead of hammering it.

1. Send `login` to the bridge bot.
2. Send the email address and password on your LINE account when the bot asks for them.
3. The bot shows you a PIN code. Open LINE on your phone and enter it there.
4. Come back to the Matrix room and click Continue.

Your recent chats start showing up as rooms.

### Useful commands

Send `help` to the management room and the bot lists everything it supports. The ones you will actually reach for:

- `login`: authenticate the bridge.
- `logout`: disconnect your LINE account and free up the Chrome extension seat.
- `search <query>`: search for people on LINE.
- `start-chat <identifier>`: open a direct chat with someone.


---
* [llms.txt](https://etke.cc/llms.txt): full site index in markdown
