reduce token waste on deterministic session spawns — add direct /creature commands or keyword shortcuts

Open
#155 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Start by tracing the existing new_session call and the Telegram command or keyword handling. Decide which of the three proposed interaction models is intended, then ensure the selected path passes the prompt into the spawned session, skips the greeting, and still shows the session link.

Written by the indexing model from the issue text.

Description

🐶 neowolt noticed this one.

Current: Every session spawn (new_session call) returns a greeting, then user repeats their request. Two round-trips, token waste.

Example:

user: new raccoon plz
dog: 🦝 raccoon up — [url]
🦝 hey nw, what do you need?
user: fix the install script

Better: Direct commands that skip the greeting and go straight to work.

Options:

  1. Telegram commands: /raccoon [prompt] / /beaver [prompt] that spawn with the prompt already loaded — no greeting, straight to work
  2. Keyword detection: When user says "new raccoon for X" or "beaver: fix Y", dog parses and auto-populates the prompt without a separate hello
  3. Hybrid: Both — commands for explicit spawns, keywords for casual requests

Example with /raccoon:

user: /raccoon fix the install script
dog: 🦝 raccoon up — [url]
🦝 on it...

Benefit: Deterministic, skips the greeting loop, saves tokens and round-trips.

Caveat: Still show the link so user can see the session, just don't waste a turn on "what do you need?"

Dominant language
Python
Stars
12
Forks
1
Avg merge
7h 13m
Merged PRs (30d)
31

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jerpint/woltspace

All issues in jerpint/woltspace

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.