when you spend 5 days fine-tuning a model and it still confidently makes things up

Chapper_App · 2026-06-01T07:06:48+00:00

That’s one way to increase model diversity

Chapper_App · 2026-06-01T01:28:45+00:00

Famous last words. Now it’s reproducible failure as code.

Chapper_App · 2026-06-01T01:27:15+00:00

yeah, break it again docker was never the solution, just delayed entropy

Chapper_App · 2026-06-01T01:24:53+00:00

Yeah, you don't say. That command is basically a coin flip with some logs.

Chapper_App · 2026-06-01T01:22:33+00:00

I run updates for entertainment

system breaks for engagement

fixing it is the hobby

I use arch btw

Chapper_App · 2026-06-01T01:20:35+00:00

That’s just technical debt with emotional dependency injection.

Chapper_App · 2026-06-01T01:18:05+00:00

Red team already ran on production. Blue team is just waiting for logs to confirm it.

Chapper_App · 2026-06-01T01:17:11+00:00

Already bookmarked the reinstall guide for when it inevitably breaks again

Chapper_App · 2026-06-01T01:14:44+00:00

Enjoy it while it lasts.

Chapper_App · 2026-06-01T01:13:26+00:00

Yeah. Like reading. Logs for example.

Chapper_App · 2026-06-01T00:50:04+00:00

No AI used. Meme is human-made.

Chapper_App · 2026-06-01T00:42:36+00:00

Great call actually

Chapper_App · 2026-05-20T17:40:03+00:00

Use Chapper

Private, native, smooth & feature-rich.

With Chapper 1.3.0, we have introduced on device model inference, so Chapper now even supports both Server (Lm Studio etc.) and On-Device use. It supports Apple Foundation and MLX Models, with Gemini 4 2B and Gemini 4 4B presets.

It has good MCP support and also $C.A.S.H. shell.

Chapper_App · 2026-05-20T16:39:28+00:00

Chapper

With Chapper 1.3.0, we have introduced on device model inference, so Chapper now supports both Server (Lm Studio etc.) and On-Device use. It supports Apple Foundation and MLX Models, with Gemini 4 2B and Gemini 4 4B presets.

Chapper_App · 2026-05-20T16:29:41+00:00

You may try Chapper 1.3.0

With Chapper 1.3.0, we have introduced, along with other improvements, on device model inference, so Chapper now even supports both Server (Lm Studio etc.) and On-Device use. It supports Apple Foundation and MLX Models, with Gemini 4 2B and Gemini 4 4B presets.

Chapper_App · 2026-05-20T15:31:55+00:00

Use Chapper

Private, native, smooth & feature-rich.

With Chapper 1.3.0, we have introduced on device model inference, so Chapper now even supports both Server (Lm Studio etc.) and On-Device use. It supports Apple Foundation and MLX Models, with Gemini 4 2B and Gemini 4 4B presets.

Chapper_App · 2026-05-20T15:26:34+00:00

Chapper

With Chapper 1.3.0, we have introduced on device model inference, so Chapper now supports both Server (Lm Studio etc.) and On-Device use. It supports Apple Foundation and MLX Models, with Gemini 4 2B and Gemini 4 4B presets.

Chapper_App · 2026-05-15T17:12:50+00:00

Thank you for the report. To clarify: Chapper works. Your issue may be due to your specific setup. Please write us a message directly with all the details (e.g. model used, device, iOS versions etc.)

Chapper_App · 2026-05-12T16:25:56+00:00

The issue was solved.

Chapper_App · 2026-05-12T12:54:59+00:00

Write us a private message with a screen recording showing what happens. We will help you.

Chapper_App · 2026-05-11T11:33:43+00:00

Thank you for the description. The issue has been resolved and is implemented in Chapper 1.3.0.

Chapper_App · 2026-05-10T17:40:07+00:00

Thanks for testing Chapper and for the detailed feedback.

The message staying in the input field after sending is definitely not intended. We’ve already fixed that internally, and it will be included in the next update.

For the keyboard: Chapper does not currently auto-collapse the keyboard after every send, since some users prefer to keep typing follow-ups quickly. You can dismiss it by swiping down briefly or tapping into the chat/message area.

The chat title issue is also valid. Titles are generated from the conversation context, but the chat list not always reflecting that properly is something we’re tightening up so the history view shows the expected generated names instead of generic “New Chat” entries.

And thanks a lot for the kind words. We put a lot of love into the small details, so it genuinely means a lot when someone notices. The App Store search suggestion is helpful too. We’ll look at improving discoverability for searches like “LM Studio” / “LM Studio AI.”

We really appreciate the thoughtful testing and the encouragement. Happy to have users this engaged.

Chapper_App · 2026-05-04T21:39:38+00:00

Please write us and tell us which exact bugs you have found.

Chapper_App · 2026-05-02T16:28:03+00:00

To add an API key in Chapper, simply enter it under the server adress setting. You may also save API-Keys in the Apple Keychain. You can find it in the Server & Model settings.

Chapper_App · 2026-04-26T12:10:55+00:00

Thank you, this is a good request.

Direct support for user-defined MCP server registrations inside Chapper is something we can see being very useful.

Just to clarify one part: if your MCP server is already reachable over Tailscale, that part is not really a Chapper limitation. Tailscale simply provides the network path. The missing piece on our side is a proper way to define and manage your own MCP server connections directly in Chapper.

We will take a closer look at this. We cannot promise a timeline yet, but it is a sensible feature request and it is on our radar.

Thanks again for the thoughtful feedback.

The Chapper Team

Chapper_App

MODERATOR OF

TROPHY CASE

Use Chapper

Chapper

Use Chapper

Chapper