Known limitations

The current gaps in LinkCode worth knowing about before you rely on a feature that isn't there yet.

This page is the single place LinkCode's docs collect known gaps. Other pages link here instead of repeating this list.

Prompts and attachments

Images and other files pasted into a prompt are not forwarded to any agent yet. The paste appears in the composer, but the agent never sees it.
The @-mention picker and the attach button are visible in the composer but not functional yet.

Thread controls

Editing a message you've already sent, forking a thread, checkpoints, and queueing a message while a turn is in progress are not available yet.

Connecting your own tools

Attaching your own MCP servers to a thread is not available yet — no agent currently forwards MCP configuration through to its underlying SDK.

Agent-specific gaps

Codex runs every thread autonomously today (no approval prompts, workspace-write sandbox) and currently overrides a stricter personal ~/.codex/config.toml if you have one — a real gap if you rely on your own Codex sandbox settings outside LinkCode.

In development
A fix is in development to stop silently overriding your config.toml. It will not add a Claude-Code-style approval menu — Codex's SDK has no callback for one.
OpenCode and Pi threads cannot be resumed once stopped; starting a new one starts fresh. See the agents overview for what each agent supports.

The built-in terminal does not work in the packaged desktop build yet — the PTY sidecar it depends on isn't bundled with releases. It works if you're running the host (the LinkCode daemon) from source with the sidecar built and configured. See panels and troubleshooting.

Remote access

In development

Reaching your host from a browser or phone through LinkCode Cloud is in development. Today, desktop is the only supported client.

Platforms