Changelog

DeepSeek V4.1 Flash now powers the DeepSeek Flash entry in the agent picker.

If you already selected DeepSeek Flash, new chats use the V4.1 generation when OpenRouter can serve it. Auto also uses DeepSeek V4.1 Flash first. DeepSeek V4 Pro is unchanged.

The Accept button on the public express quotation page now uses your workspace accent color.

Customers who open a quotation link see the same accent as the rest of your workspace, instead of the default orange. Set the color under Administration → Workspace Settings → Appearance.

Turning Navigation animations off now stops only the left-right page slide.

Other motion in the app keeps playing. That includes opening a group in the left menu, and animations inside a page.

The agent model picker now includes GLM 5.3 Flash and GLM 5.3.

Flash is the fast, low-cost option and can read images. GLM 5.3 is the larger reasoning model for longer, tool-heavy work.

GLM 5.2 stays available under Show more models if you still want it.

The Public API now enforces a shared request ceiling so one address or one token cannot flood the service. Each client IP may send 3000 requests per minute. Each access token or signed-in session may send 1200 requests per minute.

When a caller exceeds the ceiling, the API returns HTTP 429. The response includes Retry-After and X-RateLimit-Limit / X-RateLimit-Remaining so clients can wait and retry. Normal interactive use and typical integrations stay well below these limits.

Agent clients that support Skills over MCP can now import Leadtime’s setup and workspace guides from the existing Leadtime connection. Cursor and Codex plugin packages also use the portable Agent Plugins format, while older clients continue to receive the same guides from their normal plugin package.

Moving between screens is instant by default. The left-right page slide is now a setting, not a fixed behavior.

Turn it on for the whole workspace under Administration → Workspace Settings → Appearance. In My Profile → Account, you can use the workspace default, set it to Enabled, or set it to Disabled for yourself.

When you open a screen that still has to load, Leadtime no longer keeps the previous page on screen with a thin bar at the top.

The old page clears. A spinner sits in the center of the empty page. When the new screen is ready, it fades in.

A ticket can now wait on another ticket. Open Relationships in the sidebar to set a parent, add a blocker, or mark this ticket as blocking someone else.

The Blocked badge stays on while any blocker is still New, In progress, Feedback, or Backlog. It clears when every blocker is Resolved or Closed. Relationships keeps the links and switches the heading to Was blocked by. You can still change status and close the ticket. Duplicate does not copy blocking links.

Subtasks now live under the description instead of the right sidebar. You can create a new subtask or connect an existing task from the same place.

When a task already has children, they show as a list with number, icon, title, type, priority, and status. On small screens, create and connect sit in the more menu. Each row has a more menu to unlink, close, reopen, or delete the child. Child tasks still show their parent in the sidebar and cannot nest further.

If an agent already has Leadtime open in a tab, it can now use your logged-in session there. ChatGPT desktop and Codex in the browser can list workspace actions, open help, follow Leadtime URLs, switch theme or language, and move around the page you are looking at.

You do not add another MCP connector for this. The existing /api/mcp connector still works for agents that connect from outside the app. Direct API credentials stay on that connector and are not available as site tools.

You can now publish project documentation to organization members instead of sharing every page by default.

Set an organization default under Organizations → Settings → Guest access: Hidden, All pages, or Selected pages. Existing organizations start as Hidden. Each project can keep that default or override it on the new Projects → Settings → Guest access page. The project guest-access switch still decides whether members can open the project at all.

In Selected pages, mark individual pages as visible to guests, or make all pages in a folder visible or hidden. Internal users keep the complete tree. Organization members never see page History. The built-in Guest role stays read-only. A custom guest role can edit only pages that are already visible.

Organization Guest access settings now include a Welcome banner and a Guest accent color.

You can keep the localized default welcome text, write one custom message for every language, or replace the banner with an image. The settings page shows a live preview. Custom messages can include the guest’s name, organization, and your workspace company.

The optional organization color applies to guests who have not picked a personal color. A guest’s own color still wins. Otherwise Leadtime uses the organization color, then the workspace color.

To use Leadtime from Cursor, add the Leadtime GitHub repository as a custom marketplace. In Cursor Settings, open Plugins, click + Add Marketplace, choose Import from GitHub, then install Leadtime and connect your workspace.

Guest users now open Home after they sign in. The page explains why they are in Leadtime and lists the projects shared with their organization.

Each project card shows guest-visible open tasks, tasks assigned to the guest, forms to complete, and documentation pages. A clear empty state appears when no project is shared. Configurable dashboards remain available to workspace users only.

Chat with agents is now a workspace permission. Staff and other internal roles keep it.

The built-in Guest role does not. Standard guests no longer see the Agents page, the agent panel, or the toolbar button and keyboard shortcut.

If some guests should still chat with agents, turn Chat with agents on for a custom guest role.

When you sign in as a guest, Projects in the top navigation still opens the projects list. Hover the item (or open it in the mobile menu) to see the projects you can access and jump straight to one of them. The list stays available while projects load, and the menu grows with the project name.

Workspace appearance now includes Light blue next to the existing color schemes.

Pick it under Administration → Workspace Settings → Appearance. The accent applies to navigation, buttons, and active states for everyone in the workspace. You can also set it as your personal color in profile settings.

You can now open Fullscreen mode from any Leadtime editor. Type / and search for Fullscreen mode or Zen mode, or press Ctrl+Alt+Z (⌘⌥Z on Mac). The editor fills a calm overlay so you can write without the rest of the app in the way, then return with Escape or the close button. Your text stays in the original field.

Guest access now stays within the customer collaboration permissions designed for guests, including when you use custom roles or role inheritance. New workspace permissions also remain unavailable to guest roles until they have been reviewed for guest-safe data access.

When a custom guest role is deleted, organization members now return to the standard Guest role instead of receiving a staff role.

An open documentation page or folder now shows its complete hierarchy below the Documentation header. Select an earlier folder in the path to open it.

The documentation tree stays visible on more laptop screens. On narrower screens, clearer tree and information icons identify the two panel controls, and the navigation drawer now has a visible title.

The documentation home now shows the complete page and folder contents. Folder views also use a folder icon and align their title with the child list.

When you sign in as a guest, the sparkle Agent button now sits next to your account menu, just like it does for staff. You can open the agent panel from any page, not only from Agents.

Project documentation now keeps New page and New folder as equal-width actions that fill the tree rail under search. New page is the filled primary action. New folder is a simple outline button. A divider separates those controls from the pages and folders. Tree rows use the same spacing as the Components tree, so a selected row and a hovered row do not touch.

Delete now lives in details Actions, not in the tree menu. Folders also open a details panel with creator, last editor, dates, and Delete folder. A new page or folder shows its title immediately so you can start typing while Leadtime saves in the background. The cloud icon in the header stays quiet while a page connects, and folders do not show that icon.

When you sign in as a guest, Projects no longer shows staff-only tabs such as Internal projects or value-group views.

You still get the lists that apply to your organization, including All projects, Favorites, Single, Continuous, and Archived projects. Those type lists skip the word “external,” because guests do not see internal work. Columns and filters for organization, guest access, and value group stay hidden, so the grid matches what you can actually open.

DeepSeek V4 Pro in the agent picker now requests DeepSeek’s latest general-availability release.

If you already selected DeepSeek V4 Pro, new chats use that updated model when OpenRouter can serve it. Auto still prefers DeepSeek V4 Flash and keeps V4 Pro as a fallback.

The agent model picker now includes Gemini 3.7 Flash, Google’s latest fast model for agent work, coding, and multi-step reasoning.

Gemini 3 Flash Preview stays available under Show more models if you still want it.

Organization settings now include a Guest access page. You can explain guest users for that organization and upload a custom logo.

When a member of that organization signs in, the guest header shows this logo instead of the Leadtime logo or the workspace logo. If you do not upload one, guests keep the usual workspace branding.

You can now favorite models in the agent model picker.

Hover a model and click the star to pin it under Favorites, just below Auto. Your favorites are saved for you in each workspace, so the models you reach for most stay easy to find.

The agent model picker now includes Grok 4.6, xAI’s latest frontier model for coding, knowledge work, and long-running agent tasks.

Grok 4.3 stays available under Show more models if you still want it.

Managers with the new Log in as organization members permission can open a real guest session from an organization member’s detail page.

Use Log in as member from the member detail menu to check guest roles and what the member can see. Leadtime signs you in as that member, opens the dashboard, and shows an alert that explains how to switch back from the account menu.

Cursor, Claude, Codex, and other MCP clients keep using the same Leadtime MCP URL. Newer clients that speak the 2026 MCP protocol can connect there too, without a second endpoint or a client upgrade on your side.

When you talk to the Leadtime agent in Slack, you can now see it work. A live card appears in the thread with a short status and each tool the agent uses, so you can follow progress instead of waiting on a blank reply.

The final answer still arrives as a normal Slack message when the work is done.

Agents can now use the complete project documentation API: discover the ordered tree, search one project, read only relevant HTML blocks, create and move pages, create folders, and rename either kind of node. n8n and Zapier expose a focused set of the same hierarchy, page, checkpoint, and tag-catalog operations for common workflow automation. Pages can be tagged, and folder-tree deletion is protected by a current preview. Current server capabilities tell automations which actions are available.

Automations can update exact HTML fragments atomically or replace a complete page with generation guards and a stable command identity. Open editors receive those changes immediately. Supported video embeds survive create, replacement, and focused edits, while invalid embeds leave the page unchanged.

Checkpoint operations list safe page-history metadata, preview one earlier title, content, and tag set, and restore it without overwriting newer work. Cursor metadata remains available in n8n and Zapier for continued checkpoint reads. PDF export is available through the same Public API.

Project documentation now combines an ordered page-and-folder tree, the open page, and its details in one responsive workspace. Create empty pages and nested folders in place, drag or use the keyboard to reorganize them, and review exact deletion counts before removing a page or folder tree. Everyone with project access can read; the Manage project documentation permission controls changes.

Documentation managers can edit together with live text, collaborator cursors, and personal undo. One quiet header indicator covers title, tag, and content saving. If a connection or metadata save fails, Leadtime preserves recoverable work, explains conflicts, and warns only while changes are genuinely at risk.

Page history keeps complete title, content, and tag checkpoints. Preview or restore an earlier page without losing the current version. On smaller screens, the page stays central while navigation and details open in focused panels; unsaved work, expanded folders, tags, and history remain in place.

Project documentation changes now appear under Administration → Documentation activity for people with the View workspace audit history permission. Each entry identifies the editor, page, and access source. It also shows the time range, changed fields, title and tag boundaries, and a compact content activity count. Page links follow normal project access.

Leadtime keeps collaborators and access sources separate, even when people alternate rapid changes. It groups each person’s activity into one useful entry. A pause closes the current period. Continuous editing starts a new entry after ten minutes. Content activity stays compact, while version checkpoints remain available for restoration.

You can now export one project documentation page, one folder with all nested pages, or the complete documentation tree as PDF.

Start a page or complete-project export from the Documentation header. Select a folder to find its export in the folder actions menu. Every project reader can use these actions, and Leadtime prevents a second request for the same export while it is being prepared.

Folder and project exports follow your inherited project document settings for the title page, table of contents, and heading numbering. Pages follow the saved tree order, each page starts on a new PDF page, and the table of contents shows its physical page number.

Every export now uses your workspace document font, logo, and company identity, with a consistent branded header and a page / total pages footer. Leadtime shows preparation and download progress, and reuses an unchanged export so repeated downloads finish faster. Changes to content, settings, fonts, branding, or embedded images prepare a fresh file.

Leadtime Agent can now inspect attached images with every available chat model. This includes text-focused models such as DeepSeek Flash.

Large images are reduced to a suitable size before inspection. The agent keeps readable text, layout, and visual details available for its answer.

The agent can also request a closer inspection of specific details. This helps with small text, colors, chart values, or one part of a screenshot.

Leadtime Agent can now optimize older conversation context during long-running work, preserving important decisions, completed actions, remaining work, and verification evidence while making room to continue.

When this happens, the activity timeline shows that the conversation context is being optimized. The agent then resumes the same task, including work that continues across several tool calls, without requiring you to repeat earlier information.

Leadtime Agent now builds a new workspace progressively instead of collecting a long questionnaire before getting started. Share company details, staff lists, customer exports, current projects, tickets, or other source files, and the agent brings in each usable part as soon as it has enough business information.

After each step, the agent opens one relevant Leadtime page, explains what was created and how that area works, and asks the next useful question. It can preserve information for later steps, create safe records first and enrich their access or relationships later, and help map exports from the tools your company used before Leadtime.

When login-enabled colleagues have the access and real work they need, the agent lets you know that the workspace is ready and sends their invitations. Your own guided tour continues afterward with the dashboards, administration, and commercial workflows relevant to a workspace owner.

The agent model picker now includes GPT-5.6 Luna, Terra, and Sol, Claude Opus 5, and Kimi K3.

When a selected model provides reasoning summaries, its Thinking steps now appear in the conversation activity alongside tool calls and results.

Older model generations stay available without crowding the everyday list. Select Show more models at the bottom of the picker whenever you need them. If an older model is already selected, it remains visible in the collapsed list.

The Leadtime team can now use an AI writing assistant while replying to Support conversations. It can use the conversation and attachment details to create or improve a draft, and the team member can accept, decline, retry, continue, or stop the suggestion.

The assistant only writes in the reply editor. It cannot send a message, change the conversation, or act in your workspace; a Leadtime team member must still select Send explicitly.

You can now contact the Leadtime team through private Support conversations without leaving your workspace. Start a conversation from the toolbar or Support page, include screenshots and files, and follow replies through clear unread indicators.

These native Support conversations replace the previous third-party feedback widget, so support stays inside Leadtime.

Browser-created conversations safely include useful page, browser, console, and network context so the team can investigate with fewer follow-up questions. Request and response bodies, headers, and URL query values aren’t included. Replies show the team member’s name and avatar, and the Leadtime team can also start a private conversation when they need to reach you.

Conversations keep their full history after they are closed. Sending another message automatically reopens the conversation, so you can continue the same topic instead of starting over. The same acting-user workflow is also available through the Public API for integrations.

Leadtime Agent can offer to create a Support conversation when a product problem remains unresolved. It asks for your approval first, avoids duplicate conversations, and shows a live card that opens the full conversation after creating or updating it.

Leadtime Agent can now handle requests such as closing every resolved ticket in a project as one controlled batch. Before changing anything, the agent resolves the exact filters, custom statuses, and affected records so similarly named statuses or broader result sets don’t get changed accidentally.

Batch runs track every affected record, surface partial failures clearly, and verify the final state before reporting completion.

Help buttons now open the relevant documentation in a focused window inside Leadtime. You can read instructions, view images and videos, and close the article without losing your place in the application.

Search, agent guidance, and integrations use the same current documentation, so links and Read more actions lead to consistent articles in your selected language.

The Leadtime Agent can now search documentation in either German or English without choosing a source language first. It reads related articles together, understands where each page sits in the help center, and can fall back to the available translation while still replying in your conversation language.

OpenClaw and Hermes setup now recommends the coding-agent prompt first, with the manual terminal command available separately when you need it. Manual commands clearly mark the connector URL and agent ID values you must replace before running them.

When an external runtime finishes setup, an open Leadtime settings page refreshes immediately with the saved connection details. This prevents an older form value from overwriting the webhook URL returned by the installer.

Leadtime now has a dedicated public documentation site. You can browse guides in English or German, search by meaning as well as keywords, and ask questions directly from the site.

Every article is also available as plain Markdown, making the same guidance easy to use from AI tools and other integrations. If a German translation isn’t available yet, you’ll see the English article with a clear fallback notice instead of reaching a dead end.

Creating a workspace now starts with one clear details form followed by email confirmation. Leadtime generates the workspace address automatically, so you can move from registration to setup with less back-and-forth.

We also strengthened verification and retry handling. Interrupted signups can recover cleanly, and billing setup only begins after the email address has been confirmed.

You can now mark an employee’s employment mode as Part-time. The option is available when editing employees, filtering contacts, importing employee data, and working through the public API.

The setting is a clear classification rather than a scheduling shortcut: it won’t change contracted hours, capacity, or availability automatically.

Leadtime Agent can now guide a new workspace through setup in a focused conversation. It adapts to what you’ve already configured, helps bring in real company data, and explains the next useful step without forcing everyone through the same checklist.

The agent can show relevant help and videos, open the right Leadtime screen, and keep setup progress in the conversation. Invitations remain under your control until the workspace is ready.

Unread indicators now show which agent conversations have new replies or activity, so you can return to the chats that need attention without opening every one.

Longer runs are easier to follow too. Related activity stays grouped, attachments remain available, and conversation history is preserved while work continues in the background.

When an agent works from a task, it can now create a time entry for that task and read the existing time-booking activity. This keeps agent work in the same project reporting flow as the rest of the team instead of leaving it as invisible effort.

The resulting booking is attached to the task and remains visible for review like any other recorded time.

Leadtime Agent can now carry out safe interface actions on your behalf. It can open a task, move to the relevant workspace page, or switch language and theme when those actions help complete your request.

Tasks open in their normal modal, so you can inspect the real item and return to the conversation without losing context.

Automations can now react to messages from a connected Slack workspace. Choose the Slack message trigger, narrow it to the channels and message conditions that matter, and let the rest of the automation continue in Leadtime.

This makes it possible to turn the conversations your team already has into consistent follow-up work without copying each message by hand.

You can now speak a prompt instead of typing it. Start recording from the agent composer, then send the transcription immediately or keep the text in the editor to review and refine first.

The recording view includes a live waveform and a clear cancel path, making voice input practical for longer requests while keeping you in control of what is sent.

Agent conversations now have a dedicated full-page workspace with a persistent history. Pin the chats you return to often, rename or remove old conversations, and keep the most useful work at the top of the list.

Agents can also return generated files directly in the conversation. Reports, notes, and other artifacts appear as downloadable attachments instead of leaving you to find them elsewhere.

You can now create custom agents directly in Leadtime. Give each agent a purpose, choose its workspace skills, connect the tools it needs, and use its own identity across chat, Slack, tasks, and automations.

Connection problems are shown clearly instead of being silently ignored, making it easier to understand when an agent needs attention before it can complete its work.

Leadtime Agent can now stay in a floating panel while you move around the workspace. Switch between the sidebar and floating view depending on the task, and Leadtime remembers your preference for that workspace.

When the agent needs a decision, it can ask a clear follow-up question with single-choice, multiple-choice, or free-text answers. The conversation pauses safely until you respond, so longer work can continue with the right context instead of guessing.

Employee profiles now include a Statistics tab with a six-month view of current work and capacity, recent value-category breakdowns, and mood distribution when attendance features are enabled.

When you need more detail, the page links into Staff and Goal Insights while respecting the viewer’s existing permissions.

The workspace dashboard has been refreshed to make important information easier to scan. Project, staff, workload, turnover, and goal insights now share a more consistent visual language, with clearer chart labels and supporting context.

Dashboard widgets, page headers, navigation, and grids also adapt more cleanly across screen sizes, so the same overview remains useful on a smaller display.

Editing task descriptions and comments is now smoother. Linked items in the entity picker respond reliably to pointer selection, while comment actions are available from a compact side menu where you need them.

Undo also works correctly after wrapping or unwrapping content, making it safer to restructure longer descriptions without losing your previous state.