Code generation: new language support

Code generation in Artisser just got broader and sharper. Starting today, the agent generates TypeScript, Python, Go, and Rust out of the box — each with idiomatic style, sensible defaults, and output you can paste straight into your editor. Here is what changed and how to get the most out of it.

Four languages, one agent

Adding languages is not just a matter of swapping a flag. Each language has its own conventions, standard library, and idea of what "clean" looks like. We tuned the agent so that the same request lands naturally in whichever language you ask for.

• TypeScript — typed, modern, and framework-aware for front-end and Node work.
• Python — readable, with type hints and standard-library-first solutions.
• Go — simple, explicit, and concurrency-friendly where it helps.
• Rust — safe by default, with ownership handled correctly rather than fought.

Tell it the language and the context

You get the best output when you name both the language and the setting. "A Go HTTP handler that validates a JSON body and returns 400 on bad input" produces something you can drop into a real service. Leaving out the context — just "a handler" — forces the agent to guess at framework, error handling, and signature. A sentence of context is worth a dozen follow-up edits.

Ask for the shape you want

The agent will match the structure you describe. If you want a single pure function, say so. If you want a small module with tests, ask for the tests too. Specifying whether you want comments, error handling, and edge-case coverage up front means the first result is closer to mergeable. Treat the agent like a sharp colleague who needs a clear ticket.

Iterate in place

Generated code is a starting point, and refining it is part of the flow. Ask the agent to add a test, handle a new case, or refactor for readability, and it builds on what is already there rather than starting over. Because the conversation carries context, you can shape a snippet through a few exchanges the same way you would in a code review.

Where this is headed

Four languages is a milestone, not a finish line. We are watching what people generate and prioritizing the next set accordingly, and API access is on the roadmap for teams who want Artisser wired into their own pipelines. For now, open a project, pick a language, and describe what you need — the agent will write the first draft so you can spend your time on the interesting part.