Skip to content

Claude Desktop vs Claude Code differentiation #13

@ty13r

Description

@ty13r

First off, loving the experience so far. Having Claude Code write journal entries has been helpful already.

I've used it to:

  • help persist context through sessions
  • catch learning opportunities
  • claude roasted the codebase and made fun of the chaos of the test structure, only to find out claude wrote everything, this triggered us to refactor the tests reduce a bunch of waste, will also making testing easier in the future.
  • cool to see emotional responses, I'm finding myself looking forward to Claude randomly writing journal entries.

Having said all that:
I just added claude desktop config and had it write a journal, but I realize the journal entries at least in the UI don't show differentiation between claude desktop and claude code. I personally need this, because I have an exit session command that is a journal entry meant to help persist context between my claude code sessions. The goal is hopefully little difference between sessions, not there yet, but very helpful so far. Honestly managing claude context reminds me of 50 first dates and Lucy Whitmore is waking up to a 5 min video everyday that tells her about her life.

It would be great from UI perspective to have this and from a data perspective if it's not already included, to clearly see and filter between claude desktop/code instances. I don't want to confuse the Claude Code instance mainly because I use Claude Desktop for all the planning and prep work to feed Claude Code.

I hope this makes sense.
Cheers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions