Export your Signal chats to markdown files with attachments

backup chat export signal sqlite
7 Open Issues Need Help Last updated: Mar 13, 2026

Open Issues Need Help

View All on GitHub
bug good first issue

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite

AI Summary: This issue proposes migrating the project from the deprecated 'rye' tool to 'uv'. The migration involves updating the project's tooling and documentation to reflect the use of 'uv', as outlined in the provided 'rye' guide.

Complexity: 3/5
good first issue

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite
Search feature about 1 month ago
enhancement good first issue

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite

AI Summary: The user is encountering an `OSError: [Errno 63] File name too long` when exporting attachments from a macOS system. This error occurs because the generated file names for attachments exceed the operating system's maximum file name length limit, which is reported to be over 290 characters in this case.

Complexity: 2/5
bug good first issue

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite

AI Summary: The `--json` and `--no-json` command-line arguments in `signal-export` are not functioning correctly, as JSON output files are always generated regardless of the flag. The `json_output` variable, intended to control this behavior, appears to be unused in the code section responsible for producing JSON output.

Complexity: 1/5
bug good first issue

Export your Signal chats to markdown files with attachments

Python
#backup#chat#export#signal#sqlite