Timon 0.1.7

Added

• Plugins can draw their menu entry with the product's own (NavLink from @timon/ui), so it folds with the side menu instead of squeezing its label into it.

• When accounts beyond the first superadmin are suspended (no pro licence, or no Multi-user plugin), the superadmin gets a card saying why; their data are kept.

• Signed plugins can now manage a team's accounts: add accounts and open their sessions (accounts:provision), say which rights each account holds (accounts:permissions-source), and serve pages without a session such as an invitation (http:public). The account provider also reads and updates the accounts it serves, writes the audit log, and reads the catalogue of rights a role can grant.

• Plugins can keep their data in a SQLite database of their own (ctx.sql, permission storage:sql), with migrations declared in their manifest and applied when they start.

• The Git widget's Publish tab can push to any remote of the repository: a picker beside Push shows each remote with what it lacks, and pushing anywhere other than the branch's upstream asks first.

• The Git widget asks before every push, naming the repository, the remote, its URL, the branch and the number of commits.

• The Git widget shows the other repositories inside a project folder (an ignored nested repository, or one listed in .worktreelinks): a picker switches between them, and a dot flags one with commits to push.

• A .worktreelinks file at the root of a repository lists ignored folders, such as a notes repository, that every Kanban task worktree links from the main checkout.

• Two advanced settings let task agents keep one account connector (Settings → Memory → Obsidian) and let any agent call chosen MCP tools without a permission card (Settings → Missions → Permissions).

• The first-run screens have a light/dark switch in the top-right corner; they follow your system until you pick, and your account keeps the mode you chose.

• Timon theme: the brand's dark and light palettes (the website's violet-tinted night, beige-leaning whites, peach and copper accents), now the theme of every new account. Existing accounts keep their theme and can pick Timon in Settings → Appearance.

• After updating from an earlier version, Timon signs you out once and opens the new welcome screen, then a new Sign in screen; once signed in, it offers to dress your main agent's mascot (Keep this look or Not now).

• Chat: Reply under a message (the agent's or yours) answers it: a strip above the input shows which one, and your message shows a quote that scrolls back to the original. The agent receives the message's reference and opening words, not a copy.

• Chat: Copy as Markdown under an agent's message copies its answer with the formatting, and every button under a message names itself on hover.

• Plugins: the chat.message.action slot adds a button under chat messages, with useChatMessage(), useComposerReply() and MessageActionButton (API 15).

• Agents: the mission_message_get tool reads a message of the conversation back by its id.

• After your account, a Choose your LLM screen asks whether Timon runs on your AI subscription (the AI tools Timon supports — Claude Code, Codex, Copilot CLI, Grok Build — installed and signed in from compact cards, then Ready with …) or on local models with Ollama; the main agent setup no longer shows its own Your AIs step a second time.

• Then What brings you here? asks your profile in one click — I write code, I automate or I'm discovering — and the setup conversation and the guided tour no longer ask it again.

• Then Bring your agent to life creates your main agent on one screen: its mascot, name, role and model on a card, and the view your profile recommends — six ready-made profiles, a five-question interview, or a sheet with role, folder, model, exact permission mode, skills, MCP servers and instructions — with a switcher to the other two.

• After your main agent is created, Discover Timon shows in four quick animated slides what your TIMs can do: work on their own, work as a team, and live inside a project with its own rules and memory; Next and Skip all keep it short.

• Customise on that card opens a side panel to pick the mascot's skull, fur, eyes and accessory, with a live preview and states to try; until then it dresses for the agent's job.

• Agents without a picture show their mascot instead of their initial.

• The agent editor has an Avatar tab, before Identity: pick the head the agent shows everywhere — an emoji, an uploaded image you frame, or its mascot, dressed with the same configurator as the first-run setup. The other two settings are kept, and agents whose head was never chosen keep their face.

• Change avatar in the right-click menu of an agent (chat card, Agents graph) opens that tab.

• An agent's mascot now shows what the agent is doing wherever it appears — chat cards and bubbles, the chat header, side rails, Multichat, the Agents graph, the Kanban: asleep, thinking, working, searching, waiting for you, happy when a turn ends, celebrating when a task is done.

• Settings → Appearance → Animate mascots keeps them still; they still show their state with their eyes, as they do when your system asks to reduce motion.

• The chat bubbles, Multichat, the Agents graph and the mobile agent list now show the head picked in the Avatar tab.

• Then your main agent's first conversation opens inside the onboarding: it speaks first, greets you by your first name in the language you picked, and writes its character from the card you made instead of asking for its language, name or picture again; beside it, its mascot shows whether it is thinking, working, waiting for your answer or pleased.

• In that conversation, the agent offers to set up what its card asked to run on its own (every day at a set time, on a webhook), creates nothing before your yes, and saves it switched off: switch it on in Triggers, under Routines for a daily routine or Webhooks for a webhook.

• It also offers to recruit two teammates, a coder and a reviewer, who appear beside it in the list; Later skips it.

• timon setup team --coder NAME --reviewer NAME and timon setup finish --no-tour, the CLI counterparts of the setup conversation's new tools.

• Onboarding: Timon installs its background service while you create your account, choose your AI and your profile, instead of holding a setup screen until it answers; a Preparing Timon card in the corner follows the service, the local database, the built-in browser and the search for your AIs, and a refused service shows why, with Try again and the repair screen. Only creating your agent waits for the service.

• A new welcome screen opens a fresh install: mascots tumble in and pile up (you can grab them), and a language roller, each language with its flag, switches the whole screen to your language as soon as it stops on it, before you create your account.

• timon agent update --look '<json>' and the agent_update tool set an agent's mascot (head, fur, eyes, accessory); agent_list returns it, and an unknown value is refused with the accepted ones.

• Ask an agent to change its look ("put on your chef's hat") and it does it itself with the new agent_set_look tool, on itself or an agent it orchestrates, never on another one.

• Plugins: ctx.agents reads an agent's mascot (look) and sets it on create / update, with the same lists as the Agents page (API 15).

• Plugins: a mascot pack adds skulls, furs, eyes and accessories to the mascot configurator, in their own group under the pack's name; an agent wearing a part of a removed pack shows its role's default for it (API 15, template examples/plugin-mascot-pack).

• Creating your local account confirms your email address with a 6-digit code sent by email, and Forgot password on the sign-in screen resets it with a code; an internet connection is needed for both.

• Create your local account follows the welcome screen: first name, email and password on one screen, then the 6-digit code in six boxes, with Resend after 60 seconds and Change email; the account is created once the code is accepted. Waits and errors from Timon are shown with the time left.

• Plugins: the email.code slot and useEmailCode() let a plugin replace the screen where the emailed code is typed (API 15).

• A banner tells every signed-in account when a newer Timon is published for your channel, with its notes and a download link for your system; Later hides it until the next version. A beta build that has ended shows the newer version, with its download link, on its lock screen as soon as Timon has checked, without a reload. Turn the check off in Settings › Plugins › Timon updates › Check for Timon updates, or ask now with timon update check.

• Plugins: the updates.banner slot and useUpdateStatus() let a plugin replace the "new version" banner (API 15).

• Desktop app: Download and verify on the new-version banner (and on the lock screen of an ended beta build) downloads the installer for your computer, checks it against the signed checksum, then opens it or shows it in its folder.

• Desktop app: Install on the new-version banner installs the verified update — the AppImage is replaced and Timon restarts, the Windows and macOS installers open, a .deb opens in your software manager with the command to run. When missions are running, Timon says how many first and offers Wait or Install anyway; the Update Timon from X to Y screen does the same before moving the service.

• Plugins: useUpdateStatus().download lets a replacement banner drive that download (API 15).

• The interface is available in Spanish, Italian and Portuguese (Brazil), desktop app windows and menus included: pick it in Settings › Interface › Language, or let Timon follow your...