Import From Other AI Apps

Neotask Desktop can bring supported local setup and recent conversation history into Neotask without changing the source app's files. The import screen shows only apps for which it finds eligible local material on the current device. This detected-only behavior keeps unavailable or empty providers out of the picker.

Start An Import

Open Settings → Import. You can also choose Import agent during onboarding or from Add Agent.
Select one detected app.
Review the Tools & setup, Projects, and Chat sessions groups.
Choose whether to create an agent, add to an existing agent, or apply eligible shared setup globally. Company Settings keeps the import inside that company.
Run the import and review the result report, including anything skipped or requiring attention.

Neotask imports one provider at a time. It does not offer a folder picker or accept an arbitrary source root from the import screen.

Supported Local Sources

App	Local material used by the Desktop importer	Conversation destination
ChatGPT	Eligible local Desktop and Work sessions	Project-backed Work sessions go to Code; genuinely projectless local sessions go to Chat. Cloud-only ChatGPT history is not a local import source.
Claude Code	Eligible local setup, projects, and recent sessions	Code
Claude Cowork	Eligible local Cowork setup and conversations	Chat
Codex	Eligible Codex CLI setup, projects, and recent coding sessions	Code
Cursor	Eligible local setup, projects, and recent sessions	Code
Grok Build	Eligible Grok Build 1.0.5 setup and recent local sessions from an absolute `GROK_HOME`, or `~/.grok` by default	A verified Git repository or explicit source workspace goes to Code; an ordinary or projectless working directory goes to Chat.
Kimi Code	Current Kimi Code 0.38 data from an absolute `KIMI_CODE_HOME`, or `~/.kimi-code` by default, plus deduplicated eligible legacy data under `~/.kimi`	A repository or explicit Kimi workspace goes to Code; a genuinely projectless conversation goes to Chat.

An app does not appear merely because its software is installed. It appears only when Neotask detects at least one eligible item. Credential-only, cache-only, log-only, or otherwise non-importable state does not create a provider row.

What Can Be Imported

Available items depend on what the source app stores and what Neotask can map safely. Eligible items can include:

instructions, rules, and supported customization settings;
skills, commands, agents, and safe plugin components;
hooks and other executable setup, subject to the review rules below;
MCP server definitions and transferable MCP-specific credentials;
project associations; and
recent active session history, including original titles and dates and visible user, assistant, tool-call, and tool-result activity.

Session import is bounded to the most recent 30 days and up to 50 eligible sessions per provider. Oversized, malformed, changing-during-read, or out-of-scope files are skipped instead of being partially trusted.

Kimi Code current and legacy formats

For Kimi Code 0.38, Neotask recognizes the current session metadata and the main conversation wire, as well as the legacy workspace index and legacy session context layout. When equivalent current and legacy items overlap, the current format wins and the result is deduplicated.

Neotask reads active main-conversation history. Archived or deleted Kimi sessions are omitted before transcript reading. Visible parent orchestration, including a visible tool call and its result, stays in the parent transcript; private subordinate-agent wires are not read or flattened into that conversation.

Grok Build format

For Grok Build 1.0.5, Neotask reads a bounded local session summary and prefers the session's bounded updates stream. It uses bounded chat history only when the updates stream is unavailable. Hidden or subagent sessions and raw reasoning records are excluded. Detection is local and read-only; it does not query xAI for Grok history.

Code And Chat Routing

Tool use alone never decides whether a conversation belongs in Code. Neotask uses source-owned workspace information and verifies the local project boundary:

a verified repository or explicit source workspace is associated with the matching Neotask Code project; and
a genuinely projectless conversation is imported into Agent Chat.

This prevents a projectless conversation that happened to call a tool from being placed in an unrelated coding project. Project identities are stable on the device, so the same project can converge across supported coding providers without creating one duplicate project per provider.

Audit Trail And Provenance

Does imported state keep its audit trail?

Yes. Imported state preserves its source provenance, original timestamps, session/project associations, and visible user, assistant, and tool activity. Neotask also records the import in its own ledger. It does not copy the provider’s private telemetry, hidden reasoning, or internal administrative audit logs.

The ledger uses opaque, target-aware source identities to support retries and sync without placing raw local paths or secret values in public reports. It records import provenance and outcome; it is not a copy of the source provider's private operational logging system.

Executable Setup And Trust

An import is not permission to inherit another app's trust decisions. Neotask Safe Mode, approvals, project containment, and company boundaries remain authoritative.

Source folder, plugin, sandbox, shell, approval, and permission trust is not copied.
Unsupported or trust-affecting settings remain review information rather than silently changing Neotask policy.
Remote plugin installation metadata and executable project hooks remain review-only.
Kimi plugin hooks that depend on Kimi-specific working-directory or environment behavior remain review-only.
Grok project or plugin executable components are not activated when the source folder is not trusted. A home-level disabled-MCP decision continues to disable the same server in project and plugin sources.

Review the result report before enabling or recreating any item that was kept in review-only state.

MCP Definitions And Credentials

MCP import has separate definition, credential, materialization, connection, and verification steps. Neotask can transfer supported static credential values found in an MCP definition, such as environment or header values, and can adopt an MCP-specific OAuth grant only when the source exposes a portable record bound to the exact server name and canonical URL.

Portability is provider-specific:

Kimi Code 0.38 and Grok Build 1.0.5 have supported exact-key MCP credential records that Neotask can validate.
An access token is not treated as universally portable. Refresh is available only when bounded, usable token-endpoint and client metadata is present.
Source-app account login, unrelated grants, OS-keychain-only material, device-bound credentials, opaque broker state, and malformed or mismatched OAuth records are not copied.
If a grant is unavailable, rejected, expired, or non-portable, reconnect the MCP server through Neotask's fresh local authorization flow.

Imported MCP credentials are target-scoped and encrypted at rest with AES-256-GCM. Secret values and secret-derived hashes do not enter renderer payloads, the Site, import reports, screenshots, persisted public config, or logs. A bearer header is constructed only in memory for the bound connection. Neotask reports an MCP import as successful only after the definition is materialized and the connection path is checked; a missing executable or required fresh login appears as an item needing attention.

Manual Import And Autosync

A manual import applies the items you reviewed for one provider. After a successful personal import, Keep imports in sync can periodically recheck an enabled provider and apply safe, idempotent updates to its existing target. Use Check again when you want an immediate re-scan.

Autosync does not activate new or changed MCP definitions, rotate MCP credentials, or bypass review for executable or trust-affecting content. MCP changes require a new manual review and import. Company-scoped imports follow the controls shown in Company Settings.

Running the same unchanged import again does not duplicate agents, projects, sessions, messages, or setup. If an imported transcript was edited locally, Neotask does not overwrite that work. Append-only source changes can extend an imported transcript when its existing content remains an exact untouched prefix. If a Kimi or Grok source rewinds or branches, Neotask may replace only unmodified imported source rows that Neotask still owns. A local edit or an ownership or authority mismatch is reported as a conflict that needs review.

Paths, Custom Homes, And Source Safety

Neotask uses the platform's native path rules on macOS, Windows, and Linux. A custom KIMI_CODE_HOME or GROK_HOME must be absolute. Relative homes, filesystem roots, broad home-directory project guesses, unsafe links, protected paths, and files that resolve outside their approved source boundary are rejected or skipped.

If a custom Kimi or Grok home is nested inside a project, Neotask excludes that runtime-data tree from project hydration. Detection is read-only and does not modify the source app's home or session files.

Verify An Import

After the result report completes:

Open Code and confirm each repository or explicit workspace session is under the expected project.
Open Chat and confirm genuinely projectless conversations appear there.
Open a conversation and check its title, original date, message order, and visible tool activity.
Review all needs attention, review-only, and skipped rows.
For an imported MCP server, confirm its connection status and run a harmless read-only tool action. If authentication is requested, complete a fresh Neotask connection instead of copying credentials manually.
Run the same unchanged import once more when you need an idempotency check; the report should show existing items rather than create duplicates.

Troubleshooting

The provider is not listed

Confirm the source app has eligible local setup or a recent active session on this device. Installation alone is not enough.
For Kimi, confirm KIMI_CODE_HOME is an absolute path when set, or that the current or legacy default home contains eligible material.
For Grok Build, confirm GROK_HOME is absolute when set and contains eligible Grok Build 1.0.5 material.
Credential-only, archived-only, deleted-only, hidden-only, cache-only, or log-only homes are intentionally not shown.
Select Check again after the source app has finished writing its files.

A session went to Chat instead of Code

Neotask did not find a verified repository or explicit source workspace for that session. Open the source project once so the provider records its workspace association, then run a manual import again. An arbitrary working directory or tool call is not enough to create a Code project.

An item was skipped or needs review

Open the result row for the specific reason. Common causes include an archived or hidden session, an old session outside the import window, an unsafe or changing path, an oversized file, an untrusted executable component, a local edit conflict, a missing MCP executable, or OAuth that requires fresh authorization.

The MCP server imported but is not connected

Check that the server executable or URL is available, then use Reconnect or the offered authorization action. Neotask does not reuse provider-account login or a credential that cannot be proven portable for that exact server.