Chat & context

Written By Stanislas

Last updated About 16 hours ago

Overview

Everything about talking to Swiftask Code: the panel, sessions, and the context you provide.

Prerequisites

  • Swiftask Code installed and signed in

  • A project folder open in VS Code (session history is tied to it)

Step-by-step guide

1. Open the chat panel

Open Swiftask → Sessions from the activity bar.

ScreenWhen

Talk starter

Welcome — tips and input area

Active chat

Ongoing conversation

History

Past chats — clock icon

Plans library

Saved plans — checklist icon

See it: Title bar icons — + (new chat), clock (history), checklist (plans), gear (settings).

2. Manage sessions

A session is one conversation. Swiftask Code saves your chats on your computer.

Action

How

New chat

Plus icon in the title bar

History

Clock icon

Reset

Discard icon

Plan list

Check list icon

Stop

While Swiftask Code is working

Fork

From a message — new chat from that point

History is tied to the project folder you have open in VS Code.

3. Pick a model and thinking level

Model — which AI powers this chat (limited to what your workspace allows).

Thinking level (low / medium / high) — higher levels reason more deeply (often slower, more usage).

Both are set in the chat input, per session. See Account & workspace for models and credits.

4. Add context with @-mentions

Type @ to point at something specific:

MentionWhen to use

File

Focus on one file

Folder

Limit to part of the project

Terminal

Include command output

Branch

Discuss git / merge

URL

Online doc, ticket, or spec

Examples:

  • @src/components/ — "How is this folder organized?"

  • @Terminal 1 — "Why did this command fail?"

  • @README.md — "Summarize setup steps"

5. Use Add to Chat and images

  • Editor — select text → right-click → Add to Chat

  • Images — attachment button in the input

When to use: Stack traces, error logs, or UI screenshots — faster than retyping.

Practical use cases

Ask mode examples — use Ask when you want answers without file changes. Combine with @-mentions for best results.

GoalSample prompt

Explore a codebase

Give me an overview: main folders, how the app starts, and where the important logic lives.

Go deeper

How does [feature] work here? Walk me through the flow. — try @src/ or a specific file

Code review

Review [file or selection] for bugs, edge cases, and style. Don't modify anything — explain what you'd improve. — use Add to Chat on a selection

Switch to Build when you're ready to implement. See Build, plan & review for Build and Plan prompts.

Multiple chatsYou can run up to five active Swiftask Code tasks at once. If you hit the limit, stop a chat in another session.

A banner appears if another session is waiting for your approval.

Tips & best practices

Automatic context — every message already includes:

  • Your open file and any selection

  • A git summary (branch, changes)

  • Project rules — see Customize

You don't need to paste the active file path — Swiftask Code picks it up automatically.

Context indicator — the ring near the input shows how full the conversation's context window is.

  • Full → older messages are summarized to free space

  • New topic → start a new chat

  • Explore in Ask, implement in Build

Tip: Open the same root folder to see past chats for that project. Switching workspace in Swiftask doesn't delete local history.

Troubleshooting

Chat feels "forgetful" in long conversationsThis usually means older messages were summarized due to context limits. See Help & FAQ for more on long chats and context.

Additional resources