/oss · 8 merged

Tencent/teamai-cli

A command-line tool that lets a team share the skills and settings of their AI coding assistants from one place.

the project on GitHub (opens in a new tab)
  1. 20 Oct 2026

    Pasted screenshots survive a move between Codex and other tools

    What was broken
    A screenshot pasted into a Codex session disappeared when the session moved to another tool. Moving it back turned any image into plain text. The report still said nothing was lost.
    What I changed
    I made the tool read Codex's pasted images and write them back the same way. Codex now counts as supporting images.
    Why it matters
    A moved session keeps the screenshots that explained the problem.

    see the code, #1230 (opens in a new tab)

  2. 20 Oct 2026

    Absolute repo paths over SSH keep their leading slash

    What was broken
    Pointing the tool at a Git server by an absolute path, like host:/srv/git/team.git, quietly dropped the first slash. It then looked for the repository in the wrong place and the clone failed.
    What I changed
    The tool now keeps the slash when it was typed, so the path means what the person wrote. Paths without a slash, and web addresses, work as before.
    Why it matters
    Teams that host their shared setup on a plain Git server can connect.

    see the code, #1217 (opens in a new tab)

  3. 19 Oct 2026

    Codex tool output keeps its text when sessions move

    What was broken
    When a Codex session was moved or archived, tool results stored as a list came out as "[object Object]" instead of their text.
    What I changed
    I made the reader join the text parts of such results, the same way it already does for Claude Code.
    Why it matters
    Moved sessions keep what the tools actually printed.

    see the code, #1202 (opens in a new tab)

  4. 18 Oct 2026

    Codex reasoning comes through when a session moves

    What was broken
    Moving a Codex session to another tool lost all of Codex's reasoning. The tool looked for it in a place Codex never writes, so every reasoning step came out empty.
    What I changed
    I made the tool read the reasoning from where Codex really keeps it, and still read the old place first so nothing else changes.
    Why it matters
    A moved Codex session keeps the model's thinking, not a row of blank blocks.

    see the code, #1203 (opens in a new tab)

  5. 16 Oct 2026

    Moved coding sessions keep their turns in order

    What was broken
    Moving a Claude Code session with the tool could scramble it: every question came first, then every answer. The tool still reported the move as fully faithful.
    What I changed
    The tool now follows each conversation thread from start to end before the next one, so a session reads back in its real order.
    Why it matters
    A moved session reads like the conversation that really happened.

    see the code, #1145 (opens in a new tab)

  6. 15 Oct 2026

    Moved coding sessions keep the edits they made

    What was broken
    TeamAI can move a coding session from one AI tool to another. Every file edit made in Codex lost its content on the way, and the tool still said nothing was lost.
    What I changed
    I made it read the edit's content from the place Codex keeps it.
    Why it matters
    A moved or archived session still shows what each edit changed.

    see the code, #1146 (opens in a new tab)

  7. 14 Oct 2026

    Empty settings files no longer pile up in members' projects

    What was broken
    When the team removed the last of its shared tool connections, each member's next update left empty settings files behind. No longer hidden from git, they showed up as new files and were easy to commit by mistake.
    What I changed
    Updating now deletes a settings file it leaves empty, as the cleanup commands already did. Files with anything else in them, or that git tracks, stay.
    Why it matters
    Members' projects stay clean, with nothing stray to commit.

    see the code, #1110 (opens in a new tab)

  8. 14 Oct 2026

    Files the team deleted no longer come back

    What was broken
    When someone deleted a file from a shared skill, every teammate's copy kept it. The next time a teammate shared their copy, the deleted file returned for everyone.
    What I changed
    Updating now removes a file the team deleted, as long as the teammate never changed it. Files they added themselves stay.
    Why it matters
    Cleanups stick, and shared skills stop growing back old files.

    see the code, #1109 (opens in a new tab)

← every project