Copilot

Copilot is the fastest way to build in Solaris AI Flow. You describe what you want in plain English and Copilot composes the workflow: the nodes, the connections between them, and their settings. Before you see anything, it rehearses the draft against real data, flags safety issues, and lays out exactly what it built and why. Nothing lands on your canvas until you accept it, and every change it applies is undoable.

It runs on your own AI account, not ours. Log in with your ChatGPT or Grok account (no API key needed) or connect an OpenRouter or Venice key, and every model call is billed to you with a transparent token readout.

What Copilot can do

• Build a new workflow from a single prompt, ready to run.
• Edit the workflow you have open: add nodes, rewire connections, change settings, or fix what's broken, delivered as a reviewable patch.
• Plan before building: in Plan mode it asks clarifying questions and keeps a running requirements list until the idea is solid, then builds it in one click.
• Answer questions about your workflow or the platform conversationally when a prompt doesn't call for a graph.
• Improve its own drafts: one click simplifies structure, removes dead nodes, and swaps in apps you've already connected.

Connect an AI account first

Copilot needs one of four providers. If none is connected, the composer shows a note with your options:

• ChatGPT - click Log in with ChatGPT and enter a one-time code on OpenAI's site. No API key; Copilot runs on your existing ChatGPT account. Full guide: ChatGPT Integration.
• Grok - click Log in with Grok and enter a one-time code on xAI's site. No API key; Copilot runs on your existing Grok account. Full guide: Grok Integration.
• OpenRouter - one key for hundreds of models, including free ones. Get a key at openrouter.ai and add it on the Connections page.
• Venice - privacy-focused models. Add your key the same way.

When you have more than one connected, a provider switcher appears in the model picker and your choice is remembered. See Credentials for setup details.

Opening Copilot

In the editor, click the Copilot button at the bottom of the left toolbar, or the Copilot AI pill at the bottom of the canvas. On an empty canvas the prompt is front and center: "What would you like to automate?"

Outside the editor, the dashboard has a Copilot prompt bar. Type what you want to automate and it opens a new workflow with Copilot already building it. Workflows in the dashboard's "Needs attention" list also get a Fix button: Copilot opens that workflow and proposes a repair on the canvas, which you review before it applies.

Writing a prompt

Plain language works: "When a wallet I track buys a token, send me the details on Telegram." Be specific about triggers ("every 10 minutes"), destinations ("to Discord"), and conditions ("only if the market cap is under $1M").

Type @ to tag a specific app or node type, like @pumpfun, @telegram, or @loop. Tagging tells Copilot to build around that piece; the browser that pops up lists everything available. If you're out of ideas, the example cards on Copilot's welcome screen fill the composer with a full prompt you can edit before sending, and Shuffle deals a new hand.

Build now or plan first

When creating a new workflow, a Build / Plan toggle sits in the composer:

• Build drafts the workflow immediately. Best when you know what you want.
• Plan starts a conversation instead. Copilot asks numbered questions, keeps a "What I've noted so far" checklist across turns, and when the plan has no open questions it offers a one-click Build this plan.

You can also just chat: if your prompt is a question rather than a request, Copilot answers in the thread instead of forcing a graph.

Editing vs. creating

With a workflow open, an Edit / New toggle controls the target. Edit (the default on a non-empty canvas) changes the workflow you're looking at. New builds a separate workflow from scratch. Phrases like "start over" or "new workflow" switch it automatically, and your explicit toggle choice always wins.

Choosing a model

The model pill in the composer opens a full picker: search, sort by Recommended, Cheapest, Largest context, or Newest, filter to Free or Reasoning models, and star favorites. The list is fetched live from your provider, so it always reflects what your key or plan can actually access. Auto lets the server route for you, and a custom model id can be typed directly.

For models that support it, a Reasoning effort control appears: from None to Max, it trades speed for how hard the model thinks before composing. Default keeps the server's conservative setting, which is the right choice most of the time.

What happens when you generate

While Copilot works, a live thinking strip streams its progress, and drafted nodes light up as they take shape. Then comes the part most builders skip: rehearsal. Copilot actually runs the draft against real data before showing it to you. The preview reports it plainly, for example "Rehearsed live: 6 steps ran against real data", and if a step failed or a message rendered raw objects instead of text, it says so, often alongside "fixed 2 issues found in rehearsal."

The preview itself shows:

• The workflow name, node list, and connection count.
• Would have sent blocks with the exact message a Telegram or Discord step would have produced. Nothing is actually sent during rehearsal.
• Tokens involved - any token mint in the draft is verified against Jupiter and shown as a chip with its symbol, market cap, and a Solscan link. Unverified mints are flagged so you can double-check them.
• Assumptions I made and You'll need to provide - values Copilot guessed and fields or credentials only you can supply, editable inline.
• Trading safety and Could be simpler - flags like "a trade fires on every trigger run with no condition gating it" or "2 nodes whose output isn't used by anything."
• A side-effects note: either "Read-only. This workflow only reads data" or a plain statement of what it sends, trades, or spends.
• How I built this - a collapsible trace of every step Copilot took, ending with the token usage line.

Reviewing, applying, improving

• Create workflow / Apply to workflow accepts the proposal. Applied edits merge into your canvas and are undoable with Cmd+Z; Copilot also saves a restore point of the pre-change graph to Version History first.
• Discard throws the draft away.
• Improve (on new drafts) makes Copilot critique its own work. A "What I improved" summary lists what changed, like "Removed 2 unnecessary nodes" or "Swapped Birdeye for GMGN (one you've connected)". If there's nothing to simplify, it says "Couldn't simplify further" rather than churning your draft.
• Not happy? Type a follow-up: "make it every 10 minutes", "@discord too". The send button becomes Refine and the draft evolves in the same thread. Thumbs up/down on any proposal helps us tune quality.
• Stop (the send button while running) halts a generation immediately. No orphaned runs, no wasted spend.

Threads, history, and memory

Drafts survive closing the rail, reloading the page, and coming back later. Past builds in the rail header lists your recent threads (kept for 7 days), and New build starts fresh without deleting the old thread.

Under Copilot settings there's an optional, off-by-default memory: Remember my workflows grounds new builds in workflows you've previously accepted. It's kept about 90 days unless reused, and Forget everything wipes it on demand.

Troubleshooting

• "The copilot runs on your own AI account" - no provider is connected yet. Log in with ChatGPT or Grok, or add a key; the composer unlocks the moment a credential resolves.
• "Generation failed. Try again, or pick a different model." - some models are poor at structured composition. Free-tier models rate-limit aggressively; switching models via the picker resolves most failures.
• "ChatGPT session expired. Reconnect it in Connections." (or the same message for Grok) - device logins expire eventually. Reconnecting restores the same credential so nothing else needs to change. See ChatGPT Integration or Grok Integration.
• "No changes proposed. Try rephrasing the request." - in Edit mode, Copilot couldn't map your request onto the current graph. Name the node or app you mean, or tag it with @.

Copilot can make mistakes. The rehearsal, previews, and dry-run defaults exist so you catch them before they matter: review your workflow before running it live.