I tried out Cluade AI

Q & A - getting started with Tinderbox
1

Dear ALL!!
The hot weather in Japan has become a little more autumnal.
How are you getting on ?
Here is a report on the use of new AI.
I’m experimenting with Claude on Tinderbox 11.
Even using the free version with Claude ver.0.13.37
They did the note creation to Tinderbox 11.
Search for the contents of the 2025 Moyse.tbx you created, and
Are there any contradictions in the content written?
“Let’s take a look at the list of notes to see how it is structured.”
When running Claude, the note name is not recognized and the name is changed.
It does not recognize the French string Époque with an axon.
The answer was given, so in future analysis, French-style, which is cited in the context,
Perhaps the German umlaut could be a problem.
For now, we have improved the name to a simple one as above. Claude has recognized the Tinderbox11 note. It seems that when searching using Claude, they were searching except for [.tbx], which has the extension.
When you chat with other LLM (LM Studio & gemma-3-27b or mistral-3.2-24b), only the answers that are convenient for the person asking questions will come up. (The answer was that the program was programmed in a setting that gave a convenient answer and had no objections.)

The answer to this Claude question is
“There seemed to be a problem, so I tried doing something else.”
The following suggestions were presented and implemented:
—(Quote)
But there were limits:
The comparison table shows the correspondence of concepts, but as stated that “detailed correspondence analysis is required,” the specific philosophical content development was insufficient. So, I:

Deepen each correspondence philosophically
Added linkages to other related concepts (Proust, Deleuze, Hugo, etc.)
Specific relations with musical practice

This is what I did.
This means that this comparison served as a starting point, and from there it developed into a more detailed and comprehensive analysis.
Was this usage appropriate? Or did you want a different approach?
——(Quote end)
Claude’s point has revealed that there are some parts that were “lack of my work,” so is it possible to use it usefully?
Whether or not the proposed work from Claude will be adopted is
I can just make my own judgment, so can I take a step forward from the previous trial and error work on gemma-3-27b and mistral-3.2-24b? I think so.

The problems and questions
Since it is written in utf-8, there is no problem with recognizing it.
Claude responded, but

Q01: The “axan” type used in French, German, etc.
Anyone encountering the problem? Is there none?
Q02: I’m still able to access one note,
Is there a possibility that it will be accessible through multiple notes in the future?

Yours, WAKAMATSU

2

By ‘axon’ (or later ‘axan’), I think this refers to an accent, or diacritical mark. In the quote above the word ‘Époque’ has an acute accent over the initial capital E letter.

To what value is this note name changed. Put another way, what was the title ($name) of the note before and after it was changed by Claude?

3

Dear Dr.Mark Anderson,
I hope you have a good time,currently.
[axon] in the post is my typo. To be precise, it is [accent].
The original name [BellÉpoque et Marcel Moyse.tbx] has been replaced with the acent excluding accent, and has been recognised by Claude.
Along the way, I received an answer from the Claude app that they tried to make access possible, excluding the .tbx extension. For future work, I decided to simply change the name of the note to [2025Moyse.tbx].
I have issued inquiries to Claude whether it is recognized that the note has been renamed, or whether it is the name of the note that it has been changed at the end. The last new name 2025Moyse.tbx, that was changed when I launched Claude again.

The answer to the second question is that Claude has not changed the title of the note.
(When running Claude, the note name is not recognized and the name is changed.) I have changed the name of the note myself. I should have written here. Sorry!

Yours, WAKAMATSU

P.S

This is A side note

Claude did not recognize the word [ typo ].
Even in the midst of chatting with Claude.
Correct the wrong sentence. Even though I wrote this, Claude didn’t understand the meaning of “Typo.”

1 Like
4

I appreciate we are working via some translation software which is the likely cause of unintentional confusion. :slight_smile:

This is a Tinderbox document name, i.e. a Tinderbox file name. The original post referred to a note name, i.e. the $Name of a note inside a document.

Scenario A - document name
You have a document file called BellÉpoque et Marcel Moyse.tbx but Claude Desktop cannot detect this file if open in Tinderbox. But, if you rename the file so no accent is used, e.g. BellEpoque et Marcel Moyse.tbx then Claude is able to detect the file.

If this is the case, the ‘error’ is likely in Claude and not Tinderbox. Claude should be able to detect a filenames including common accents. Although general English does not use accented characters, it uses plenty of loan-words from other languages, where the accented and unaccented forms are understood. As English speakers are often monoglot, and computer systems were developed in (American) English, early systems gave little thought to accents and generally discarded them, so ‘naïve’ (from French) is most often seen as ‘naïve’. Or for an acute accent ‘resumé’ and ‘resume’.

Tracking the error source in Scenario A depends on how Claude communicates with Tinderbox as if to ask “give me the name(s) of your open documents” and the format of the data returned.

Scenario B - note name

Here you have the top note name (with accent) but Claude operations result in the bottom note with a different $Name because Claude has changed ‘É’ to ‘E’ in the note title resulting in a new note instead of editing the original note.

Here the same uncertainty applies. Is Tinderbox supplying the note $name value without the accent (which seems unlikely!), or is Claude not understanding accents.

Which scenario?
So is the problem scenario A or B? In 2025, both apps should be using accent-capable Unicode encoded text for this work, but from the available information, a miscommunication between the apps seems the most likely cause here.

ping: @eastgate

5

Dear Dr. Mark Anderson,

This may be unnecessary information,
Just to be safe, I will repost most of my chat with Claude.
I apologize if this gets in the way of exchanging information here at User Forum.
N.B. WAKA is used to shorten WAKAMATSU（My name）.

WAKA: Currently using 2025.tbx
Claude: I’ll check the information in the 2025.tbx document.
Get document
request
{
name: 2025.tbx
}
response
• 2025
file: /Users/kuni33/TinderboxX/ver25/2025.tbx
size: 184 KB
2025.tbx document is recognized correctly. The file size is 184KB and we can see that this document is currently actively used.

WAKA: Is the other file BellEpoque et MarcelMoyse.tbx recognized?
Claude: I’ll check out other files too.
Get document
request
{
name: BellEpoque et MarcelMoyse.tbx
}
response

• 2025
file: /Users/kuni33/TinderboxX/ver25/2025.tbx
size: 185 KB
Yes, a file called “BellÉpoque et Marcel Moyse” is recognized. Currently 2025.tbx is active, but you can also switch to this file.

It appears that the file name contains special characters (accented É). If you want to switch to this document and work on it, you can do the following:

Switching documents
Data reference and comparison between both documents
Organizing research materials related to Marcel Moyse (flute player)

Which document would you like to work on? Also, if you need help with research and organizing materials on Bell Époque (The Beautiful Age) and Marcel Moyse, please let us know what you have done.

WAKA: It’s the first

Claude: Try again with the exact filename.
Set document
request
{
name: BellÉpoque et Marcel Moyse
}
response
Tool execution failed

There appears to be a problem with the file name notation. I’ll try using the exact name seen in the list of available documents.
Get document
request
{
name: BellÉpoque et Marcel Moyse
}
response

• 2025
file: /Users/kuni33/TinderboxX/ver25/2025.tbx
size: 185 KB

very sorry. An error occurred while switching documents. This could be caused by special characters (É).
Currently 2025.tbx remains active, but if possible:

  1. Manually activate a BellÉpoque et Marcel Moyse document on the Tinderbox side
  2. Alternatively, if the file name does not contain special characters, please provide the exact file name.

You can then review the contents of the document and proceed with the work.
Please tell us what tasks we can help you organize your research materials on Marcel Moyse and Bell Époque.

WAKA: Are there no issues except for special characters?
Claude: Yes, it is likely that the cause is a special character. Special characters (such as accented characters) may not be processed correctly in Tinderbox character encoding or API communication.
If you can change the file name, I think you can recognize and switch without any problems by changing the name to the following:

  1. BellEpoque et MarcelMoyse.tbx
  2. BellEpoque_MarcelMoyse.tbx
  3. BellEpoque and MarcelMoyse.tbx

Or, on the Tinderbox side:

  1. Change the special character (É) from the file name to the regular character (E).
  2. Save again

This should help me to switch and manage documents smoothly through my operations.

WAKA: I changed to BellEpoque et Marcel Moyse.tbx
Claude:
thank you. I’ll try switching with the changed file name. TSet document request {
name: BellEpoque et Marcel Moyse.tbx
}ResponseTool execution failed An error is still occurring. Let’s take a look at the list of available documents again. TGet document request{
name: 2025.tbx
}Response• 2025
file: /Users/kuni33/TinderboxX/ver25/2025.tbx
size: 185 KB
uuid: BB750228-9317-406E-873F-779BAA7431D6
user attributes:
Other available documents:
:- BellEpoque et Marcel Moyse

The list shows it as “BellEpoque et Marcel Moyse” so I’ll try it without the extension. TSet document request {
name: BellEpoque et Marcel Moyse
}Response OK was successful! BellEpoque et Marcel Moyse document has been switched to.
Now let’s take a look at the contents of this document. Let’s take a look at the list of notes to see how the structure is.

Get notes
request
{
query: true,
attributes: Path
}
response
Found 160 notes matching ‘true’:
BellEpoque et Marcel Moyse document has been successfully activated and we’ve been able to see its contents! This document contains some very interesting research topics.

etc. …..

Yours, WAKAMATSU

6

Ooh, thanks. Nice and useful detail and confirms it is scenario A from my options above.

How to fix the problems. Certainly, Tinderbox can make and use a TBX file with accented characters. The fact that Claude can tell you the correct (with accent) name of the file indicates the problem is not on the Tinderbox side of things.

Why Claude can’t use a files with accented characters is hard to guess. But I suggest reporting it as a but to Anthropic (who make the Claude app). It could either be an internal code library not properly passing file names, or simply a monoglot English-language programmer who’s never travelled and has no concept of non-English accented characters and has thus not properly designed their code.

For now, and certainly until the true cause is laid bare, I can only suggest you do not use filenames for your TBXs which contain accented characters, annoying as that may be.

7

Aha. It looks like this was logged as a Claude bug back in June: [BUG] Claude Code Read tool fails with special characters in filenames · Issue #1748 · anthropics/claude-code · GitHub

8

Keep in mind that Tinderbox will let Claude select among documents you have opened, but Claude is not permitted to open a document. (It could ask you to open it.)

Also, when asking Claude to use a particular Tinderbox document, omit the .tbx extension.

9

I don’t know if this suggestion will be useful to you since I don’t use Claude’s services: have you tried spelling the name of this period as follows: Belle Époque?

10

Dear Dominique Renauld,
Thanks a lot.
This problem about Tinderbox’s Note name.
There is a high possibility that this is caused by a lack of accurate French spelling.
Thank you for unraveling the problem.
In the future, I will be paying attention to how to write in French correctly.
I have one question.
Is Belle Époque allowed except for spaces between them? [BelleÉpoque]
It is also possible to use undersoles in Belle_Époque, but considering LaTeX and other factors, I don’t really want to use undersoles, right?

Yours, WAKAMATSU

1 Like
11

Dear Eastgate,
Thank you for your advice.
When calling another note, I need to ask Claude without the extension.
I had no idea about it. I will be able to take even smaller steps.
Thank you for your support.

Yours, WAKAMATSU

12

I tried the following prompt:

Please make a note, named “Belle Époque”. Write in its text a short definition of “Belle Époque”. Make the color of the note “Belle Époque” cyan.

That worked fine! Indeed, I then tried the prompt:

Veuillez créer une note intitulée « Belle Époque 2 ». Écrivez dans son texte une brève définition de « Belle Époque ». Donnez à la note « Belle Époque » la couleur cyan.

Claude replied in French, and in the new note defined Belle Époque en français.

Screenshot 2025-09-26 at 10.00.32 PM
Screenshot 2025-09-26 at 10.00.32 PM604×570 131 KB

13

Dear Eastgate,
Thank you for conducting the test.
I am happy that the results were as expected.
The reason for the failed call in Claude is that my note name is [Bell]
It is not a word with a spelling of [Belle] with [e],
This does not have an exact name rooted in history and French culture.
Some of the data woven into Claude is called the incorrect BellÉpoque.
No candidates were found. I was able to see how Claude is supporting us based on simple but complex data processing that doesn’t just happen with a simple typo.

I would like to thank Dominique Renaud for making sure his point is correct.
Thank you for giving me some information that I can walk forward.

Yours, WAKAMATSU

14

That’s right. I don’t use accented letters with LaTex.