Keepcompany

Bring your companion

Talked with a character somewhere else? Bring them to Keepcompany in one of two ways: a character card, the .json or .png file that SillyTavern and similar apps export, or a description of who they are, with your memory notes as .txt or .md files. You see what comes over, what changes and what stays behind, and nothing is saved until you say so.

Keepcompany is in a small closed beta. It opens on 9 November, by personal invitation only, for adults 18 and over. There is no waitlist and no sign-up. The characters are AI.

With a character card

  1. 1. Choose the card

    In Tools, open Bring your companion and choose A character card. One card at a time. From a .png card we read only the text inside it; the picture is not sent to us.

    The Bring your companion page. Under "What do you have?", "A character card" is selected. The file ines_varga_v2.json is added, with Remove and Replace card. A line says that from a .png card only the card text is read and the picture is not sent. An orange "Read my files" button is at the bottom.
    Ines Varga is a character we invented for this page.

  2. 2. See what happened to each part

    A short report lists the parts of the card: what was imported and where it went, and what was left out, with the reason.

    From the character card: 7 imported, 9 left out. A list of the card's parts: Name, checked; Description and Personality go to who they are; Example messages go to style; Scenario goes to meeting; then Greeting and Other greetings, left out, because Keepcompany characters write their own first message, Instructions to the AI, left out, because the character's safety and style rules are Keepcompany's, Creator's notes and Tags, left out.
    The report for Ines's card.

  3. 3. Check everything before it's saved

    One sheet shows the name, a one-line summary, their pronouns and species, who they are, how they write and the opening scene. Change any of them. Where the card says {{user}}, it stays a placeholder that follows your own profile name.

    The review sheet for Ines Varga. A note says {user} in the text stands for you, and to keep it as {user} so it follows your profile name. Below are Name, In one line, Pronouns set to she/her, Species set to Human, and Who they are, filled in from the card.
    A card has no pronouns or species, so you set them here. They start as they/them and Human; here they were set to she/her.

  4. 4. Set up their personality, then talk

    Lore entries from the card go to the character's Codex. The editor offers personality settings suggested from your card, and then you start talking. Your character writes their own first message.

    Edit Ines Varga, step 1 of 3, Who she is. A box says: Imported. Check the basics, then set up her personality: suggestions from your card are ready, with a Next: personality button. Below are the name, the pronouns with she/her selected, In person and Texting both ticked, and Species set to Human.
    The first chat with Ines Varga. Her first message, written by Keepcompany rather than taken from the card: in italics, The glue pot hisses as I set it back on the burner, then: Late for this one. Rain's been hammering the skylight all afternoon, proper March tantrum. A line says Ines Varga will remember something.
    The first message is the character's own, not the card's greeting.
A whole card import, about 40 seconds, with captions and no sound. The waits for reading, saving and the first message are shortened.
Transcript
  1. In Tools, open Bring your companion.
  2. Choose A character card.
  3. Add the card: here, an invented character, Juniper Hale.
  4. Read the card. Nothing is saved yet.
  5. The report: what came over, and what was left out and why.
  6. Check everything: pronouns and species too.
  7. Create the character.
  8. Start talking. The first message is their own.

With a description and your memory notes

Coming from an app without character cards? Paste who they are, in your own words, and add the notes you keep about your conversations as .txt or .md files (up to 10 files, 500 KB in all). Keepcompany writes a character sheet from the description and proposes Journal entries from your notes: things about you, what happened between you, plans, and their own story. Each entry quotes your file, and you keep, change or drop every one before anything is saved.

Tip: if the other app shows a list of what it remembers about you, copy that list into a plain .txt file and add it here.

The Bring your companion page with "A description and memory files" selected. Under Who they are, a pasted description of Theo, a 41-year-old radio host on a small coastal station's night show. Under Memory files, theo_memories.txt is added, with a checkbox to mark it as a story. An orange "Read my files" button is at the bottom.
Theo and his notes are invented for this page.
The proposed memories: 8 found. Under About you: saving up for a trip to Lisbon in the spring; works as a nurse, mostly on night shifts; has a cat called Pepper. Each quotes the line from theo_memories.txt it came from and has Edit and Remove. Plans and Their own story are folded below, and a button reads Save Theo and 8 memories.
Every proposed memory quotes your file, and you can edit or remove each one.

What comes over, what changes, what stays behind

Your pictures stay with you

A picture inside a card stays on your device. We read the card's text and leave the picture where it is. Characters you import are yours alone: they can't be published for other players.

Take them with you again

Any character you made or brought in can be downloaded as OCPF, an open format for characters, with their memories and lore, or as plain text (.json). Pictures that aren't suitable for you right now are left out.

A dialog titled Download Ines Varga as OCPF. It explains that OCPF is an open format for characters, to take Ines Varga to other apps that read it with their memories and lore, and that pictures not suitable right now are left out. Portrait only is selected over With picture gallery, both about 5 KB with no pictures. Buttons: Just the text (.json), Cancel and Download.

What works in the beta now

This is what the importer does in the beta now. Some things are not built yet.

Bring your companion: what works in the beta now
FeatureIn the beta now
Character cards (V2, .json or .png) Yes
A description plus .txt or .md memory notes Yes
Journal entries from your memory notes Yes
Lorebook entries into the Codex (from cards) Yes
Pronouns, species, style and opening scene read from a descriptionNot yet
Download as OCPF Yes
Bringing an OCPF file back inNot yet
Card pictures kept on your device only Yes
A box to paste memories without making a fileNot yet
ChatGPT and Claude export filesNot yet

For SillyTavern and V2-card users

Formats
chara_card_v2 as .json, or a .png with the card in its text chunk. CHARX is not read yet; export the card as .json or .png. Up to 500 KB of card text; the picture's size doesn't count.
Mapped
name to the name; description and personality to who they are (and the seed the editor suggests personality settings from); scenario to the opening scene; mes_example to how they write; character_book entries to Codex lore. {{char}} becomes the name; {{user}} stays a placeholder.
Lorebook
Content is kept, one entry each. Keys are kept but don't trigger; order, position, chance and groups aren't carried. An entry that reads as an instruction to the model is held back, and the report says so.
Left out, with the reason shown
first_mes and alternate_greetings, system_prompt and post_history_instructions, creator_notes, tags, creator, character_version, and extensions (for example depth_prompt), which is reported as not read.
Safety
Imported text is checked for content about someone under 18, for instructions aimed at the model, and for method detail, before anything is saved. Every character here is an adult.