LinX

Let AI hold onto the thread of work on your desktop

LinX brings chat, memory, files, and follow-up into one desktop interface. It is not another chat shell. It is the entry point where AI can begin carrying work forward over time.

Desktop-firstChat and memoryFilesFollow-up
LinX App

secretary / continuity / active workline

never stops continue by default
Worklines Today
Search active threads
release-train

Tests passed, continue checking DEV

09:42
Integration

Queued now, return result on the same workline

09:28
Secrets inbox

render_api_token waiting for approval

09:18
SIT regression

Promote only after acceptance closes

yesterday

Current Thread

release-train · tests -> DEV -> integration
Codex runtime · 24m
continue by defaultask on boundary
This workline has 1 pending ask

Until approval lands, runtime stays in xpod instead of bouncing back into chat to ask the same question again.

LinX

Unit tests passed. I continued to DEV health checks instead of asking you to confirm the obvious next step.

Runtime

DEV is healthy, integration is queued, and the result will return on the same line of work.

Boundary

The next step needs a wider render_api_token scope. The request is now routed to xpod for approval.

Continue this workline…

What LinX reconnects first

What breaks is not only a conversation. It is the history of a piece of work. LinX brings the information you switch between most often back into one surface so AI can see the active thread.

Entry

Chat

Keep conversation as the main entry point without trapping work inside single prompts.

Core

Memory

Keep people, projects, and past decisions on the same working thread.

Material

Files

Keep materials, attachments, and structured data close to the task surface.

Why it differs from a normal AI client

Most AI clients optimize for asking again. LinX cares about whether the same piece of work can keep moving without being restarted over and over.

  • Handle conversation, material, and follow-up in one place
  • Stop reintroducing the same background every time
  • Keep room to connect your own runtime and more data later

Who should start here

If you already rely on AI but keep re-uploading files, re-explaining background, and re-stating the next step, LinX is the shortest path in.

Personal

Individuals

For people who want AI to remember the thread instead of reopening from zero every day.

Team

Small teams

For teams that want product value first, then deeper control over runtime and data.

Next step

Start with LinX

If your first question is “how do I start using this now?”, LinX is the answer.