Skip to content

Releases

parro-api-client 0.13.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 19:46
Immutable release. Only release title and notes can be modified.
a83c2dd

Photos, videos and documents in a chat are shown, where a message used to look empty. The desktop
app shows a chat the way a messenger does, with small pictures you can click. A calendar item's
link is shown, everywhere.

Added

  • Files in a chat. A message with a photo, a video or a document used to have no text at all,
    so it looked empty. It now shows what it holds: [video] IMG_0001.MOV (12 MB), after the text if
    there is any. attachment --chat <chat id> --message <message id> reads or saves the file
    (--save-to DIR); the MCP tool parro_attachment takes chatroom_id and message_id.
  • A video or a sound recording is never read as text. The MCP tool returns a video's small
    picture and the file's details, never the film itself. The film is only fetched when you save it.
  • "Joined", "left" and "renamed the chat" are shown as such. They were a second kind of empty
    message.
  • A calendar item's link. A teacher can add a web address to a calendar item. It was not shown
    anywhere; now it is a line in calendar --details, in the MCP tool, in the archive and in the
    desktop app.
  • Desktop app: a chat that reads like a chat. Your own messages are on the right, the others on
    the left. A name appears once per run of messages, in a colour per person; the time is small, and
    the date is a line between days.
  • Desktop app: small pictures. A photo or a video in a chat shows its small picture; so do the
    photos of an announcement or calendar item, side by side in place of a row per photo. A click
    shows the photo, with Save…. A video or recording asks Open or Save…; Open fetches it and
    hands it to your computer's own player, and the copy is removed when the app closes. In the
    Flatpak that copy is kept in the app's cache folder: from the sandbox's own temporary folder the
    desktop could not open it.
  • Deleting a chat message you wrote yourself: chat-delete <chatroom-id> <message-id> shows
    the message and asks first; chat-messages now shows the id on your own messages. In the desktop
    app your own messages have a small Delete, and only Confirm deletes. For an assistant it is
    the MCP tool parro_delete_chat_message, off unless you set PARRO_ALLOW_DELETE_CHAT=1. It
    cannot be undone, and everyone in the chat sees that a message was deleted.
    This changes the client's promise again: it reads, and it can change five things, each only
    when you ask (the guide).
  • Desktop app: a photo is shown scaled to fit its window, and follows the window's size.
    Actual size shows it as before, with scroll bars.
  • Desktop app: an address written as www.school.nl is a link too, and opens as https://.
  • Links in the news from Parro keep their address: "dit filmpje (https://…)" in place of only
    "dit filmpje".
  • API description: a chat message's attachment, the entry types THUMBNAIL and VIDEO,
    status messages (chat.RChatStatusMessage), a calendar item's url, an announcement's
    richTextContents, and deleteChatMessage.

Changed

  • In the JSON output, a chat message's attachment has the same compact form as an announcement's
    (attachment_id, filename, contentType, size, …) in place of the API's own object. Each
    attachment also says whether it is media (image, video, audio) and whether it has a small
    picture. A photo, which has no name in Parro, is called photo-<id>.jpg.
  • The desktop app fetches the small pictures of the item or chat you open from Parro's file server,
    without asking. They are kept in the same cache as other attachments (cache --clear empties it).

Download the desktop app

No Python needed. Pick the file for your computer; the instructions explain the first
start on each system.

Computer File
Windows 10 or 11 Parro-Client-0.13.0-windows-x64.msi
Mac with macOS 14 or newer (Apple silicon and Intel) Parro-Client-0.13.0-macos.dmg
Linux on a usual PC Parro-Client-0.13.0-linux-x86_64.flatpak
Linux on ARM (Raspberry Pi 5, Apple silicon with Asahi) Parro-Client-0.13.0-linux-aarch64.flatpak

The installers are not signed yet, so Windows and macOS warn at the first start; the instructions
say what to do. Check a download with SHA256SUMS, or that GitHub built it from this release:
gh attestation verify FILE --repo chris-swift-dev/parro-api-client.

parro-api-client 0.12.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 22:20
Immutable release. Only release title and notes can be modified.
21a9ab0

The desktop app without Python: an installer for Windows, macOS and Linux, which names its
publisher and can tell you about a new version. A project page with the downloads, and Swagger UI
next to it. In the app, chats open at the newest message, messages above a section stay short, and
the login dialog shows only what most people need.

Added

  • The desktop app without Python: each release has an installer for Windows (.msi), macOS 14 or
    newer (.dmg, Apple silicon and Intel) and Linux (.flatpak, x86_64 and aarch64), with Python and
    Qt inside. They are not signed yet; docs/INSTALL-DESKTOP.md explains the
    first start on each system. Each file is in SHA256SUMS and has a GitHub build attestation
    (gh attestation verify).
  • Desktop app: telling you about a new version, if you agree at the first start. It asks GitHub
    at most once a day, sends nothing about you, and downloads nothing itself. A Help menu has the
    switch, Check for updates now and About.
  • The desktop app has its own icon, in the window, the taskbar and the installers.
  • The installers name their publisher, chris-swift-dev (as in the licence): under Installed
    apps
    on Windows, in Get Info on macOS, and in Linux software centres, which now also show the
    app's summary, licence, homepage and the "unofficial" line. The warning at the first start on
    Windows and macOS stays until the installers are signed. The package on PyPI names its author too.
  • A project page, chris-swift-dev.github.io/parro-api-client:
    what it is, a download button per system (the one for your computer first), the three ways to use
    it and the safety rules, on a phone too. It loads nothing from other sites and is rebuilt when a
    release is published, so its buttons always name the newest installers.
  • macOS: a Terminal shortcut past the first-start check, for people who prefer it, in
    docs/INSTALL-DESKTOP.md.
  • Desktop app: HTTPS certificates are checked by the operating system, as a browser does it,
    through the small truststore library (now part of the gui extra and the installers). Without
    it, the installers' own Python could not verify Parro, GitHub or the attachment server on macOS and
    some Windows computers. Certificates a company installs on the computer work too. The command line
    and the MCP server are unchanged.

Changed

  • Swagger UI moved to …/parro-api-client/api/,
    the spec to api/parro.openapi.json (the old address works too). Old links to an operation
    (…/#/Chat/…) are sent on.
  • Desktop app: a chat opens at its newest message, like other chat apps. It stays at the end
    while the window or the splitter changes size, until you scroll up; after Send… it is at the end
    again, with your message.
  • Desktop app: a message above a section takes at most two lines. The rest, such as every file
    that Save all attachments… could not save, is behind Details…, where it scrolls and can be
    copied, and the message can be closed. Save all counts the reasons instead of listing every file.
    Long attachment names are shortened with "…", so their buttons stay in view, and the window has a
    minimum size (760 × 520) at which every section's buttons fit.
  • Desktop app: the login dialog shows only the password form. Logging in in the browser, which
    few people need, is under Other ways to log in…; a browser login that was started and not
    finished opens there directly, also after a restart. The command line and the MCP server are
    unchanged.
  • Desktop app: parro-client-gui --version, and --self-check, which starts the app without a
    screen and without logging in, to check an installation.

Fixed

  • Saving attachments into a folder that cannot be written to no longer stops at the first file
    with "Something went wrong (PermissionError)" in the desktop app, or an error in the command line.
    Each file now says it "could not be written" and why, and the other files are still read. Save
    all
    counts it like any other reason.

Download the desktop app

No Python needed. Pick the file for your computer; the instructions explain the first
start on each system.

Computer File
Windows 10 or 11 Parro-Client-0.12.0-windows-x64.msi
Mac with macOS 14 or newer (Apple silicon and Intel) Parro-Client-0.12.0-macos.dmg
Linux on a usual PC Parro-Client-0.12.0-linux-x86_64.flatpak
Linux on ARM (Raspberry Pi 5, Apple silicon with Asahi) Parro-Client-0.12.0-linux-aarch64.flatpak

The installers are not signed yet, so Windows and macOS warn at the first start; the instructions
say what to do. Check a download with SHA256SUMS, or that GitHub built it from this release:
gh attestation verify FILE --repo chris-swift-dev/parro-api-client.

parro-api-client 0.11.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 13:42
Immutable release. Only release title and notes can be modified.
2836e3f

A better desktop app: details that always fit in the window, saving all attachments at once, less
waiting when you switch sections, and logging in by itself from a password file. Tab completion for
the command line. And the MCP tool hints can now be seen by services that read the code instead of
running the server.

Added

  • Save all attachments… in Announcements and Calendar, next to Mark as read: one folder
    question, then every file, with a report that names each file that failed.
  • Logging in by itself in the desktop app: tick the box in the login dialog and choose a private
    file with your password. One password check when the login has expired, none after a rejected
    password until you log in by hand. Only the e-mail address and the file's path are remembered.
    PARRO_USERNAME and PARRO_PASSWORD_FILE work as in the command line.
  • "Fetched at 14:32" next to each section's title, and under an opened announcement.
  • Every MCP tool has a title.
  • Tab completion for the command line in bash, zsh and fish: parro-client completion bash
    (or zsh, fish) prints a script for your shell's startup file. It completes commands, options,
    their fixed values and file names, and never contacts Parro.

Changed

  • An announcement or calendar item with long text, many attachments or many helper slots fits in the
    window: Mark as read stays visible under the text, the attachments and the answer and helper rows
    scroll, and a line you can drag shares the height between the two.
  • The desktop app keeps what it fetched for 5 minutes, in memory only, so switching sections or going
    back to a filter choice is instant. Refresh and every change you make fetch again.
  • The MCP tool hints (readOnlyHint and the others) are written into each tool's definition in the
    code, so services that read the code see them. What clients receive is unchanged.

Fixed

  • A quick second click in the desktop app could send a chat message twice: two clicks on Send…
    opened two previews, and confirming both sent it twice. Every button that starts a request now stays
    off until the answer is in, and a section runs one action at a time. The same goes for answers,
    helper sign-ups, Mark as read (which asked twice), Refresh, the subscription and privacy links,
    and reading or saving an attachment.
  • In the desktop app, Mark as read and the last answer or helper rows could fall off the bottom of
    the window for an item with a lot in it, and could not be reached.
  • Saving an attachment claims the file name and writes it in one step, so a file that appears in the
    meantime is not replaced either (also for --save-to).

parro-api-client 0.10.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 22:10
Immutable release. Only release title and notes can be modified.
b39c8d7

A desktop app: parro-client-gui does what the command line does, in a window on Windows, macOS and
Linux. It is optional, and it needs Python 3.12 or newer. The command line and the MCP server do not
change and keep working on Python 3.10 or newer.

Added

  • parro-client-gui, installed with pipx install "parro-api-client[gui]": an overview,
    announcements with attachments, the calendar, chats, your family's details and the local archive.
  • It shares its login, cache and archive with the command line.
  • It follows your system's light or dark setting. The sidebar's icons are from Lucide (ISC licence),
    and their licence comes with the app.
  • The four changes the client can make are all there, and need a click on Confirm in a dialog that
    shows exactly what would happen. Nothing changes because you opened or read something.
  • docs/DESKTOP-APP.md explains it.

Changed

  • sync_archive can report its progress, for the desktop app. The command line behaves as before.

parro-api-client 0.9.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 08:43
Immutable release. Only release title and notes can be modified.
df98121

Say whether you are coming: rsvp answers a calendar item's invitation with accept, decline or
tentative. This changes the client's promise again: it reads, and it can change four things,
only when you ask: mark items as read, send a text message, sign you up or withdraw you as a helper,
and answer an invitation. An answer is a statement in your name: the school sees it, and you can
change it but not remove it.

Added

  • rsvp accept|decline|tentative EVENT. It shows the item, your current answer and the new one,
    and asks first. --yes skips the question for scripts; without a terminal and without --yes,
    nothing changes.
  • It refuses an item that does not ask for an answer, an item that is cancelled and an item in the
    past. The answer you already gave is not sent again.
  • The agenda and overview show your answer in place of RSVP needed.
  • The MCP tool parro_rsvp, only when you set PARRO_ALLOW_RSVP=1 (a switch of its own). Without
    confirm: true it only returns the preview, and it is marked as destructive so MCP clients ask
    first. Please read the warning in the README before you switch it on.
  • The spec describes answering an invitation, your own answer on the event, and the list of everyone
    an invitation went to, with a warning about the personal data in it.

Changed

  • The MCP tools parro_get and parro_attachment refuse the list of everyone an invitation went to,
    because it holds other people's names and answers. The command get still reaches it if you ask.
  • An answer is never repeated on its own: after a timeout or a server error the client says it may
    or may not have gone through.
  • The README, the help text, SECURITY.md and the User-Agent describe the new promise.
  • The README is shorter again. The details moved to three guides that come with every download:
    docs/CHANGING-THINGS.md, docs/MCP.md and docs/CALENDAR-AND-ARCHIVE.md.

parro-api-client 0.8.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 22:25
Immutable release. Only release title and notes can be modified.
eeb2a72

Say you can help: helper signup and helper withdraw put you on a calendar item's helper slot, or
take you off it. This changes the client's promise again: it reads, and it can change three
things, only when you ask: mark items as read, send a text message, and sign you up or withdraw you
as a helper. A sign-up is a promise in your name: the school sees it, and you may take the last
place.

Added

  • helper signup EVENT, with --count N for more than one place (for example three children
    in your car) and --slot ID when an item has several slots, and helper withdraw EVENT. They
    show the item, the slot and the places taken, and ask first. --yes skips the question for
    scripts; without a terminal and without --yes, nothing changes.
  • They refuse an item that asks for no helpers, an item in the past, a full slot, a count that does
    not fit the places left, signing up where you already have, and withdrawing where you have not.
  • calendar --details shows the id of each helper slot.
  • The MCP tools parro_helper_signup and parro_helper_withdraw, only when you set
    PARRO_ALLOW_HELPER_SIGNUP=1 (a switch of their own). Without confirm: true they only return
    the preview. Please read the warning in the README before you switch them on.
  • The spec describes adding, listing and removing a helper commitment, and says what is not known
    about it.

Changed

  • A helper change is never repeated on its own: after a timeout or a server error the client says
    it may or may not have gone through.
  • The README, the help text, SECURITY.md and the User-Agent describe the new promise.
  • The README's opening note no longer says only GET calls are used, which stopped being true in
    0.6.0.

parro-api-client 0.7.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 19:45
Immutable release. Only release title and notes can be modified.
23df097

Reply from the terminal: chat-send sends a text message to a chat you are in. This changes the
client's promise again:
it reads, and it can change two things, only when you ask: mark items as
read, and send a text message. Real people receive what you send, under your name, and as far as we
know a message cannot be taken back.

Added

  • chat-send ID "text" (or --file PATH, --file - for standard input). It shows the chat, who
    receives the message and the exact text, and asks Send this message? [y/N]. --yes skips the
    question for scripts; without a terminal and without --yes, nothing is sent.
  • It refuses empty text and chats that are archived, that you have left, that have replies switched
    off, or that are with a bot.
  • The MCP tool parro_send_chat_message, only when you set PARRO_ALLOW_SEND_CHAT=1 (a switch of
    its own). Without confirm: true it only returns the preview, and it is marked as destructive so
    MCP clients ask first. An assistant also reads what others write, so please read the warning in
    the README before you switch it on.
  • The spec describes POST /chatroom/{id}/chatmessage, and says what is not known about it.

Changed

  • A message is never sent twice on its own: after a timeout or a server error the client says it may
    or may not have arrived. The text is never logged or stored.
  • The README, the help text, SECURITY.md and the User-Agent describe the new promise.
  • Writes no longer follow redirects.
  • Every MCP tool now states all four hints (readOnlyHint, destructiveHint, idempotentHint,
    openWorldHint), matching what it does. MCP clients can use them to decide when to ask you.

parro-api-client 0.6.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 22:09
Immutable release. Only release title and notes can be modified.
38fcac4

See what is new, and mark what you have read: overview now shows only unread announcements and
new calendar items, and mark-read marks an item as read. This changes the client's promise:
it used to be read-only; now it reads, and the one change it can make in Parro is marking items as
read, only when you ask. The school sees what you mark (read counts, read receipts), and so does
the Parro app.

Added

  • mark-read announcement|calendar|chat ID marks one item as read. It looks the item up first,
    so a wrong id is an error, not a write, and leaves items that are already read alone.
    mark-read group ID shows how many unread announcements a group has; with --yes it marks them
    all.
  • --mark-read on announcement ID and chat-messages ID: show it, then mark it.
  • The MCP tool parro_mark_read (one item at a time), only when you set
    PARRO_ALLOW_MARK_READ=1. It is marked as not read-only, so MCP clients ask before calling it.
  • Chat filters: chatrooms --unread --archived only|include --type group --schoolyear 2025, and
    chat-messages ID --since 2026-10-01. The MCP tools take the same options.
  • chat-members ID (MCP parro_chat_members): who is in a chat, parents with their children
    and teachers, and who is admin; --former adds members who left.
  • The spec describes 10 more operations: chat details, members, scheduled and single messages,
    school years, an identity, an announcement attachment, and the three calls that mark items read
    (in their own section, Read state, which says what the school sees).

Changed

  • overview lists only what you have not read: unread announcements and new calendar items.
    overview --all (MCP all: true) shows the latest announcements and everything coming up, as
    before.
  • chatrooms leaves archived chats out, as the API does by default; --archived include adds them.
  • The README, the help text, SECURITY.md and the User-Agent describe the new promise. Making the
    client write anything else, or mark something without being asked, is a security problem.

Fixed

  • sync missed archived chats: the API leaves them out unless asked. It now archives them too.

parro-api-client 0.5.1

Choose a tag to compare

@github-actions github-actions released this 06 Nov 12:14
Immutable release. Only release title and notes can be modified.
1d7d7a4

Know how long you stay logged in: a login lasts at most 8 hours, and status now says until when.

Added

  • status (MCP parro_auth_status) says until when the login lasts and what happens then, e.g.
    Login: valid until Fri 6 Nov 2026 19:37 (7 h 40 min left); then log in again. JSON:
    login_valid_until, login_expires_in_seconds.

Fixed

  • The docs, the help text and the spec promised that a login with offline_access lasts "far
    longer" than the web app's 8 hours. Measured: a login lasts at most 8 hours, however often it is
    refreshed. They now say so, and what happens after 8 hours.
  • The TestPyPI install command in the docs (--extra-index-url, as pipx needs it).

parro-api-client 0.5.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 11:46
Immutable release. Only release title and notes can be modified.
f266861

Install it like any other command, on Windows, macOS and Linux: pipx install parro-api-client
(or uv tool install parro-api-client), then parro-client overview.

Added

  • The commands parro-client and parro-client-mcp, from the Python package
    parro-api-client on PyPI. pipx and uv put them on your PATH (on Windows as .exe files) and
    update them with one command. The MCP server can also run without an install step:
    uvx --from parro-api-client parro-client-mcp.
  • Releases carry the wheel and sdist next to the archives, all in SHA256SUMS. Publishing a
    release uploads exactly those two files to PyPI, with trusted publishing (no token stored).
  • Tested on Windows, macOS and Linux, Python 3.10 and 3.14, including installing the package and
    running both commands.

Changed

  • Help, hints and messages name the command as you started it: parro-client … when installed,
    parro_cli.py … from a release archive. python3 parro_cli.py and parro_mcp.py keep working,
    so existing MCP configurations need no change.
  • The code of the CLI and the MCP server moved into the package (parro/cli.py,
    parro/mcp_server.py).
  • Archived files say archived with parro-api-client (sync) in their header.
  • The README's links and pictures are absolute, so they also work on the PyPI page.

Fixed

  • On Windows: output is UTF-8 (the console could not print markers such as ● and 📌),
    calendar --ics - keeps single CRLF line endings, and the MCP server ends each message with a
    plain line feed.