Artifacts.
Your result.
Instantly editable.
Documents, code, diagrams – directly editable, directly exportable.
The AI does not hand you a text blob inside the chat that you have to copy painstakingly. It hands you an artifact: a standalone result panel with a WYSIWYG editor, export options and automatic de-anonymization of placeholder data. Edit right in the panel. Export as Markdown, Word or PDF. Choose per export whether originals or placeholders are written to disk. Your edits flow into the ongoing chat.
Interactive · Preview
No chat mush. A real document.
Bigger results become an artifact: a separate, editable document next to the conversation — with versions, export and a direct path into your knowledge base. Also as HTML, a React component or an SVG diagram.
Message the AI …
What is an artifact?
Output you can
actually work with.
An artifact is a standalone result that lives next to the chat in its own panel. Not embedded in a message you have to scroll back to. A first, proper document – with a title, formatting, structure, version state.
The idea comes from the Claude ecosystem, but anymize extended it in two crucial ways:
Two extensions
Direct editing
Full WYSIWYG control, not just a preview panel. Headings, bold, italic, tables, lists – everything editable.
Automatic de-anonymization
Anonymized data is automatically translated back in the artifact preview. You see the names, addresses, IBANs of your real cases – not the placeholders.
The artifact becomes your second workspace: chat window on the left, artifact panel on the right. Ask, generate, edit, export – without switching windows.
What you can create
Four artifact types.
All editable.
Structured texts
Contracts, reports, legal briefs, discharge letters, executive summaries, proposals, reference letters. Headings, lists, tables, citations – every element of a formal document renders cleanly structured.
Code
Any language, with syntax highlighting and line numbers. Code reviews, refactoring suggestions, snippets, entire components. Directly editable, with clipboard copy and export as a file.
HTML & React
Full HTML pages or React components – rendered live inside the artifact panel. Landing pages, interactive diagrams, micro-demos, prototype UIs. Ideal for quick visualizations a text document cannot deliver.
SVG diagrams
Technical drawings, process flows, org charts, architecture sketches. Output as vector graphics, infinitely scalable, exportable for presentations.
The WYSIWYG editor
Edit exactly where
the AI stopped.
Probably the most important difference to other artifact implementations: you can edit directly inside the artifact.
01
Full formatting control
Headings (H1, H2, H3), bold, italic, tables, lists, blockquotes, code blocks. Keyboard shortcuts like in Google Docs or Word. What you see is what gets exported.
02 · The actual leverage
Edits flow into the ongoing chat
Your edits become part of the chat context. If you then ask the AI to "add a clause about …", it builds on your current state – not on its original draft.
Practical consequence: you collaborate with the AI on the same document. It writes a draft. You correct details, strike passages, add your own wording. It continues based on your state. That produces a real document partnership instead of copy-paste ping-pong.
03 · Usage patterns
Three typical document partnerships
Iterative contract drafting
AI produces the skeleton
You remove boilerplate, add client specifics
AI proposes additional clauses matching your edits
Report compression
AI produces 5 pages
You strike two paragraphs
"Summarize the rest in 1 page" – cleanly condensed, your cuts stay in
Code refactoring
AI produces a function
You rename a variable
"Adjust the tests accordingly" – tests use your renamed identifier
Export
Out of the chat.
Into your workflow.
Three export formats, one click:
Original
.mdMarkdown source file – ideal for developers, wikis, further AI processing.
As Word
.docxFor sending to clients, colleagues, editors – with full formatting and commentable passages.
As PDF
.pdfFinal, presentable version – ideal for distribution, archival, submission to authorities.
Further formats (XLSX, PPTX) are on the roadmap, depending on artifact type.
A single click on the download icon opens the selection menu. No dialog cascade, no manual filename entry – anymize suggests a sensible filename based on the artifact title.
From artifact to knowledge
Your output
becomes your archive.
Artifacts are rarely one-off results. A contract draft becomes the template for the next mandate. An executive summary becomes a building block for the next presentation. A process sketch becomes the starting point of further iterations. Instead of manually copying such documents into folders, you move them straight into a knowledge base – and they are available to the AI as context from that moment on.
The cycle
This closes a loop other AI interfaces do not offer:
The AI produces an artifact based on your question.
You refine the content in the WYSIWYG editor.
The edited artifact moves into a knowledge base.
Future chats pull your curated knowledge as context.
The AI produces an artifact based on your question.
You refine the content in the WYSIWYG editor.
The edited artifact moves into a knowledge base.
Future chats pull your curated knowledge as context.
Every answer you give today becomes part of your organization's knowledge base tomorrow. Without manually maintaining a wiki. Without endless re-copying. Without duplicate work.
Two paths to reuse
Move into an existing knowledge base
Already have a knowledge base for this topic? One click adds the current artifact. From the next query on, it will be considered during retrieval.
Create a new knowledge base from the artifact
Starting a new topic archive? One click creates a new knowledge base with the artifact as its seed.
With or without original data
When moving into a knowledge base you decide – just like on file export – whether the artifact variant with original data or the anonymized version is stored. Anonymized artifacts remain under the knowledge base's anonymization logic; original variants make sense for daily team work with access control.
More about knowledge basesAnonymization in artifacts
Originals in preview.
Two export variants.
If your chat runs anonymized (because the data is sensitive and goes to an international frontier model), artifacts are produced with placeholders first. Instantly irritating for you – you want to see your real contract, not [[LASTNAME-…]].
In preview: always originals
anymize automatically translates placeholders back inside the artifact preview. You see "Dr. Maria Schmidt", "Müller GmbH", "DE89 3704…" – not the placeholder codes. Bidirectional anonymization works in the background.
On export: you choose
Per export action, you decide which variant the file contains:
With original data
Real names, addresses, IBANs, case numbers
Internal sharing inside the team, filing to the client record, sending to the client themselves
Anonymous
Placeholders stay intact
External sharing with providers, training material, template documents for colleagues, publications
A single toggle decides. The export respects the selection fully – no accidental original data inside an anonymously intended export.
Use cases
What artifacts
actually look like.
Six types born out of real work:
Contract draft, legal brief, expert opinion outline
Word · PDF
Anonymous export for external peer review, original export for client
Executive summary, due-diligence report, presentation outline
PDF · Markdown
Anonymous export for internal training, original export for clients
Discharge letter, treatment documentation, SOP draft
Word · PDF
Anonymous export for case conferences, original into patient file
Reference letter, job posting, policy draft
Word
Anonymous export as a template for further reference letters
Code snippet, React component, architecture diagram (SVG)
Markdown · File
Can be pulled straight into the repository
Landing page HTML, newsletter draft, product FAQ
Markdown · HTML
Live rendering in the artifact panel for preview
The pattern
Artifacts live where the chat ends and the work starts. You don't just want the answer – you want the finished document, the finished code, the finished graphic. With the ability to keep editing before it goes out.
What you should know about artifacts.
Frequently asked questions
A standalone result panel next to the chat in which the AI produces structured documents, code, diagrams or HTML. Instead of hiding output inside chat messages, you get a first, proper document – with a WYSIWYG editor, export options and automatic handling of anonymized data.
We stand behind anymize. And we know – when an AI tool touches client, patient or employee data, a demo video isn't enough. That's why we give you 14 days of full access – all models, all features, no credit card. Enough time to be certain, before you trust us.
Your AI workplace awaits.