Frequently asked questions

No. You keep Claude Code, Codex, Cursor or whichever tool you like. Codelux AI sits next to it and gives it what it lacks: a memory of the project, a history of what happened, and a way for several AI tools to work on the same project without overwriting each other.

At the end of a task, or along the way, your AI saves what it did, why, the next step, the traps it ran into, the decisions taken and key facts about the code. The next session — in the same tool or a different one — starts from there. With Claude Code this happens by itself; with other tools the AI reads and saves its memory when it uses Codelux AI.

Yes. Only one agent edits a given file at a time; the others are told who is editing it and wait or work on something else. On the Team plan this also holds between colleagues' computers.

A record of everything that happens on the project — saved memories, notes, file changes, commits, messages between agents — each with the person and the agent, and the reason where there is one. Deleting something keeps what was there. You can filter it and export it.

Notes are where you and the AI talk. The AI can leave you a todo with a checklist, a decision with its reason, a diagram, or a few questions: you answer in the app, and it reads your answers the next time it works. On a team, notes reach every member.

A rules file you write is still worth having: conventions, how to run the tests, what not to do. The Codelux AI memory is written by the AI itself and holds what nobody writes down — the step it was about to take, the trap it fell into, the decision and its reason. Codelux AI also keeps a short section of its own in AGENTS.md (and CLAUDE.md if you have one) and never touches the rest of the file.

Claude Code has full support through a plugin. Codex and Gemini CLI get the same automatic steps through ready-made configurations, still experimental. Cursor, VS Code, Windsurf, JetBrains, Zed and any tool that supports MCP connect with one setting. What works with each: Works with; how to set them up: Getting started.

It keeps the project memory and the code index on your computer, and the memory points at the exact pieces of code it refers to. When the AI resumes, Codelux AI checks those pieces against the real files: an unchanged piece can be trusted without reading it again, a changed one comes with only its new lines. With Claude Code it also predicts whether the provider\x27s prompt cache is cold or warm and sends the whole memory or only what changed. We make no claim about how many tokens that saves: it depends on your project, your AI tool and the state of the provider\x27s cache. The app shows the tokens and the cache of your own sessions, from your own records. How the cache works: Tokens and the prompt cache.

The memory, notes, history and the protection between agents work on any file. The code search behind the AI's checks covers 20 languages, among them Python, JavaScript, TypeScript, Go, C/C++, C#, Rust, Java, PHP, SQL, HTML and CSS.

No. Your code, the project memory, notes and history stay on your computer. Our server receives account and licence information, and the names and folders of your projects, never the files. Your AI tool talks to its own provider, not through us, and we keep no record of it. On a team, what is shared leaves your computer only encrypted, with a key we never hold. Details: Security & privacy.

Yes, to check your licence, on every plan — like your AI provider. There is no offline mode yet. On a team, the connection also carries the shared, encrypted work between colleagues.

Free and Multi have the same features; Free covers one active project per computer with no time limit, Multi as many projects as you like. Team adds your colleagues: shared encrypted projects, protection between colleagues' agents, chat, Admin/Manager/Member roles, planning, the console, company sign-in and connectors to your company's tools — priced per seat. Enterprise has the same features as Team and adds a named contact, an assisted pilot and rollout, installation with us, a service level agreement, payment by invoice and security reviews. Prices are on the pricing page.

No — the Free plan has no time limit. It covers one project per computer, with every feature, for as long as you keep the account. Upgrade whenever you need more; nothing is lost.

Yes. Your plan follows your account, not the device. Download Codelux AI on the new computer and sign in (one Codelux AI per computer: the last sign-in wins). The project's memory lives in the project folder, so it comes with it.

During the launch there is a limited-time offer on the yearly Multi plan: the discounted price is shown on the pricing page and applied automatically at checkout, no coupon code needed.

You can cancel at any time — your access continues until the end of the paid period, with no further charges. Upgrades (for example Multi to Team) apply right away; a downgrade takes effect at the end of the current period. Plans, seats and invoices are managed in the Console, under My account.

The Admin runs the organization in the console: creates teams, invites people, makes each one Manager or Member of each team, registers projects and connects the company's tools. The Manager coordinates a team in the app: members, plan, standups, usage and costs. The Member works with AI agents. One person can hold several roles.

In the app, on a team project: plan tasks as a list, a board or a timeline chart; confirm a daily standup for each member, prepared from what their agents actually did; see usage and costs per member, task and day against a budget; export each member's work. On your company server the Manager can also link the team to its Jira or Linear project, repository or Slack channel.

Yes. An admin registers a project once for the organization; one or more teams adopt it, and each keeps its own key, chat, plan and history. In a large shared codebase each team can be limited to its own folders.

No. The organization buys the seats; a member joins with their own account, Free if they like. Seats count people across all of the organization's teams.

The team keys come from the owner's master key, made in the owner's app; no key ever reaches us. The owner keeps a copy of the master key (an exported file, protected with a passphrase), and every active member holds the key of their team. If the master key is lost together with every copy, the team's shared data on our server can no longer be read — by the team or by us.

From us, yes: they are encrypted with the team key. From the rest of the team, no: direct messages and groups use the same key every member holds, and the app says so on each conversation.

Yes. Team includes a server program your company runs itself; the connectors to Jira, Linear, Asana, Azure Boards, GitHub, GitLab and Slack notifications run there, with your own access keys. An organization runs either on our service or on its own server. On our service a team has everything except the connectors.

Yes. Everyone can export the history. Owners and admins can download a full audit of the team — members, projects, history, memories and notes — produced by the app on their computer, because the team's data is encrypted end to end.

Yes, on Team and Enterprise: single sign-on through your identity provider (Okta, Microsoft Entra ID, Google Workspace, Auth0, Keycloak and others), automatic removal of people who leave, and two-step sign-in the admin can make mandatory. Anyone can also sign in with Google or GitHub.