In-App Agent Chat

Author from a chat inside the app

The in-app chat is the fastest way to work with an agent in Looky: nothing to install, nothing to configure beyond one thing — your own AI provider key. Open a workspace, open the chat, describe the change you want, and the agent drafts the Malloy and YAML for you. You review, validate and approve before anything goes live.

• Zero install. No Python, no CLI, no editor. If you can open your Looky instance in a browser, you have everything.
• Bring your key. The chat works with Claude (Anthropic) and Gemini (Google) keys today, with more providers on the way. The key is pasted once, in the chat's settings.
• You approve what ships. The agent drafts and validates; publishing always requires your explicit yes — same rule as everywhere else in Looky.

How it works

1. Open the chat. With a workspace selected, use the chat button in the corner of the app.
2. Add your provider key. Pick your provider, paste your key, choose a model. The key is saved in your browser only.
3. Describe the change. "Add a monthly revenue trend to the sales dashboard." The agent reads your workspace and the official docs, then drafts the files in a private working copy inside your browser.
4. Review and validate. Browse the draft files right in the chat, ask for adjustments, and run validation — the same checks the CLI runs.
5. Approve the publish. When validation is clean and you say yes, the change goes live and the view refreshes in place.

If you are looking at a dashboard or visualization while you chat, the agent knows — "change this title" just works. A small chip above the message box shows what context rides along, and you can remove it with one click.

Where your work and your data live

• The draft lives in your browser. Until you publish, every edit exists only in a private sandbox in your browser — invisible to other users and to your instance.
• Your key stays yours. It is stored in your browser, travels only with each request you make, and is never kept by Looky.
• Your data never enters the conversation. The agent works with your content files and schemas — models, visualizations, dashboards — not with the rows in your database. Query results render for you in the browser, outside the chat.
• The agent reads the official docs. Its authoring contract is the same public documentation you are reading now, so it does not invent options that do not exist.

When to use which

The chat is one rung on a ladder — use as much or as little of it as you like:

• In-app chat — quick edits and new content without leaving the browser. Zero setup.
• Claude Code / Cursor workbenches — your own agent working on local files, with git and your editor around it. More control, more setup.
• By hand — the CLI and your editor, no agent at all. Everything the agents do, you can do yourself.