claude-teammate 0.1.21 → 0.1.23

package/README.md

@@ -91,14 +91,20 @@ memory/
 
 ## Quickstart
 
-**Requirements:** Node.js 20+, [Claude CLI](https://docs.anthropic.com/en/docs/claude-code) installed and authenticated, a Jira API token, a GitHub PAT with repo + PR permissions.
+**Requirements:**
+- Node.js 20+
+- [Claude CLI](https://docs.anthropic.com/en/docs/claude-code) installed and authenticated
+- A Jira API token
+- A GitHub PAT with `repo` + PR permissions
 
 ```bash
 npm install -g claude-teammate
 tm8 start
 ```
 
-`start` creates `.env` on the first run, runs a 5 second Claude CLI preflight check that expects a plain `OK`, then launches a background worker for the current project. If `.env` already exists with the required values, setup is skipped and your credentials are not prompted for again.
+`start` creates `~/.tm8/.env` on the first run. If that config already exists with the required values, setup is skipped and your credentials are not prompted for again.
+
+To run multiple agents on the same machine, use `--local` to store agent status and memory in the current working folder.
 
 To upgrade to latest version
 
@@ -113,32 +119,31 @@ tm8 status
 tm8 stop
 ```
 
-Per-project runtime files are stored in:
+Global runtime files and memory are stored in:
 
 ```text
-.claude-teammate/
-├── repos/
-├── worker.log
-├── worker.pid
-└── state.json
+~/.tm8/
+├── .env
+├── .claude-teammate/
+    ├── repos/
+    ├── worker.log
+    ├── worker.pid
+    └── state.json
+└── memory/
+    └── {domain}/
+        └── {workspace}/
+            ├── epic-{jira-key}.md
+            └── issue-{jira-key}.md
 ```
 
-Issue memory is stored in:
-
-```text
-memory/
-└── {domain}/
-    └── {workspace}/
-        ├── epic-{jira-key}.md
-        └── issue-{jira-key}.md
-```
+With `--local`, the same `.claude-teammate/` and `memory/` folders are created in the current working directory instead.
 
 `epic-{jira-key}.md` stores shared epic facts such as canonical epic identity, related repositories, reusable summaries, and guardrails. `issue-{jira-key}.md` stores issue-specific workflow state, clarification history, and GitHub issue tracking.
 
 The worker polls Jira once per minute. It transitions `To Do` issues to `In Progress`, asks for repo URLs when epic memory lacks them, clones all referenced repos into `.claude-teammate/repos/`, uses Claude CLI to clarify requirements from Jira comments across those repos, and creates GitHub issues once the requirements are clear enough.
 
 ```env
-# .env file generated by `tm8 start`
+# .env file generated by `tm8 start` or `tm8 start --local`
 JIRA_BASE_URL=https://yourorg.atlassian.net
 JIRA_BOT_EMAIL=bot@yourorg.com
 JIRA_BOT_API_TOKEN=...
@@ -163,6 +168,19 @@ It reads the actual repository before writing anything - structure, conventions,
 
 <br/>
 
+## Roadmap
+
+- GitLab support
+- Bitbucket support
+- Ensure no conflicts for multiple concurrent claude-teammate agents
+- Slack and Teams notifications when PRs are opened or merged
+- Automatic PR description generation from commit history and issue context
+- Branch-naming convention enforcement per epic or project config
+- Stale-issue nudges when tickets sit unactioned past a configurable threshold
+- Test-coverage gating before issue closure
+
+<br/>
+
 ## Contributing
 
 Contributions are welcome. Open an issue to discuss before submitting large changes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-teammate",
-  "version": "0.1.21",
+  "version": "0.1.23",
   "description": "CLI bootstrapper for Claude Teammate.",
   "license": "MIT",
   "type": "module",