flyspace-cli 0.1.13 → 0.1.14

package/dist/index.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   startServer
-} from "./chunk-VKTJBYA3.js";
+} from "./chunk-DA7SYYKU.js";
 import "./chunk-ZBMYF5LX.js";
 export {
   startServer

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flyspace-cli",
-  "version": "0.1.13",
+  "version": "0.1.14",
   "description": "AI-native headless community OS",
   "license": "SEE LICENSE IN LICENSE",
   "private": false,
@@ -14,6 +14,7 @@
     "hooks",
     "system.default.md",
     "system.capabilities.md",
+    "templates",
     "slack-app-manifest.yml"
   ],
   "scripts": {

package/templates/general/01-welcome.md

@@ -0,0 +1,20 @@
+# Welcome to Flyspace
+
+Flyspace is team chat with an AI agent working inside every channel. You talk with your team and with the agent in the same place, and the agent does real work: reading and editing files, running scripts, answering questions about your projects.
+
+## How a workspace is laid out
+
+- **Channels** hold the conversation. Each message starts a topic, and replies stay inside that topic.
+- **Every channel is a folder.** The agent in a channel works inside that channel's folder, so a channel linked to a project can read and change the real files.
+- **#general** is the one channel everyone in the workspace can see. New members land here first.
+- **Docs** are the files in a channel's folder. You are reading one now, in the Docs pane of #general.
+
+## Where to go next
+
+1. [Working with the agent](02-working-with-the-agent.md)
+2. [Channels and folders](03-channels-and-folders.md)
+3. [Docs](04-docs.md)
+4. [Inviting your team](05-inviting-your-team.md)
+5. [Automations](06-automations.md)
+
+These guides are ordinary files. Edit them, add your own team notes next to them, or delete them once you no longer need them.

package/templates/general/02-working-with-the-agent.md

@@ -0,0 +1,21 @@
+# Working with the agent
+
+Start a topic in any channel and mention the agent, or reply inside a topic it is already part of. It answers in the same topic, so the context stays together.
+
+## What it can do
+
+- Read, write and organise files in the channel's folder.
+- Run commands and scripts on the machine connected to the workspace (your Host).
+- Summarise a long topic, draft a document, review code, research a question.
+- Schedule work for later with an automation.
+
+## Tips
+
+- **One topic per task.** A focused topic gives the agent focused context. Start a new topic when the subject changes.
+- **Point at files.** Name the file or folder you mean; the agent works from the real contents, not a guess.
+- **Ask for a doc.** For anything you want to keep (a plan, meeting notes, a spec), ask the agent to write it as a file. It then shows up in the Docs pane.
+- **Use the buttons.** When the agent offers quick replies under a message, clicking one is the same as typing it.
+
+## Where it runs
+
+The agent runs on the Host: the machine you connected during setup, using that machine's own agent CLI and login. If the Host is offline, chat still works, but the agent waits until the machine is back.

package/templates/general/03-channels-and-folders.md

@@ -0,0 +1,19 @@
+# Channels and folders
+
+Every channel has a folder behind it. That folder is where the agent works and where the channel's docs live.
+
+## Two kinds of channel folders
+
+- **New folders.** A channel you create from scratch gets its own empty folder under `~/Flyspace/<workspace>/`.
+- **Linked projects.** A channel made from an existing project folder links to that folder, so the agent works on the real project and its history.
+
+## Public and private
+
+- **Public** channels are visible to everyone in the workspace. #general is always public, and it cannot be made private, renamed or deleted.
+- **Private** channels are visible only to the members you add (and to admins).
+
+## Good habits
+
+- One channel per project, team or recurring topic.
+- Keep the conversation in the channel and the lasting knowledge in its folder: decisions, plans and notes as docs, not buried in a chat history.
+- Use the channel's settings to give its agent extra instructions, for example the project's conventions or the tone to use.

package/templates/general/04-docs.md

@@ -0,0 +1,14 @@
+# Docs
+
+The Docs pane shows the files in the current channel's folder. Markdown files render as articles; other files can be previewed or downloaded.
+
+## Working with docs
+
+- **Read and edit** Markdown right in the pane.
+- **Ask about a doc.** Open the chat beside a doc to ask the agent about it, or to have it make changes.
+- **Share.** Publish a doc as a public page with its own link when someone outside the workspace needs to read it.
+- **Let the agent write.** Ask for a plan, a summary or a spec as a file, and it appears here.
+
+## Why docs live in folders
+
+Files in the channel's folder are real files on disk, next to the project they describe. Nothing to sync, nothing to copy: the agent, your editor and your team all see the same thing.

package/templates/general/05-inviting-your-team.md

@@ -0,0 +1,17 @@
+# Inviting your team
+
+Invite people from Workspace Settings. Each person gets an email with a link to join.
+
+## Roles
+
+- **Admins** manage the workspace: members, channels, settings and billing.
+- **Members** take part in the channels they can see, and can work with the agent there.
+
+## What new members see
+
+New members land in #general and see every public channel. Private channels stay hidden until someone adds them.
+
+## Before you invite
+
+- Write a short note in #general about what the workspace is for.
+- Check which channels are public. Anything in a public channel is visible to everyone you invite.

package/templates/general/06-automations.md

@@ -0,0 +1,21 @@
+# Automations
+
+Automations run the agent without anyone typing a message.
+
+## Kinds
+
+- **Schedules** run a prompt on a timetable, for example a daily digest every weekday at 9am.
+- **Triggers** run when a message in a channel matches a pattern, for example triaging every new bug report.
+
+## Setting one up
+
+The quickest way is to ask the agent in the channel where the results should go, for example:
+
+> Post a summary of yesterday's topics in this channel every weekday at 9am.
+
+You can also create and edit automations from the channel's settings.
+
+## Tips
+
+- Start with one schedule you would actually read, then add more.
+- Keep the prompt specific about what to include and what to leave out.