Spaces

What a Space is

A Space is a folder on your computer that stays in sync with storage you and your people already use: Google Drive, OneDrive, Dropbox, Box, Nextcloud, or a shared folder on a NAS. Nobody needs to learn git or set up S3.

Every Space is laid out the same way, so people and AI tools always know where to look:

Everyone who joins keeps a synced copy at ~/Tekt/Spaces/<name> on their own computer.

Make your first Space

curl -fsSL https://tekt.md/install.sh | bash   # once: installs Tekt and the tekt command
tekt space add team drive                      # sign in to Google Drive in your browser
tekt space autosync on                         # keep it in sync every 10 minutes
tekt connect                                   # let Claude Code, Claude Desktop and Codex use it
tekt space invite team                         # write an invitation for your people

On Windows, install with irm https://tekt.md/install.ps1 | iex, then run the same tekt space commands.

Only need the Spaces part? Any computer with rclone can run bash install.sh space add team drive from a copy of the installer.

Where it can live

Tekt never sees your password. Sign-in tokens stay in rclone's config on your own computer.

Invite people

1. Share the Space's folder (for example Tekt/team in Google Drive) with them, the way you share any folder.
2. Let Tekt write the invitation:

tekt space invite team

It prints a short message and copies it to your clipboard, ready to paste into an email or chat:

Join our "team" Space on Tekt: shared documents, knowledge and AI skills.

1. I've shared the folder "team" with you on Google Drive. Open "Shared with me",
   right-click it, choose Organize > Add shortcut, and pick My Drive.
2. Install Tekt (once):
   macOS / Linux:  curl -fsSL https://tekt.md/install.sh | bash
   Windows:        irm https://tekt.md/install.ps1 | iex
3. Join:                tekt space add team drive "team"
4. Let your AI use it:  tekt connect

The steps match where the Space lives. Google Drive and OneDrive need a shortcut to the shared folder; Dropbox, Box and Nextcloud need the invitation accepted; a network folder needs its path. A folder someone shares with you lands at the top of your storage under its own name, so the join command uses "team", not "Tekt/team".

Now everyone, and everyone's AI, works from the same files.

What goes where

• Documents (docs/): proposals, PDFs, spreadsheets, meeting notes. Anything you'd want an assistant to read before it helps.
• Knowledge (knowledge/): the things your group has agreed on: decisions, how-tos, glossaries, reference answers. Keep it short and current.
• Skills (skills/): packaged instructions an AI agent loads for one kind of job. One folder per skill, with a SKILL.md inside. Tekt links shared skills straight into Claude Code (see below).

Give your AI access

One command lets the AI apps on your computer read and write your Spaces:

tekt connect                   # every supported app it finds
tekt connect claude-desktop    # or just one: claude-code, claude-desktop, codex, opencode, crush

Running it again changes nothing, and Tekt only touches its own tekt-spaces entry. Then ask your AI: "What's in my team Space?" or "Summarize the new files in team/docs."

Add tools and shared memory

Tekt also keeps a shelf of hand-picked MCP servers: tools your AI apps can call. One command adds a tool to every AI app tekt connect knows about:

tekt tool shelf                  # what's on the shelf
tekt tool add memory team        # a memory your AI writes to, kept in the team Space
tekt tool add sequential-thinking
tekt tool remove time            # take a tool back out

Shared memory is the point. With tekt tool add memory team, the memory server keeps its knowledge graph at team/knowledge/memory.jsonl, inside the Space. After a sync, everyone in the Space whose AI has the memory tool recalls the same people, decisions and facts. If two people's AIs write at the same moment, the newest version wins and the other is kept next to it.

Tekt registers each tool under its own name, like tekt-memory or tekt-fetch. A server you set up yourself, even one called memory, is never replaced or removed.

Some tools (fetch, time) run with uvx. If it's missing, Tekt tells you how to install uv.

Share skills

A skill is a folder with a SKILL.md: a short set of instructions an AI loads for one kind of job, like "summarize meeting notes our way" or "draft a proposal from our template". You share skills the way you share documents:

tekt skill new team summarize    # starts team/skills/summarize/SKILL.md from a template
# edit the SKILL.md, then:
tekt space sync team             # everyone in the Space gets it on their next sync
tekt skill list                  # every shared skill, and which ones are in your Claude Code

After each sync, Tekt links every skill in your Spaces into Claude Code as ~/.claude/skills/<space>--<skill>. When pi is installed it also links them into ~/.agents/skills, the shared folder the Agent Skills standard uses. omp picks up Claude Code's skills by itself. When someone deletes a skill, it disappears from everyone's Claude Code, and when you disconnect a Space, its skills go too. Tekt only manages its own links. Your personal skills and any folder that isn't Tekt's are never touched.

Add a curated skill

Tekt keeps a shelf of hand-picked, tested skills. Adding one puts it in a Space, so everyone in the Space gets it:

tekt skill shelf                              # what's on the shelf
tekt skill add rfp-proposal-responder team    # into the team Space, and your Claude Code
tekt space sync team                          # now everyone in the Space has it

If you have just one Space, you can leave off its name. With no Space yet, tekt skill add <skill> installs it just for you. The whole shelf is listed on the catalog.

See your Spaces in a window

Not everyone wants a terminal. tekt space gui installs RcloneView and opens it: a point-and-click window for browsing your cloud storage and copying files between it and your computer.

tekt space gui

• macOS: installed with Homebrew (brew install --cask rcloneview).
• Windows: Tekt downloads the official installer and runs it. You'll see the normal setup wizard.
• Linux: a self-contained AppImage in ~/.local/bin, with no sudo needed. It needs FUSE 2, and Tekt tells you how to add it if it's missing.
• Servers without a desktop skip it; Spaces work the same from the terminal.

RcloneView is freemium software from Bdrive Inc. The core features are free, and RcloneView Plus adds scheduling and filters. Tekt lists it in the catalog as optional.

Everyday commands

How it works

• Tekt uses rclone bisync for two-way sync. The first sync merges both sides without deleting anything.
• If the same file changed in two places, the newest version wins and the other is kept next to it with a .conflict number, so nothing is lost.
• System clutter stays out of the shared folder: .DS_Store, Thumbs.db, Office lock files (~$…) and *.tmp.
• Each Space keeps a small .tekt-space file with its settings. It stays on your computer and is never uploaded.

Troubleshooting

• A Space won't sync. Run tekt space sync <name> to see the message. If it keeps failing, reset it with the rclone bisync … --resync command Tekt prints. That merges both sides again.
• Sign-in didn't open a browser. This happens on a computer without a desktop. Run rclone authorize drive on a computer that has a browser and paste the result back, as rclone explains.
• Autosync on Windows. tekt space autosync on creates a Scheduled Task named TektSpacesAutosync. On macOS and Linux it adds one line to your crontab.