--- title: Get started with 0.2.31 description: Natural-language work, explicit permissions, readable deliverables and source-preserving continuation. lastVerified: 2026-11-06 --- # 1.2 Get started with 0.2.31 Teloa Community 0.2.31 is published on GitHub Releases, npm and Docker Hub. [Install or upgrade](https://docs.teloa.ai/v/0.2.31/markdown/en/start/quickstart.md), configure your own model, then start with one clear job. The Docker image targets Linux ARM64. Existing installations retain their original home and follow [backup and upgrades](https://docs.teloa.ai/v/0.2.31/markdown/en/deploy/backup.md) to migrate to data version 18. ## Menus remain usable as the window changes Conversation creation, filters, folder actions and execution history share one panel. Resizing, scrolling and larger text keep it within the available space; Escape or clicking outside returns to the current work. ## Discuss in the group, start formal work when it is needed Ordinary group replies stay in their original topic without creating a separate task or run for each response. Explicitly assigned work still has its own task, progress and deliverables. Completed work remains reachable without repeating a completion checklist in the discussion. ## Keep reading and editing in context The workbench retains its familiar visual style with more compact typography and controls; personal font settings still scale the interface. Materials open for reading first, with source, version and management actions available under file information. Returning, closing details or switching reading entry points preserves the original object and unsent draft. Preparing and saving remain explicit actions. A small lock explains when business scope is fixed. Check the relevant entry point when changing ownership; browsing or dismissing a hint does not change permissions. ## Start with one description [Create an employee](https://docs.teloa.ai/v/0.2.31/markdown/en/guides/colleagues.md) or [create a task](https://docs.teloa.ai/v/0.2.31/markdown/en/guides/tasks.md) with a Markdown description, carrying the current business and source context. Review the draft before explicitly creating or starting work. Preparing configuration, saving a task and executing it are separate actions. Expand optional settings only when needed. Mention an employee with `@` or select a business, then verify the actual object and scope. A mention does not grant tools or access to another business's materials. Recheck changed sources or business context while preserving unsent content. ## Read the result before editing it Deliverables open for reading, with source, files, feedback and modification available as needed. Existing previews cover Markdown, code, images, PDF, HTML, Office files and spreadsheets; preview support does not imply retrieval support. Saving a version, opening its source, downloading a file and requesting a change remain separate actions. Historical deliverables retain their version rather than silently showing current content as the original result. ## Set explicit permissions An employee's **Permissions** entry brings business scope, materials, tools and ongoing work together. File permissions can separately restrict read, write and edit operations to files or directories, becoming effective only after an explicit save. Write permission does not grant read access; editing requires both scopes. Fine-grained file rules cannot be bypassed through arbitrary code execution: execution routes that cannot enforce them are blocked. Rejecting or cancelling an approval stops that operation. A rejection is not a missing permission to repair, and should not prompt an invitation to reauthorize. A later request you explicitly make still goes through the normal approval flow. ## Continue existing work without replaying unknown effects After a restart, eligible tasks can continue with their original Task/Run under the persisted checkpoint and current permissions. Ordinary conversations show **Continue unfinished work** when recovery is available. This does not turn an old question into a new task or automatically send the current draft. Unknown external effects, changed sources, insufficient budget or invalid permissions keep recovery waiting or refused. Restarting is not permission to repeat an operation. On a version conflict, check the current version and retained draft before continuing. ## Keep materials, memory and retrieval distinct After updating material, verify its current version and indexing state. Historical citations still point to their original version; click to inspect the actual source. General conversations, projects and employee material scopes are different. General retrieval without explicit isolation may include other materials enrolled by the same owner. Verify the business, employee grant and current selection when limiting sources. Long-term memory is selectable per conversation; source, current settings and withdrawal state are checked before use. Local retrieval needs a prepared embedding model and does not index the whole disk. A remote chat model may still receive retrieved excerpts. See [materials](https://docs.teloa.ai/v/0.2.31/markdown/en/guides/knowledge.md) and [projects](https://docs.teloa.ai/v/0.2.31/markdown/en/guides/projects.md). ## Existing composer suggestions After a reply, an empty composer may show a next-step suggestion. Tab adds it to the draft without sending; typing hides it and Escape dismisses it. Turn it off under **Settings > General > Show next-step suggestions**. Suggestions require an available model, may not appear, and do not represent executed work.