ChatGPT on a keypad Nokia: what AIKON actually does

What AIKON is and where the AI runs

Developer Emir Karşıyakalı, known as emir on GitHub, created AIKON for Java ME-equipped Nokia Series 40 and Symbian S60 phones. Its name is Nokia backwards. The app began as Claude S40 and gained its new name after support for other providers was added.

A small Java client on the phone takes keyboard input, sends requests and displays replies. A separate Go server connects it to the APIs of Claude, OpenAI, Gemini or Grok. The language models run at their providers. This is cloud AI accessed from an old phone, rather than an offline ChatGPT installation.

One date matters: the story attracted attention in late October, but the latest release returned by GitHub during our check was v0.18.4, published on 4 October 2026. A news article's publication date is not the project's launch date.

Why opening ChatGPT in the old browser was not enough

The small screen is only part of the problem. The author's measurements show that the Nokia 6300 uses TLS 1.0, sends no SNI and has an outdated root certificate store. It can fail to establish a secure connection to modern services before a page even loads.

AIKON inserts a gateway between the phone and the AI. The gateway supports the phone's older connection requirements while using modern HTTPS with model providers. The phone needs a configured trusted certificate. This bridge makes the experiment possible; the phone's processor has not suddenly become more powerful.

When you ask for news or weather, a provider's search tool runs on the server side. The old Nokia browser is not involved. The result comes back through an interface designed for physical keys.

It does more than display a single reply

The documentation describes per-chat provider and model selection, conversation history, history search, pinned chats and paginated reading for long replies. There are three text sizes, light and dark themes, and prompt shortcuts. The server operator chooses which models are offered; a provider's menu entry does not guarantee access to every model it sells.

On compatible hardware, you can dictate up to 30 seconds. The server transcribes the recording and lets you review the text before sending it. You can also take or select a photo and ask about it. These are author-documented features; availability depends on the phone's Java APIs, server settings and the selected model's capabilities.

A useful touch is saving a reply as a TXT file to read without a connection. Suggested events or tasks can be added to the phone's calendar after confirmation. Offline access means reading saved material, not generating new answers.

Supported phones and Ukrainian language support

The author names two tested devices: the Nokia 6300 RM-217 running firmware V06.60 and the Nokia E63 with Symbian S60 3rd Edition FP1. WLAN operation is documented for the E63. The 6300 needs working mobile data. Check connectivity, access-point settings and network availability before buying anything.

Other Series 40 phones with CLDC 1.1 / MIDP 2.0 and a 240×320 screen may work, but the author does not list them as tested. The original Nokia 3310, which lacks Java, is unsuitable. A modern reissue sharing an old model name should not be assumed compatible either.

Ukrainian is absent from the eight listed menu languages. However, the author says replies follow the language of the prompt. These are separate issues: a Ukrainian model response does not provide a Ukrainian app interface. We have not verified Ukrainian input and font rendering on a particular firmware.

Free source code does not mean free conversations

AIKON uses the MIT licence, allowing use and study under its terms. Self-hosting still requires a server and an API key for at least one provider. The author's USD 4–6 monthly VPS estimate is a guideline, not a guaranteed offer or the total running cost.

Model requests are billed separately, as may be web searches, speech transcription and mobile data. Do not assume that a consumer chat subscription pays for API usage: check access and billing with your chosen provider. AIKON's setup guide explicitly calls for a paid-tier Gemini key.

Setup includes a mock mode with simulated replies and no model calls. It helps verify the connection but does not demonstrate real AI quality. Configure server limits and provider spending controls before enabling real requests.

How to try it: a realistic route to getting started

1. Check the model, Java support and internet connection. The two author-tested phones leave fewer unknowns. Do not buy an old handset solely because of a ChatGPT headline.
2. Read the project's SETUP.md and prepare a server. It needs Docker, a public IPv4 address and reachable TCP port 443. Ordinary static website hosting does not replace this gateway.
3. Download the JAR, JAD and SHA256SUMS from GitHub Releases on a computer. Transfer the app using a method in the guide: Bluetooth, USB, PC Suite or a web server the phone can reach. The E63 has separate installation caveats; follow the S60 section.
4. Configure the certificate, verify its fingerprint and run the connection test. Pair the phone with your server using the six-digit code, then check a mock reply. Do not ignore an untrusted-certificate warning.
5. Add the API key to the server, choose the models and limits, then enable real replies. Start with a short, non-sensitive prompt. If server administration is unfamiliar, this experiment will require technical help.

Nostalgia comes with trade-offs

The author explicitly identifies TLS 1.0 as weaker than modern protection. The connection is encrypted, but we would avoid banking details, work secrets and personal documents in this retro experiment. That is our assessment of a documented limitation, not a claim that AIKON has been breached.

API keys stay on the server and the phone receives its own revocable token. The documentation says ordinary chats remain on the server for 30 days after the last message, pinned chats persist longer, and setup details can be stored on the memory card. Revoke access if the phone or card is lost. The selected model provider also processes requests.

Why bother when a smartphone is easier?

A smartphone is more practical for most people. But AIKON illustrates a useful engineering idea: a limited device need not do all the work itself. A lightweight client, a readable interface and a properly designed gateway can connect it to a capable service.

There is a lesson for vibe coding: value often comes from adapting an existing technology to an awkward environment. Physical keys, legacy protocols, long replies and cost controls are the product, not minor details. Is it worth trying? For a compatible Nokia owner interested in retro computing, it is a compelling project. For everyday use without setup, simpler options exist.

Quick answers

Does ChatGPT work on the Nokia without internet?

No. The phone connects to a gateway, which calls a cloud model. Previously saved TXT replies can be read offline.

Is installing the JAR enough?

No. You also need a configured AIKON server, a trusted certificate, phone pairing and API access to a model. The ready-made app simplifies only part of the process.

Is this an official Nokia or ChatGPT app?

No. AIKON is an independent open-source project. Its repository explicitly disclaims affiliation with or endorsement by Nokia and the AI providers.

Primary sources and verification

Check the author’s current requirements and releases before installing: model support and instructions can change. These links lead to the project’s own sources.

• AIKON: repository and features
• Release v0.18.4, 4 October 2026
• SETUP: installation, server and connectivity
• ARCHITECTURE: phone, gateway and model APIs
• SECURITY: TLS, tokens and data retention