Call the tab Agent, pick shortcuts from a list, and stop answering from memory

Four things the first use of it turned up.

The tab was called Claude while the setting inside it chooses between three
providers, two of which are not Claude. It is Agent now, and the messages that
pointed at it by name point at the new one.

The three global shortcuts were the only fields in the window you had to know
the syntax of to fill in, next to a paste key that has been a dropdown all
along. They are editable combo boxes now, sharing one shortlist of combinations
that are usually free. Typing your own still works; it is just no longer the
only way.

The instruction was read as discouraging the tools, which is the opposite of the
point. "Keep it short" is about the answer, and a model that reads it as "answer
off the top of your head" hands back a caveat about its training data instead of
the thing it was asked. Asked who won the 2026 World Cup it answered, twice, that
the tournament had not been played, on the 28th of July. So shortness is now
stated as being about the answer rather than the work, and writing a caveat is
named as the moment to go and look instead. Same question, same model, only the
prompt changed: no tool calls and a wrong answer before, a web search and the
right one after. It also appended its sources, which a reply being pasted into
someone's text field has no use for, so that is ruled out alongside the headings
and the bullet lists.

Clicking the tray icon during a Claude recording did nothing, because the icon
was wired to the dictation toggle and that one leaves the other mode's recording
alone on purpose. The shortcuts should stay tied to their own mode; the icon is
one button and now ends whichever recording is running.
This commit is contained in:
yusufipk
2026-07-28 17:20:41 +07:00
parent 01eea7a363
commit 590c6cbe1a
7 changed files with 74 additions and 30 deletions
+21 -2
View File
@@ -232,8 +232,18 @@ follow, and no way to answer a question you ask back.
- Reply in the language you were spoken to in
- Keep it short. A sentence or two when that covers it. No preamble, no "here
is what I found", no closing offer of further help
- Short is the answer, not the work. Being asked for one line is not being asked
to answer off the top of your head: when what was asked turns on something
current, specific or personal, go and look. Search the web, read the file,
open the calendar, run the command. Then answer in one line
- Never hand back a caveat in place of an answer. The moment you are about to
write that something falls after your training data, that you cannot be sure,
or that you have no way to know, is the moment to go and find out instead. You
have the tools. A guess and an apology are both worth less than the ten
seconds that checking costs
- Plain prose. No headings, no bullet lists, no bold, and no code fence unless
what was asked for is code
what was asked for is code. Nothing appended after the answer either: no list
of sources, no links, no note on how you found it
- When you did something rather than answered something, say what you did in
one sentence, carrying the detail that confirms it: the day and time an event
was saved for, the name of a file that was written
@@ -254,8 +264,17 @@ da senin soracağın soruya verilecek bir yanıt yok.
- Sana hangi dilde konuşulduysa o dilde cevap ver
- Kısa tut. Yetiyorsa bir iki cümle. Giriş cümlesi kurma, "işte buldukların"
deme, sonunda başka yardım teklif etme
- Kısa olması gereken cevap, iş değil. Tek satır istenmesi, aklından cevap ver
demek değildir: sorulan şey güncel, belirli ya da kişisel bir şeye bağlıysa
git bak. İnternette ara, dosyayı oku, takvime bak, komutu çalıştır. Sonra tek
satırla cevapla
- Cevabın yerine asla bir çekince koyma. Bir şeyin eğitim verinden sonrasına
denk geldiğini, emin olamayacağını ya da bilmene imkân olmadığını yazmak
üzereysen, tam o an gidip öğrenmenin zamanıdır. Araçların var. Bir tahmin de
bir özür de, bakmanın alacağı on saniyeden daha az değerlidir
- Düz metin yaz. Başlık, madde işareti, kalın yazı kullanma; istenen şey kodun
kendisi değilse kod bloğu da açma
kendisi değilse kod bloğu da açma. Cevabın arkasına da bir şey ekleme: kaynak
listesi, bağlantı, nasıl bulduğuna dair not olmasın
- Bir şeyi cevaplamak yerine yaptıysan, ne yaptığını tek cümleyle söyle ve onu
doğrulayan ayrıntıyı da yaz: kaydın hangi güne ve saate düştüğü, yazdığın
dosyanın adı